Incident Score: Analysis & Impact (MERIBM1780698286)
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 IBM'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 IBM 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 IBM breach identified under incident ID MERIBM1780698286.
The analysis begins with a detailed overview of IBM's information like the linkedin page: https://www.linkedin.com/company/ibm, the number of followers: 19057383, the industry type: IT Services and IT Consulting and the number of employees: 341860 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 833 and after the incident was 799 with a difference of -34 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 IBM and their customers.
IBM recently reported "Alleged Decade-Long Cover-Up of State-Sponsored Cyberattacks on IBM", a noteworthy cybersecurity incident.
A lawsuit filed by IBM’s former vice president of threat intelligence, William Barlow, accuses IBM of concealing multiple cyber breaches, including attacks by foreign governments over the past decade.
The disruption is felt across the environment, affecting Nearly 200 systems, and exposing Yes.
In response, teams activated the incident response plan, and stakeholders are being briefed through No public disclosure or customer notifications.
The case underscores how Ongoing litigation, with advisories going out to stakeholders covering None issued.
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 moderate confidence (60%), supported by evidence indicating outdated and vulnerable infrastructure and Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating compromising 400 accounts across 18 countries. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating aPT 10 potentially breached IBM’s network over 56,000 times and External Remote Services (T1133) with moderate to high confidence (70%), supported by evidence indicating hackers moving undetected across its systems. Under the Privilege Escalation tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (80%), supported by evidence indicating 400 accounts compromised across multiple business units. Under the Defense Evasion tactic, the analysis identified Indicator Removal (T1070) with high confidence (90%), supported by evidence indicating iBM allegedly did not retain access logs and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating outdated and vulnerable infrastructure. Under the Credential Access tactic, the analysis identified OS Credential Dumping (T1003) with moderate to high confidence (80%), supported by evidence indicating 400 accounts compromised and Adversary-in-the-Middle (T1557) with moderate confidence (60%), supported by evidence indicating hackers moving undetected across its systems. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate to high confidence (80%), supported by evidence indicating 400 accounts compromised across 18 countries and File and Directory Discovery (T1083) with moderate to high confidence (70%), supported by evidence indicating nearly 200 systems compromised. Under the Lateral Movement tactic, the analysis identified Remote Services (T1021) with high confidence (90%), supported by evidence indicating hackers moving undetected across its systems in 18 countries and Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating 400 accounts compromised. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating healthcare data, federal client data potentially compromised and Data from Information Repositories (T1213) with moderate to high confidence (70%), supported by evidence indicating truven (healthcare data company) breached post-acquisition. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), supported by evidence indicating aPT 10 campaign spanning 2013–2016 and Proxy (T1090) with moderate confidence (60%), supported by evidence indicating state-sponsored group operating undetected. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data exfiltration motivation; 56,000 breaches and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating state-sponsored group with espionage motives. Under the Impact tactic, the analysis identified Defacement (T1491) with lower confidence (40%), supported by evidence indicating undisclosed breaches at major tech firm and Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating lack of access log retention. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- IBM Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/ibm/incident/MERIBM1780698286
- IBM CyberSecurity Rating page: https://www.rankiteo.com/company/ibm
- IBM Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/meribm1780698286-ibm-truven-cyber-attack-january-2013/
- IBM CyberSecurity Score History: https://www.rankiteo.com/company/ibm/history
- IBM CyberSecurity Incident Source: https://techcrunch.com/2026/06/05/former-cyber-executive-turned-whistleblower-accuses-ibm-of-covering-up-several-data-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