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

Incident Score: Analysis & Impact (CAM1769571508)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-117
Company Score Before Incident778 / 1000
Company Score After Incident661 / 1000
INCIDENT NUMBERCAM1769571508
Type of Cyber IncidentBreach
ATTACK VECTORCredential Stuffing
DATA EXPOSEDNine million customer records
INCIDENT DATE12/01/2020
STATUSCompleted (convictions secured)

Key Highlights From The Incident Analysis

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

The analysis begins with a detailed overview of Camelot's information like the linkedin page: https://www.linkedin.com/company/camelot, the number of followers: 34321, the industry type: Consumer Services and the number of employees: 977 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 661 with a difference of -117 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 Camelot and their customers.

Camelot (National Lottery) recently reported "Cybercriminal Jailed for Nine Months Over National Lottery Hack", a noteworthy cybersecurity incident.

A 29-year-old man from Notting Hill, London, was sentenced to nine months in prison for his role in a cyberattack targeting the National Lottery.

The disruption is felt across the environment, affecting National Lottery customer database, and exposing Nine million customer records, with nearly 9,000,000 records at risk, plus an estimated financial loss of £13 stolen from one account, £5 shared with Batson.

Formal response steps have not been shared publicly yet.

The case underscores how Completed (convictions secured), teams are taking away lessons such as Even basic cybercrime has serious consequences, and offenders will be pursued and prosecuted. Highlights risks of credential-stuffing attacks.

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 Brute Force: Credential Stuffing (T1110.004) with high confidence (95%), with evidence including used the hacking tool Sentry MBA to launch credential-stuffing attacks, and bombard lottery accounts with thousands of login attempts. Under the Credential Access tactic, the analysis identified Brute Force: Credential Stuffing (T1110.004) with high confidence (95%), with evidence including sentry MBA...to launch credential-stuffing attacks against Camelot, and shared a victim’s login details with Idris Kayode Akinwunmi and Credentials from Password Stores (T1555) with moderate to high confidence (70%), supported by evidence indicating compromised a database containing nine million customer records. Under the Execution tactic, the analysis identified User Execution: Malicious Link (T1204.001) with moderate confidence (60%), supported by evidence indicating provided others with a configuration file to launch credential-stuffing attacks. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating nine million customer records compromised and Data Manipulation: Stored Data Manipulation (T1565.001) with moderate confidence (50%), supported by evidence indicating stole £13 from the account and sent £5 to Batson. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating nine million customer records compromised via credential-stuffing attacks. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Brute Force: Credential Stuffing (95%)
Credential Access
Brute Force: Credential Stuffing (95%)
Credentials from Password Stores (70%)
Execution
User Execution: Malicious Link (60%)
Impact
Data Destruction (40%)
Data Manipulation: Stored Data Manipulation (50%)
Exfiltration
Exfiltration Over C2 Channel (70%)

Sources & References