← Breach analysis by the Dual Vulnerabilities framework

Capita ransomware and data theft attack (Unattributed, 2023)

2023 · United Kingdom · M - Professional, scientific and technical activities · Ransomware attack with data theft via compromised endpoint

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft via compromised endpoint

Dual vulnerability type

Expertise to Leadership

Evidence coverage: 3/6 stages, weight 25/60

Decisive stage: containment (tie-break: pre-breach condition) · Alternative: Strategy to Leadership

Why this classification

(1) Capita, the UK government's largest outsourcing supplier and administrator of hundreds of pension schemes, ran a formal security apparatus with its own written expectations: a one-hour response target for high-priority alerts, a penetration-testing and risk-assessment programme, IT security standards requiring pen-test findings to reach its CISO, and the least-privilege / account-tiering baseline the ICO pointed to NCSC guidance for. (2) In practice, after a malicious file was downloaded onto an employee device on 22 March 2023, endpoint monitoring did fire - a high-priority alert within 10 minutes - but Capita took 58 hours to act against its one-hour target; the attacker escalated to administrator privileges through an Active Directory with no tiering model for administrative accounts, moved laterally across multiple domains, exfiltrated nearly one terabyte on 29-30 March and deployed ransomware with a global password reset on 31 March, causing weeks of disruption and costs the company put at GBP 15-20m (later GBP 20-25m). (3) The ICO's October 2025 penalty findings place the decisive gap at the containment stage: the privilege-escalation and lateral-movement failings were 'flagged as a vulnerability on at least three separate occasions' but 'were not remedied' - the knowledge sat with assessments and security specialists (material origin), while group-wide directory tiering and privileged access management, exactly the remediation Capita deployed only after the incident, were never taken up, prioritised or funded at decision level (leadership break). That is the expertise-to-leadership diagonal: experts knew, leadership did not act. The entry itself is not load-bearing and the case is not classified from the attacker's technique: an employee download with immediate automated detection; the assurance failure that let the known exposure persist (no testing after commissioning, findings siloed in a federated group contrary to its own standard) is described here but classified at the entry stage only as a contributing doctrinal-to-execution condition. The competing detection-stage gap (own one-hour SLA missed by 57 hours due to a chronically understaffed SOC) reads Strategy to Leadership; the containment condition, the structural pre-breach state furthest from the breach moment, wins the tie-break and is the decisive stage. (4) RM41 (Expertise to Leadership lens): leaders deferred directory hardening and PAM despite expert and audit warnings - the ICO records the escalation path as flagged at least three times and never remedied, and the escalation needed no zero-day (causal role: Amplifying). RM34 (Expertise to Leadership lens): the raised-but-ignored high-priority alert - 10 minutes to detection, 58 hours to action - shows alert handling known to be failing for at least six months was not restored to its own standard (causal role: Obscuring). RM08 (Expertise to Leadership lens): the SOC was understaffed and under-resourced, a constraint that persisted below its targets long before the attack, so the knowable capability to handle alerts was unavailable for execution (causal role: Enabling). RM07 (Expertise to Leadership lens): expert warnings were repeatedly disregarded and diluted - vulnerability flags went unremedied and pen-test findings stayed siloed within business units instead of reaching the decision level able to address the wider network (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

Dataset caveats: the row understates the incident it describes - 'limited data exfiltration' and fields data_theft = non-sensitive (1 point), has_disruption = False and functional_impact = 'No system interference/disruption' sit against the ICO's findings of ~975 GB stolen affecting 6.6 million people including special category data (criminal records, financial data) and weeks of service disruption; the economic_impact_value of USD 32.2m roughly matches Capita's own GBP 20-25m cost estimate. The receiver_subcategory 'Critical Manufacturing' does not fit Capita's activity (business process outsourcing / professional services). The described incident (breach disclosed 3 April 2023, unauthorised access from ~22 March, interrupted 31 March) matches the stated victim and was verified as the March 2023 attack. Attribution: the row says Not attributed; the Black Basta gang posted Capita on its extortion site on 17 April 2023 (reported by BleepingComputer) - an unverified attacker claim, Capita never publicly confirmed ransomware involvement. Disclosure timeline: 3 April initial statement said no evidence of data compromise; 20 April Capita admitted 'some evidence of limited data exfiltration', three days after the extortion-site posting; The Record noted Capita described the breach only in non-standard server-estate percentages. The ICO monetary penalty notice PDF itself could not be retrieved (bot-blocked); its findings were read from the ICO's 15 October 2025 statement, corroborated by Slaughter and May, Mayer Brown and Burges Salmon analyses of the notice. A separate May 2023 incident (customer files left exposed in an AWS S3 bucket for years, first reported by TechCrunch, also under ICO enquiry) is a different incident and is not classified in this row. TPR's February 2024 intervention report documents multi-regulator coordination and communications challenges but attributes member-notification delays to forensic data-matching complexity, not to a Capita notification failure. Link check: ico.org.uk blocks automated access (HTTP 403); the page was opened and read during research.