Incident Score: Analysis & Impact (FED1781749923)
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 FedEx's Ransomware 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 FedEx 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 FedEx breach identified under incident ID FED1781749923.
The analysis begins with a detailed overview of FedEx's information like the linkedin page: https://www.linkedin.com/company/fedex, the number of followers: 2256620, the industry type: Freight and Package Transportation and the number of employees: 194419 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 821 and after the incident was 762 with a difference of -59 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 FedEx and their customers.
National Health Service (NHS) recently reported "Global Ransomware Attack Disrupts NHS, Hospitals Across 100 Countries", a noteworthy cybersecurity incident.
A massive ransomware attack struck the UK’s National Health Service (NHS) and organizations worldwide on Friday, crippling hospital systems, canceling operations, and diverting ambulances.
The disruption is felt across the environment, affecting Hospital IT systems, Windows-based computers, and exposing Patient records, appointment systems.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like System wipes, reinstallation to prevent reinfection, and began remediation that includes Applied Windows patches, urged software upgrades, while recovery efforts such as Restoring systems from backups (unconfirmed if backups existed) continue, and stakeholders are being briefed through Public statements by Home Secretary Amber Rudd and Prime Minister Theresa May.
The case underscores how Ongoing (as of incident report), teams are taking away lessons such as Need for timely software patching, risks of outdated IT infrastructure (e.g., Windows XP), importance of backup protocols, challenges in securing large networks, and recommending next steps like Apply security patches promptly, upgrade unsupported systems (e.g., Windows XP), implement robust backup strategies, enhance phishing awareness training, improve incident response planning, with advisories going out to stakeholders covering Public statements by UK government officials (Amber Rudd, Theresa May).
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 Phishing: Spearphishing Attachment (T1566.001) with high confidence (90%), supported by evidence indicating attack began after an employee opened a malicious email attachment and Exploit Public-Facing Application (T1190) with moderate to high confidence (80%), with evidence including exploited a Windows vulnerability (MS17-010), and leveraged a flaw in Microsoft Windows. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), with evidence including exploited a Windows vulnerability (MS17-010), and malware identified as WanaCrypt0r 2.0. Under the Persistence tactic, the analysis identified Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with moderate confidence (50%), supported by evidence indicating ransomware encrypted files on infected computers (implied persistence). Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating exploited Windows SMB vulnerability (MS17-010). Under the Defense Evasion tactic, the analysis identified Disabling Security Tools (T1089) with lower confidence (40%), supported by evidence indicating systems reverted to pen-and-paper (implied disruption of security tools) and Indicator Removal: File Deletion (T1070.004) with moderate confidence (50%), supported by evidence indicating full system wipe and reinstallation required to prevent reinfection. Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with high confidence (90%), with evidence including rapid spread across 99 countries, and exploited Windows SMB vulnerability (MS17-010). Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (100%), with evidence including ransomware encrypted files on infected computers, and demanding $300 ransom in Bitcoin and Inhibit System Recovery (T1490) with moderate to high confidence (80%), with evidence including full system wipe required to prevent reinfection, and no confirmation of backups. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with lower confidence (30%), supported by evidence indicating patient data exposure (potential exfiltration not confirmed). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- FedEx Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/fedex/incident/FED1781749923
- FedEx CyberSecurity Rating page: https://www.rankiteo.com/company/fedex
- FedEx Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/fed1781749923-fedex-ransomware-may-2017/
- FedEx CyberSecurity Score History: https://www.rankiteo.com/company/fedex/history
- FedEx CyberSecurity Incident Source: https://www.theguardian.com/society/2017/may/12/hospitals-across-england-hit-by-large-scale-cyber-attack
- 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