MGB
MGB // Cyber Blog
← All incident files

Capita: 58 hours to quarantine one device

In March 2023 an employee at Capita downloaded a malicious file. An alert fired within ten minutes. The device stayed on the network for 58 hours, and by the end of the month 6.6 million people's data had been taken. The regulator's £14 million fine explains why.

The short version
  • What happened: a malicious file downloaded on one employee device gave an attacker a foothold. They reached administrator access, moved across the network, copied out nearly a terabyte of data and deployed ransomware.
  • The gap: detection worked. The first alert was raised within ten minutes, but the device was not quarantined until 58 hours after the compromise, against a one-hour target.
  • Root causes the ICO found: no tiering model for administrator accounts, an understaffed security operations centre that had missed its response targets for months, and penetration testing that was too limited and too siloed.
  • Outcome: 6.6 million people affected and a £14 million fine, reduced from a provisional £45 million. Capita accepted liability and did not appeal.
10 minTime to first alert
58 hrsTime to quarantine the device
~1 TBData taken
6.6MPeople affected
£14mICO fine

Timeline

Went wrong Worked Context

22 Mar 2023

A malicious file is downloaded. An employee unintentionally downloads it onto their device.

22 Mar 2023

The alert fires within ten minutes. A high-priority security alert is raised and some automated action is taken.

Next 58 hours

Nobody quarantines the device. It is not quarantined until 58 hours after the compromise, around 24 March. The ICO says the attacker used that time to exploit Capita's systems.

Dates not given

The attacker escalates and spreads. The malware keeps the attacker in the network. They gain administrator permissions and move laterally.

29 to 30 Mar 2023

Data leaves the network. Nearly one terabyte is copied out.

31 Mar 2023

Ransomware is deployed. The attacker resets every user password, locking staff out of their systems.

Oct 2025

The ICO issues its penalty. A provisional £45 million fine is reduced to £14 million: £8 million for Capita plc and £6 million for Capita Pension Solutions Limited. Both accepted liability and did not appeal.

What went wrong

  • Administrator accounts were not tiered. There was no tiering model, so one compromised device could lead to administrator access and lateral movement. The ICO says this had been flagged as a vulnerability at least three times and never fixed.
  • The response was far too slow. The alert took ten minutes. Containment took 58 hours against a one-hour target. The security operations centre was understaffed and had missed its response targets for at least six months before the attack.
  • Penetration testing was too thin. Systems holding millions of records were tested only when first commissioned, and test findings stayed inside individual business units, so wider network risks were never addressed.
  • Breadth of impact. 6.6 million people were affected, including some records with criminal records, financial data or special category data. 325 of the 600-plus organisations whose pension data Capita Pension Solutions processes were affected.

What worked

  • Detection. The alert was raised within ten minutes, and some automated action followed.
  • Accepting responsibility. Capita accepted liability and did not appeal. It offered 12 months of credit monitoring, and more than 260,000 people activated it.

What would have helped

This section is MGB's own analysis, not part of the source material.

  • Tier administrator accounts. Separate, protected accounts for domain and identity administration, never used on ordinary workstations, remove the easy path from one infected laptop to the whole estate.
  • Measure time to contain, not just time to detect. If a managed detection service does the response, put the contain time in the contract, and let it isolate a device automatically on a high-severity alert.
  • Close repeated findings. A finding raised three times needs an executive owner and a date. Track it until it is fixed or formally accepted.
  • Test regularly and share the results. Re-test systems that hold large volumes of personal data, and share findings across business units so network-wide risk has an owner.