Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Amazon Web Services (AWS) » AMA1780793273

Incident Score: Analysis & Impact (AMA1780793273)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-8
Company Score Before Incident820 / 1000
Company Score After Incident812 / 1000
INCIDENT NUMBERAMA1780793273
Type of Cyber IncidentCyber Attack
ATTACK VECTORBotnet of malware-infected machines
DATA EXPOSEDNA
INCIDENT DATE18/06/2020
STATUSpublished

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 AMA1780793273.

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.

Amazon Web Services (AWS) recently reported "AWS Shield Mitigates Largest DDoS Attack in History at 2.3 Tbps", a noteworthy cybersecurity incident.

Amazon Web Services (AWS) disclosed that its DDoS protection service, AWS Shield, successfully defended against the largest recorded distributed denial-of-service (DDoS) attack in February.

Impact assessments are still underway, so the full scope is not yet clear.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like AWS Shield defense mechanisms.

The case underscores how teams are taking away lessons such as The attack underscores the growing sophistication of cybercriminal operations and the escalating arms race between attackers and defenders.

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 Impact tactic, the analysis identified Network Denial of Service (T1498) with high confidence (95%), with evidence including dDoS attack peaked at 2.3 Tbps, and overwhelm systems by flooding them with traffic and Direct Network Flood (T1498.001) with high confidence (90%), with evidence including dDoS attack...flooding them with traffic, and botnets of malware-infected machines. Under the Resource Development tactic, the analysis identified Botnet (T1583.005) with moderate to high confidence (85%), supported by evidence indicating botnets of malware-infected machines that cybercriminals rent cheaply and Malware (T1588.001) with moderate to high confidence (80%), supported by evidence indicating botnets of malware-infected machines. Under the Initial Access tactic, the analysis identified Endpoint Denial of Service (T1499) with moderate to high confidence (70%), supported by evidence indicating dDoS attacks overwhelm systems by flooding them with traffic. Under the Defense Evasion tactic, the analysis identified Network Denial of Service (T1498) with moderate confidence (60%), supported by evidence indicating aWS Shield successfully defended against the attack. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Impact
Network Denial of Service (95%)
Direct Network Flood (90%)
Resource Development
Botnet (85%)
Malware (80%)
Initial Access
Endpoint Denial of Service (70%)
Defense Evasion
Network Denial of Service (60%)

Sources & References