Exposed: Woeful security at UK criminal records office that led to sensitive data leak
REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); According to the Information Commissioner's Office (ICO), which reprimanded ACRO rather than imposing a financial penalty, the breach was uncovered in March 2023 only because ACRO was investigating a separate intrusion. REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/c'); }); Busting ICO enforcement jargon The ICO has a few enforcement tools in its belt when it comes to data protection offenders. Monetary penalties are pretty self-explanatory, but are reserved only for the very worst and most flagrant UK GDPR offenses.
- ▪REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); According to the Information Commissioner's Office (ICO), which reprimanded ACRO rather than imposing a financial penalty, the breach was unc
- ▪REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/c'); }); Busting ICO enforcement jargon The ICO has a few enforcement tools in its belt when it comes to data protection offenders.
- ▪Monetary penalties are pretty self-explanatory, but are reserved only for the very worst and most flagrant UK GDPR offenses.
The Register publishes from United Kingdom and files mainly under tech. We currently carry 509 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Register |
| Canonical URL | https://www.theregister.com/security/2026/08/12/exposed-woeful-security-at-uk-criminal-records-office-that-led-to-sensitive-data-leak/5286736 |
| Publication time | Wed, 12 Aug 2026 15:40:00 +0200 |
| Retrieval time | 2026-08-12T13:41:36.930Z |
| Last seen | 2026-08-12T13:41:36.930Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 3mAGxYvXTwsy · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); SECURITY Exposed: Woeful security at UK criminal records office that led to sensitive data leak Nobody patched the CMS or read the alerts, and ACRO still cannot tell whether info was exfiltrated Connor Jones Connor Jones Cybersecurity reporter Published wed 12 Aug 2026 // 14:40 UTC The UK's criminal records office, ACRO, has escaped a fine and received a regulatory reprimand after security failings potentially exposed highly sensitive data belonging to nearly 11,000 people.ACRO disclosed…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Register.
Discussion
0 commentsMore from The Register
