Incident Score: Analysis & Impact (DIG1777919462)
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 DigiCert'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 DigiCert 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 DigiCert breach identified under incident ID DIG1777919462.
The analysis begins with a detailed overview of DigiCert's information like the linkedin page: https://www.linkedin.com/company/digicert-inc-, the number of followers: 195368, the industry type: Computer and Network Security and the number of employees: 1907 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 764 and after the incident was 748 with a difference of -16 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 DigiCert and their customers.
On 03 April 2024, DigiCert disclosed Cyberattack issues under the banner "DigiCert Revokes Fraudulently Obtained Certificates Following Cyberattack".
On April 2, digital certificate authority DigiCert fell victim to a cyberattack after a threat actor targeted its support team with malware disguised as a screenshot in a customer chat channel.
The disruption is felt across the environment, affecting Support portal, customer accounts, and exposing Initialization codes for EV Code Signing certificates.
In response, moved swiftly to contain the threat with measures like Revoked 60 fraudulent certificates, canceled pending orders, and began remediation that includes Enforced MFA for administrative workflows, restricted support user access to initialization codes, limited file types in support chats and Salesforce case attachments, enhanced logging capabilities.
The case underscores how Ongoing, and recommending next steps like Implement stricter access controls, enforce MFA for administrative workflows, restrict file types in support channels, enhance logging and monitoring.
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 malware disguised as a screenshot in a customer chat channel and User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating malicious payload infected two endpoints. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating malware disguised as a screenshot executed on endpoints. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating exploited authenticated support analysts to proxy into customer accounts. Under the Privilege Escalation tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating leveraged support analysts access to obtain initialization codes. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Cloud Instance Metadata API (T1552.006) with moderate confidence (60%), supported by evidence indicating obtained initialization codes for pending EV Code Signing certificates. Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with moderate confidence (50%), supported by evidence indicating proxy into customer accounts via support portal. Under the Defense Evasion tactic, the analysis identified Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating malware disguised as a screenshot in customer chat and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (60%), supported by evidence indicating delayed discovery due to malfunctioning security tools. Under the Collection tactic, the analysis identified Data from Information Repositories: Sharepoint (T1213.002) with moderate to high confidence (70%), supported by evidence indicating accessed initialization codes via internal support portal. Under the Exfiltration tactic, the analysis identified Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate confidence (50%), supported by evidence indicating issued fraudulent certificates across multiple customer accounts. Under the Impact tactic, the analysis identified Network Denial of Service (T1498) with lower confidence (40%), supported by evidence indicating revocation of 60 fraudulent certificates disrupted services and Develop Capabilities: Malware (T1587.001) with moderate to high confidence (70%), supported by evidence indicating fraudulent certificates used to sign Zhong Stealer malware. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- DigiCert Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/digicert-inc-/incident/DIG1777919462
- DigiCert CyberSecurity Rating page: https://www.rankiteo.com/company/digicert-inc-
- DigiCert Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/dig1777919462-digicert-cyber-attack-april-2026/
- DigiCert CyberSecurity Score History: https://www.rankiteo.com/company/digicert-inc-/history
- DigiCert CyberSecurity Incident Source: https://www.securityweek.com/digicert-revokes-certificates-after-support-portal-hack/
- 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