Incident Score: Analysis & Impact (ZSCPALDRISAL1773852939)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Salesloft's Breach and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Salesloft Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Salesloft breach identified under incident ID ZSCPALDRISAL1773852939.
The analysis begins with a detailed overview of Salesloft's information like the linkedin page: https://www.linkedin.com/company/salesloft, the number of followers: 119144, the industry type: Software Development and the number of employees: 1181 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 615 and after the incident was 525 with a difference of -90 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Salesloft and their customers.
Salesloft recently reported "The Great SaaS Breach of 2025: How a Single OAuth Token Compromised 700+ Organizations", a noteworthy cybersecurity incident.
A new report from Grip Security reveals alarming trends in SaaS security, analyzing 23,000 SaaS environments and uncovering critical vulnerabilities.
The disruption is felt across the environment, affecting Salesforce, Slack, Drift Chatbot, AWS Environments, and exposing PII, Customer Data, OAuth Tokens, Refresh Tokens.
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as The incident underscores the risks of shadow AI and IdentityMesh, where AI-embedded SaaS applications lack formal oversight. OAuth tokens, treated as routine access credentials, can become critical weak links if stolen. The attack highlights the need for dynamic governance, continuous oversight, and risk-based controls to manage AI as a third-party risk, and recommending next steps like Replace static approvals with dynamic governance, implement continuous oversight, and adopt risk-based controls for AI-enabled SaaS environments. Treat AI as a managed third-party risk to mitigate cascading breaches.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (90%), with evidence including compromised Salesloft’s GitHub repositories, and supply chain such as true and Steal Application Access Token (T1528) with high confidence (95%), supported by evidence indicating stole OAuth and refresh tokens used by customers to connect Drift Chatbot. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (95%), supported by evidence indicating oAuth and refresh tokens stolen from Drift’s AWS environment, Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (80%), supported by evidence indicating oAuth tokens treated as routine access credentials in GitHub repositories, and Adversary-in-the-Middle (T1557) with moderate to high confidence (70%), supported by evidence indicating infostealers likely used to steal tokens. Under the Lateral Movement tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating legitimate OAuth token used to impersonate Drift and breach Salesforce and Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (95%), supported by evidence indicating oAuth tokens used to cascade through connected systems (IdentityMesh). Under the Collection tactic, the analysis identified Data from Cloud Storage Object (T1213.003) with moderate to high confidence (80%), supported by evidence indicating pII, customer data compromised via Salesforce installations and Data from Local System (T1005) with moderate to high confidence (70%), supported by evidence indicating data compromised via AI-embedded SaaS applications. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with moderate to high confidence (80%), supported by evidence indicating cascading breaches through connected systems (700+ organizations) and Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating attackers likely exfiltrated data via compromised OAuth channels. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (90%), supported by evidence indicating legitimate OAuth token used to bypass authentication controls and Hide Artifacts: Email Hiding Rules (T1564.008) with moderate confidence (60%), supported by evidence indicating shadow AI enabled attacks without formal oversight. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (70%), supported by evidence indicating aI-embedded SaaS apps used as vectors for cascading breaches and Data Destruction (T1485) with moderate confidence (50%), supported by evidence indicating potential data manipulation via compromised Salesforce installations. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Salesloft Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/salesloft/incident/ZSCPALDRISAL1773852939
- Salesloft CyberSecurity Rating page: https://www.rankiteo.com/company/salesloft
- Salesloft Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/zscpaldrisal1773852939-salesloft-zscaler-drift-palo-alto-networks-breach-january-2025/
- Salesloft CyberSecurity Score History: https://www.rankiteo.com/company/salesloft/history
- Salesloft CyberSecurity Incident Source: https://www.securityweek.com/the-shadow-ai-problem-how-saas-apps-are-quietly-enabling-massive-breaches/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf