Data & Economics
What does a data breach actually cost a UK public body?
The government's survey measures breach costs for businesses and charities, not public bodies, and not detection time. What the figures do and do not tell you.
The short answer
There is no official figure for UK public bodies. The government's Cyber Security Breaches Survey 2025/2026, published by DSIT and the Home Office on 30 April 2026, covers businesses, charities and education institutions; other public-sector organisations are outside its scope. Among businesses and charities that identified a breach or attack, it put the median perceived cost of the most disruptive one at £0, because many reported no direct financial loss, while at the 95th percentile, which marks the costliest 5% of cases, the perceived cost was £4,000 for businesses and £10,000 for medium and large businesses. The survey does not measure detection time. IBM's Cost of a Data Breach Report 2026, a vendor-published global study, puts the mean time to identify a breach at 183 days and to contain it at a further 64 days, but gives no figure for UK public bodies. The direct cost is only part of the picture; time to detection is a separate measure of exposure.
Data breach costs get quoted constantly, usually from a vendor's own annual report, with underlying data nobody outside the vendor can check. The UK government publishes its own figures, and they are worth using where they apply, because they are official statistics from a random-probability survey of businesses, charities and education institutions rather than a sales document. They have one important limit for this journal's readers: public-sector organisations other than schools, colleges and universities are outside the survey's scope.
What are the headline numbers?
The Cyber Security Breaches Survey 2025/2026, commissioned by the Department for Science, Innovation and Technology (DSIT) and the Home Office and published on 30 April 2026, puts the median perceived cost of the most disruptive breach or attack at £0 for both businesses and charities that identified one, and £30 for medium and large businesses. That does not mean breaches are harmless: the survey notes that a £0 median reflects many organisations reporting no direct financial loss, and that a minority face high costs. At the 95th percentile, which marks the costliest 5% of cases, the perceived cost was £4,000 for businesses and £10,000 for medium and large businesses. The previous edition, published in April 2025, reported mean costs of £1,600 per business and £3,240 per charity; this edition stopped reporting means because the costs are highly skewed and subject to high sampling error, which makes a mean an unreliable indicator.
None of these figures covers central government, councils or other public bodies, which the survey's technical report places outside its scope. Its separate education annex covers schools, colleges and universities but does not report breach costs.
Why does detection time matter more?
The cost figure is a snapshot. The more revealing number is how long an incident sits undetected, because every additional day is additional exposure. The government survey does not measure this, so here we have to rely on the kind of vendor research described above. IBM's Cost of a Data Breach Report 2026, based on research by the Ponemon Institute into 602 organisations in 17 industries across 16 countries and regions, found a mean of 183 days to identify a breach and a further 64 days to contain it, 247 days in all, up from 241 days in the previous year's report. These are global averages across all industries. The report does not publish detection times for the public sector or for UK public bodies, so there is no published measure of how UK public bodies compare.
The survey's cost figure is a snapshot of direct cost. IBM's global average of about six months to identify and contain a breach is a separate measure, and it is not specific to UK public bodies.
Why is detection time an economics question, not just a security one?
Every day a breach goes undetected is a day of continuing exposure, additional data at risk, and a longer, more expensive remediation once it is finally found. A council or public body budgeting for cyber risk on the direct cost figure alone is pricing only part of the problem. The detection gap is where cost compounds: longer exposure windows mean larger incidents, more extensive notification obligations, and a harder job proving to a regulator or an auditor exactly what happened and when.
What does this mean for procurement decisions?
These figures are a useful, if indirect, benchmark for any public body evaluating how it holds sensitive data, and for weighing the cost of a shared, third-party-managed estate against infrastructure it can see into directly; none of them measures UK public bodies themselves. This is one part of the wider economics this journal covers: not whether AI and digital sovereignty sound appealing in principle, but what the published numbers actually say about the cost of getting detection and control right, or wrong.
For context on where that spend currently goes, see our companion piece on UK public sector dependency on hyperscale cloud.
Correction, 26 September 2026: an earlier version of this article attributed to the government survey a mean breach cost, detection times and public-sector coverage that it does not contain. It now uses the survey's own 2025/2026 medians and percentiles, states that public bodies are outside its scope, and credits detection times to IBM's global 2026 report.
Sources cited in this article
Questions readers ask
- Where do these figures come from?
- The cost figures come from the Cyber Security Breaches Survey 2025/2026, official statistics commissioned by the Department for Science, Innovation and Technology (DSIT) and the Home Office and published on GOV.UK on 30 April 2026. It is the UK government's annual survey of businesses, charities and education institutions. Public-sector organisations other than schools, colleges and universities are outside its scope, so it gives no cost figure for central government, councils or other public bodies. The survey does not measure detection time, so the detection figures come from IBM's Cost of a Data Breach Report 2026, a global study conducted by the Ponemon Institute and published by IBM.
- Does the public sector take longer to spot a breach?
- No official source answers that for UK public bodies. The government survey does not measure detection time, and IBM's 2026 report gives global averages (183 days to identify a breach and 64 days to contain it) without a UK public-sector breakdown. Reasons often given for slower detection in large public organisations, such as fragmented estates, legacy systems and reliance on third-party and shared infrastructure, are plausible, but no published figure measures their effect on UK public bodies.
- Does keeping data on infrastructure you control reduce this?
- It changes the shape of the problem rather than eliminating it. An organisation running its own infrastructure still has to invest in detection and response, but it is not waiting on a third party to notice or disclose an incident on its behalf, and it has direct visibility into its own systems rather than partial visibility into a shared, multi-tenant environment. Whether that translates into a shorter detection time depends on what is actually built, not on ownership alone.
Published by Mickai LTD. Written by Micky Irons.
Common Fortune covers the economics of the whole category and treats Mickai as one option among serious alternatives. About the journal and the team.
Mickarle Wagstaff-Irons - Micky Irons, full name Mickarle Sean Junior Wagstaff-Irons. Founder and CEO of Mickai. Biography and related work.