Incident Score: Analysis & Impact (STE1764701205)
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 StepSecurity'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 StepSecurity 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 StepSecurity breach identified under incident ID STE1764701205.
The analysis begins with a detailed overview of StepSecurity's information like the linkedin page: https://www.linkedin.com/company/step-security, the number of followers: 13596, the industry type: Computer and Network Security and the number of employees: 23 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 749 and after the incident was 686 with a difference of -63 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 StepSecurity and their customers.
GitHub recently reported "Non-Human Credential Exploitation in App-to-App Access", a noteworthy cybersecurity incident.
Attackers target app-to-app access using API keys, OAuth tokens, and service accounts to move laterally and remain undetected.
The disruption is felt across the environment, affecting Google Workspace, Salesforce, Slack, AI productivity tools, and exposing Sensitive data (emails, customer data, communications).
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as Non-human credentials (API keys, OAuth tokens, service accounts) are a critical attack vector. Legacy security monitoring focused on human identities is insufficient. AI tools and agents amplify risks due to their broad access and machine-speed operations, and recommending next steps like Increase visibility and control over non-human credentials. Implement monitoring for app-to-app access. Enhance security measures for AI tools and agents to prevent lateral movement and data exfiltration.
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 Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), with evidence including compromised API keys, OAuth tokens, and service accounts, and entry point such as Compromised non-human credentials and Cloud Service Discovery (T1526) with moderate to high confidence (80%), supported by evidence indicating attackers target app-to-app access across Google Workspace, Salesforce, Slack. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (95%), with evidence including exploitation of OAuth tokens and API keys, and non-human credentials are cybercriminals new frontier and Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating insufficient monitoring and control over non-human credentials. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (90%), with evidence including attackers move laterally using API keys and OAuth tokens, and aI tools inherit API access for multi-service workflows and Remote Services: Cloud Services (T1021.007) with moderate to high confidence (85%), supported by evidence indicating lateral movement across Google Workspace, Salesforce, Slack. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Pass the Hash (T1550.002) with moderate to high confidence (70%), supported by evidence indicating attackers remain undetected using non-human credentials and Hide Artifacts: Email Hiding Rules (T1564.008) with moderate confidence (60%), supported by evidence indicating aI agents operate under the radar of legacy security monitoring. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with moderate to high confidence (85%), with evidence including data exfiltration of emails, customer data, communications, and motivation such as Data exfiltration. Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Credentials (T1098.001) with moderate to high confidence (80%), supported by evidence indicating attackers establish undetected persistence via non-human credentials. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- StepSecurity Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/step-security/incident/STE1764701205
- StepSecurity CyberSecurity Rating page: https://www.rankiteo.com/company/step-security
- StepSecurity Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ste1764701205-stepsecurity-breach-december-2025/
- StepSecurity CyberSecurity Score History: https://www.rankiteo.com/company/step-security/history
- StepSecurity CyberSecurity Incident Source: https://www.scworld.com/perspective/seven-ways-to-manage-nhis
- 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