Incident Score: Analysis & Impact (AMA1768595116)
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 Amazon Web Services (AWS)'s Cyber Attack 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 Amazon Web Services (AWS) 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 Amazon Web Services (AWS) breach identified under incident ID AMA1768595116.
The analysis begins with a detailed overview of Amazon Web Services (AWS)'s information like the linkedin page: https://www.linkedin.com/company/amazon-web-services, the number of followers: 10600547, the industry type: IT Services and IT Consulting and the number of employees: 153837 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 820 and after the incident was 812 with a difference of -8 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 Amazon Web Services (AWS) and their customers.
A newly reported cybersecurity incident, "Russian Sandworm Hackers Target Misconfigured AWS Edge Devices in Multi-Year Campaign", has drawn attention.
Russian state-sponsored hackers (Sandworm group) conducted a yearslong cyberattack campaign in 2025 targeting misconfigured network edge devices hosted on AWS infrastructure.
The disruption is felt across the environment, affecting Enterprise routers, VPN concentrators, remote access gateways, EC2 instances running customer-managed network appliances, and exposing Credentials, network access.
In response, moved swiftly to contain the threat with measures like Disruption of active threat operations, customer notifications, and stakeholders are being briefed through Public disclosure by Amazon's Threat Intelligence unit.
The case underscores how Ongoing (disruption of active operations, customer notifications), teams are taking away lessons such as Shift in Sandworm tactics from zero-day exploits to low-effort targeting of misconfigured devices; importance of securing edge devices and cloud-hosted network infrastructure, and recommending next steps like Secure management interfaces on edge devices, enforce proper configurations, monitor for persistent connections from actor-controlled IPs, collaborate with cloud providers for threat intelligence.
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 Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating exploited exposed management interfaces on customer-owned edge devices and External Remote Services (T1133) with moderate to high confidence (80%), supported by evidence indicating targeted misconfigured VPN concentrators and remote access gateways. Under the Credential Access tactic, the analysis identified Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating harvest credentials to move laterally within victim networks and Unsecured Credentials: Private Keys (T1552.004) with moderate to high confidence (70%), supported by evidence indicating exploited misconfigured network edge devices for credential harvesting. Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate to high confidence (80%), supported by evidence indicating moved laterally within victim networks after initial access and Remote Services: SSH (T1021.004) with moderate to high confidence (70%), supported by evidence indicating persistent connections to compromised EC2 instances. Under the Persistence tactic, the analysis identified External Remote Services (T1133) with moderate to high confidence (80%), supported by evidence indicating maintained persistent access via misconfigured edge devices and Account Manipulation (T1098) with moderate to high confidence (70%), supported by evidence indicating actor-controlled IPs established persistent connections. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (60%), supported by evidence indicating minimizing detection risks by leveraging misconfigurations and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (70%), supported by evidence indicating used harvested credentials to evade detection. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating credentials and network access compromised via edge devices. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating persistent connections to actor-controlled IPs suggest data exfiltration. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Amazon Web Services (AWS) Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/amazon-web-services/incident/AMA1768595116
- Amazon Web Services (AWS) CyberSecurity Rating page: https://www.rankiteo.com/company/amazon-web-services
- Amazon Web Services (AWS) Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ama1768595116-aws-cyber-attack-june-2021/
- Amazon Web Services (AWS) CyberSecurity Score History: https://www.rankiteo.com/company/amazon-web-services/history
- Amazon Web Services (AWS) CyberSecurity Incident Source: https://www.crn.com/news/cloud/2026/aws-infrastructure-targeted-by-russian-cyberattacks-in-years-long-campaign-copy
- 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