Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Crunchyroll » CRU1774377906

Incident Score: Analysis & Impact (CRU1774377906)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-86
Company Score Before Incident778 / 1000
Company Score After Incident692 / 1000
INCIDENT NUMBERCRU1774377906
Type of Cyber IncidentBreach
ATTACK VECTORCompromised third-party vendor (Okta SSO account)
DATA EXPOSEDSupport ticket records (names, email...
INCIDENT DATE31/12/2022
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Crunchyroll'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 Crunchyroll 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 Crunchyroll breach identified under incident ID CRU1774377906.

The analysis begins with a detailed overview of Crunchyroll's information like the linkedin page: https://www.linkedin.com/company/crunchyroll, the number of followers: 287244, the industry type: Entertainment Providers and the number of employees: 1925 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 778 and after the incident was 692 with a difference of -86 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 Crunchyroll and their customers.

Crunchyroll recently reported "Crunchyroll Data Breach via Third-Party Vendor", a noteworthy cybersecurity incident.

Crunchyroll, the anime streaming platform owned by Sony Pictures Entertainment and Aniplex, has acknowledged a data breach involving customer service ticket records after a threat actor publicly claimed unauthorized access to user data and internal systems.

The disruption is felt across the environment, affecting Third-party support ticket system, Crunchyroll customer service infrastructure, and exposing Support ticket records (names, email addresses, subscription information, IP addresses, message content), with nearly Approximately 8 million support ticket records (unverified) records at risk.

In response, and stakeholders are being briefed through Public acknowledgment; notifications to comply with legal obligations.

The case underscores how Ongoing, with advisories going out to stakeholders covering Notifications to be sent in compliance with legal obligations.

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 Trusted Relationship (T1199) with high confidence (90%), supported by evidence indicating incident linked to a third-party vendor handling support tickets and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (95%), supported by evidence indicating gained entry through a compromised Okta single sign-on (SSO) account. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating compromised Okta SSO account belonging to a support agent and Brute Force: Password Guessing (T1110.001) with moderate confidence (50%), supported by evidence indicating stolen credentials (human factor) as root cause. Under the Collection tactic, the analysis identified Data from Information Repositories: Sharepoint (T1213.002) with moderate to high confidence (80%), supported by evidence indicating access to approximately eight million support ticket records and Data from Local System (T1005) with moderate to high confidence (70%), supported by evidence indicating support ticket systems may contain sensitive details. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating hacker claimed unauthorized access to user data and internal systems and Transfer Data to Cloud Account (T1537) with moderate confidence (60%), supported by evidence indicating potential for data sale or phishing leveraging exposed records. Under the Impact tactic, the analysis identified Data Manipulation: Stored Data Manipulation (T1565.001) with moderate confidence (50%), supported by evidence indicating potential misuse of exposed data for fraudulent account recovery and Defacement: Internal Defacement (T1491.001) with lower confidence (40%), supported by evidence indicating unauthorized access to internal systems. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (80%), supported by evidence indicating compromised Okta SSO account used for access. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Trusted Relationship (90%)
Valid Accounts: Cloud Accounts (95%)
Credential Access
Steal Application Access Token (90%)
Brute Force: Password Guessing (50%)
Collection
Data from Information Repositories: Sharepoint (80%)
Data from Local System (70%)
Exfiltration
Exfiltration Over C2 Channel (70%)
Transfer Data to Cloud Account (60%)
Impact
Data Manipulation: Stored Data Manipulation (50%)
Defacement: Internal Defacement (40%)
Defense Evasion
Use Alternate Authentication Material: Application Access Token (80%)

Sources & References