Six weeks after hackers broke into the system Bristol's schools run on, the stolen data is out in public. More than 320,000 files have turned up on the dark web, and Bristol City Council says it cannot yet tell families what is in them.
The files come from Trading with Schools, a Bristol City Council service providing IT and administrative support to local schools. Malicious software got into the platform on September 21, 2026. The council detected suspicious activity and shut the system down on September 25, four days later — leaving many schools without their telephone systems. At the time, the council's leader told the BBC investigators had not identified evidence that data was stolen. That assurance held for six weeks; then the council confirmed a significant number of files had been taken and published online.
The scale is in the structure of the service. Eighty-eight schools use Trading with Schools; 49 buy only internet services, and the council says the theft is not believed to have affected those. The other 39 use it for much more: scheduling, lesson plans, staff details, payroll, and records about students — including, potentially, sensitive educational psychology files about children. It is that group whose data investigators have identified in the material circulating online. The council has not confirmed which kinds of records were in the leak, or all the schools and individuals affected. Vik Verma, the council's director of education and skills, told parents to remain vigilant — criminals holding real school contact details can make fraudulent messages look credible.
The investigation is now a race between the audit and the exposure. The council is working with Avon and Somerset Police, the South West Regional Organised Crime Unit, and specialist advisers to establish what the published files contain and who they concern. But the files are already public, and the people whose details may be in them are the ones who have to stay vigilant.
What actually failed
Start with the assurance. "We have not identified evidence that data was stolen" is a true statement about an investigation at a moment in time, and it reads — to parents, to schools, to everyone downstream — as "your data was not stolen." The difference between those two sentences is the difference between a fact and a reassurance, and when the reassurance is wrong, the cost is paid in the six weeks during which nobody watched for misuse of data that had, in fact, been taken. It is the same shape as the DigiCert story in this series.
Second, concentration by design. Trading with Schools exists to do exactly what it did: gather the administrative life of 39 schools — payroll, HR, scheduling, children's records — into one shared platform, because that is efficient and that is what a council service is for. Efficiency concentrates risk: one compromise becomes the payroll and personnel records of dozens of schools and the sensitive files of children.
Third, the detection window. Four days passed between the malware entering on September 21 and the shutdown on September 25. Four days is fast by the standards of this series, and it still left time for more than 320,000 files to be taken. The lesson is not that four days is slow: it is that the volume taken in days from a concentrated store is already more than any audit can quickly characterize — which is why the council, six weeks later, still cannot say what is in the leak.
How Redthread is built for this class of failure
Say this plainly first: Redthread does not secure council school systems, did not assess Trading with Schools, and no assessment product would have patched an unknown intrusion in that platform from the outside. The honest mapping is to the pattern — the concentrated store, the early assurance that proved wrong, the audit racing the exposure — and to the one discipline that narrows all three: continuous, evidence-based verification of where sensitive data lives and who can reach it.
The assessment platform (redthreadsec.com) is agentless and AI-native, and it starts from the question this breach forces every organization that runs a shared platform to ask: where does sensitive data actually live, including in administrative systems, and what paths reach it? It builds one context graph of your whole estate — the Redthread Flow — covering agents, applications, code, cloud accounts, identities, controls, and the data they can reach. The free self-serve estate scan (Assess & Consolidate) — nothing to install — shows your AI and agent footprint, shadow-AI, cloud posture and sensitive-data exposure (DSPM), and cross-cloud attack paths, ranked first. Our exploit-validation engine actually exercises weaknesses, pentesting AI applications and agents against the OWASP LLM Top 10 as mapped to MITRE ATLAS, with a reproducible proof of concept for every finding. Evidence, never inferred. CI/CD gating blocks merges that introduce proven attack paths, continuous re-assessment catches drift, and results roll up into reports and Letters of Attestation mapped to the frameworks your auditors ask about.
The Agentic Trust & Protection Platform — ATPP (trust.redthreadsec.com; in the console, Agent Trust & Enforce) applies the same principle to machine authority: cryptographic agent identity (SPIFFE) bound to builds, call-time verification of identity and tool claims jointly, attenuating delegation with signed receipts, revocation that propagates when a tool drifts, signed trust-state events that orchestrators, gateways, and SIEMs can react to in seconds, and a daily signed scan of the MCP registry — our November 1 scan covered 54,513 servers and found 1,509 listing swaps — anchored in the public Sigstore Rekor transparency log, with our Enforce gateway, currently in preview, putting these checks in-path, and hooks for Claude Code and Cursor that check each MCP tool call against the server's signed claim before it runs. Its relevance here is the principle the Bristol timeline confirms: the difference between "no evidence of theft" and "no theft" is evidence, continuously gathered — and a finding is only as good as the last time it was re-verified.
What Redthread does NOT claim
Plainly: we do not claim Redthread would have prevented this breach, detected the malware sooner, or given Bristol City Council a complete picture of the exposure — we were not inside those systems, the intrusion method has not been disclosed, and the investigation is ongoing. We do not claim children's educational psychology files were in the leak: the platform can hold such files and reporting describes them as potentially exposed, but the council has not confirmed the contents. We also do not claim to know which 39 schools are affected — the council has not published the list. What we claim is the pattern-level lesson: when a shared platform concentrates sensitive data, the only honest answer is continuous, evidence-based verification of where it lives and who can reach it — plus the discipline to report "we have not yet found evidence" as exactly that. If your child attends a Bristol school using Trading with Schools, the council's advice stands: stay vigilant for unexpected messages that use real school details.
Build it with us
We are opening two to three founding design-partner slots: a free 30–45-day pilot — estate scan, cryptographic identity and call-time verification on one live workflow, detect-only, plus the attestation evidence your auditors keep asking for — with deeply discounted, locked founding pricing after.
If sensitive data lives in a shared platform in your estate — and it does — start with the free estate scan at redthreadsec.com, or come straight to us about a design-partner slot.
Sources: BBC reporting via TechRadar and CyberPresso, "Hackers Published 320,000 Files Stolen From 39 Bristol Schools," Nov 4, 2026; Silicon UK, "Hackers Publish Stolen Data After Bristol Schools Hack," Nov 5, 2026; TES, "Cyberattack leads to online leak of schools' data," Nov 4, 2026; SC Media, "Bristol schools data breach leads to online leak of 320,000 files," Nov 5, 2026; Cyber Insider, "Bristol schools face major data exposure," Nov 5, 2026.