Public bodies hold some of the most sensitive records in any society: health and social care histories, benefits claims, tax information, court and probation files, safeguarding records, and the addresses of people who need protection. These records are created to serve people over a lifetime, and many must be kept for decades by law.
Breach response plans work on a very different clock. They are measured in hours for containment, days for notification and weeks for recovery. This article looks at that mismatch, why it matters particularly for the public sector, and what persistent control over records could add to existing plans.
A mismatch of timescales
When a public-sector incident is closed, the record of it usually is too. Yet a copy of a case file or a health record taken during that incident remains sensitive long afterwards. The people it describes do not stop being vulnerable when the incident report is filed. The data cannot be changed: a medical history or a court record is what it is.
This is not a criticism of any organisation or response team. Public bodies operate under real constraints, with legacy systems, many partners and high volumes of data sharing. It is a structural gap: the tools in most response plans were designed for data that can be replaced or systems that can be rebuilt, not for records whose sensitivity outlasts the response.
Why the public sector feels this most
Several features make the gap sharper in government, health and local authorities:
- Irreplaceable data. Identity, health and case records cannot be reissued.
- Wide sharing. Records legitimately move between departments, agencies, contractors and partner organisations, so copies exist in many places.
- Long retention. Statutory retention periods keep records in existence for many years.
- High stakes for individuals. Exposure of safeguarding, health or justice data can cause serious harm.
- Public accountability. Bodies must be able to explain to oversight bodies and the public what happened and what they did about it.
What persistent control adds
Existing measures remain essential: access management, encryption, secure sharing agreements, monitoring, incident response and support for affected people. What they often lack is a way to keep exercising control once a copy has moved beyond the original system.
Persistent control means policy stays attached to selected records and is re-evaluated each time a record is used. The evaluation considers who is asking, on which device, in which environment, for what declared purpose and under the current security state. If an incident occurs, the organisation can tighten that policy and the effect applies to protected copies wherever they are used. Every decision is recorded, which supports oversight, audit and the duty to explain.
How PastWipe approaches it
PastWipe™ provides post-breach data control for enterprise and government. Policy stays attached to selected high-value data, every use of a protected copy is re-checked against identity, device, environment, declared purpose and the current security state, and the answer is allow, deny or degrade. Each decision is recorded as evidence. PastWipe sits alongside existing controls rather than replacing them, and focuses on selected records, which keeps it proportionate for organisations with large estates. The technology is US patent pending.
As with any control, there are limits. It applies to records placed under policy, and its evidence describes decisions made, not every possible route of exposure. It complements, rather than replaces, good records management and incident response.
A starting point for public bodies
A useful first step needs no procurement. Bring together information governance, security and records management leads and work through three questions:
- Which record types do we hold that would remain harmful for years if a copy left our control?
- Where do copies of those records legitimately travel today, and who holds them?
- After an incident, what control and what evidence would we have over those copies?
The answers often show where persistent control would add most value, and where existing measures are already sufficient. Either result is useful: it turns a general worry into a specific, prioritised list.
Try it on fictional data
You can test the approach on fictional records, with no integration and no real data, in the PastWipe sandbox: https://pastwipe.com/sandbox