Incident Score: Analysis & Impact (ZENPCC1769030611)
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 Zendesk'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 Zendesk 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 Zendesk breach identified under incident ID ZENPCC1769030611.
The analysis begins with a detailed overview of Zendesk's information like the linkedin page: https://www.linkedin.com/company/zendesk, the number of followers: 649809, the industry type: Software Development and the number of employees: 7843 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 758 and after the incident was 679 with a difference of -79 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 Zendesk and their customers.
PcComponentes recently reported "PcComponentes Credential Stuffing Attack", a noteworthy cybersecurity incident.
PcComponentes denied a major data breach but confirmed a credential stuffing attack exposed sensitive account details of customers.
The disruption is felt across the environment, and exposing Order histories, physical addresses, full names, phone numbers, IP addresses, product wishlists, customer support messages, national ID numbers, email addresses, with nearly 500,000 leaked (16.3 million claimed) records at risk.
In response, moved swiftly to contain the threat with measures like Invalidated active sessions, forced re-authentication, and began remediation that includes Implemented CAPTCHA protections, mandatory two-factor authentication (2FA) for all accounts.
The case underscores how Ongoing, teams are taking away lessons such as Importance of enforcing multi-factor authentication (2FA) and monitoring for credential reuse from previous breaches, and recommending next steps like Enforce 2FA for all accounts, implement CAPTCHA protections, monitor for credential stuffing attacks, and educate users on password hygiene, with advisories going out to stakeholders covering Forced re-authentication with 2FA enabled, CAPTCHA protections implemented.
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 Valid Accounts (T1078) with high confidence (90%), with evidence including credential stuffing attack exposed sensitive account details, and reused login credentials from previous breaches and Brute Force: Credential Stuffing (T1110.004) with high confidence (95%), supported by evidence indicating attack stemmed from credential stuffing where attackers used reused login credentials. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with moderate to high confidence (80%), supported by evidence indicating compromised credentials traced to info-stealing malware infections and Gather Victim Identity Information: Credentials (T1589.002) with moderate to high confidence (70%), supported by evidence indicating sample of verified emails from the leak matched records in existing infostealer logs. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating leaked data included order histories, physical addresses, full names, phone numbers, IP addresses and Data from Information Repositories (T1213) with moderate to high confidence (70%), supported by evidence indicating customer support messages exchanged via Zendesk. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating 500,000 entries leaked and remainder offered for sale on hacker forums and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), supported by evidence indicating data exfiltration and sale on dark web. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate confidence (60%), supported by evidence indicating invalidated active sessions, forcing users to re-authenticate. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating no evidence of data destruction, but included due to breach impact and Disk Wipe: Disk Structure Wipe (T1561.002) with lower confidence (20%), supported by evidence indicating no evidence, but included as potential secondary impact. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Zendesk Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/zendesk/incident/ZENPCC1769030611
- Zendesk CyberSecurity Rating page: https://www.rankiteo.com/company/zendesk
- Zendesk Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/zenpcc1769030611-zendesk-pccomponentes-breach-june-2020/
- Zendesk CyberSecurity Score History: https://www.rankiteo.com/company/zendesk/history
- Zendesk CyberSecurity Incident Source: https://www.bleepingcomputer.com/news/security/online-retailer-pccomponentes-says-data-breach-claims-are-fake/
- 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