Incident Score: Analysis & Impact (ATTIBM1780946436)
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 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 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 ATTIBM1780946436.
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 "IBM and AT&T Accused of Covering Up Years-Long Data Breaches by Chinese Hackers", a noteworthy cybersecurity incident.
A recently unsealed whistleblower lawsuit alleges that IBM and AT&T concealed multiple data breaches spanning from 2013 to 2016, including attacks attributed to Chinese state-backed hackers.
The disruption is felt across the environment, affecting IBM’s core network, at least two IBM subsidiaries, and exposing True.
In response, and stakeholders are being briefed through Concealment alleged.
The case underscores how Ongoing (lawsuit).
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 (50%), with evidence including breaches affecting its core network, and aPT 10 may have breached IBM’s systems over 56,000 times and Trusted Relationship (T1199) with moderate to high confidence (70%), with evidence including aT&T managed IBM’s network infrastructure, and breaches extended to at least two IBM subsidiaries. Under the Persistence tactic, the analysis identified Account Manipulation (T1098) with moderate confidence (60%), supported by evidence indicating aPT 10 breached systems over 56,000 times during three-year period and Create Account (T1136) with moderate confidence (50%), supported by evidence indicating poor network design and insufficient logging may have enabled persistence. Under the Credential Access tactic, the analysis identified OS Credential Dumping (T1003) with moderate confidence (60%), supported by evidence indicating neither IBM nor AT&T could confirm what data was accessed or altered and Unsecured Credentials (T1552) with moderate to high confidence (70%), supported by evidence indicating poor network design and insufficient logging. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate confidence (60%), supported by evidence indicating breaches extended to at least two IBM subsidiaries and Network Service Discovery (T1046) with moderate to high confidence (70%), supported by evidence indicating aPT 10 breached IBM’s core network over 56,000 times. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), with evidence including data breach involving state-sponsored espionage, and personally identifiable information compromised and Data from Information Repositories (T1213) with moderate to high confidence (70%), supported by evidence indicating breaches affecting IBM’s core network and subsidiaries. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), with evidence including data exfiltration confirmed, and aPT 10 attributed to state-sponsored espionage and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating insufficient logging prevented confirmation of exfiltration methods. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), with evidence including aPT 10 breached systems over 56,000 times, and state-sponsored threat actor and Encrypted Channel (T1573) with moderate confidence (60%), supported by evidence indicating insufficient logging prevented detailed analysis of C2 methods. Under the Defense Evasion tactic, the analysis identified Indicator Removal (T1070) with moderate to high confidence (80%), with evidence including iBM lacked critical logs to determine scope of breaches, and alleged concealment of breaches and Impair Defenses (T1562) with moderate to high confidence (70%), supported by evidence indicating poor network design and insufficient logging. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating neither IBM nor AT&T could confirm what data was altered and Defacement (T1491) with lower confidence (30%), supported by evidence indicating brand reputation impact due to alleged cover-up. 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/ATTIBM1780946436
- IBM CyberSecurity Rating page: https://www.rankiteo.com/company/ibm
- IBM Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/attibm1780946436-ibm-att-breach-january-2013/
- IBM CyberSecurity Score History: https://www.rankiteo.com/company/ibm/history
- IBM CyberSecurity Incident Source: https://www.securitymagazine.com/articles/102353-whistleblower-accuses-ibm-at-and-t-of-covering-up-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