Government | Modelled case study
Protect citizen records with confidentiality horizons longer than system life
Which identity, tax, health, benefits, and justice records need protection beyond the next platform replacement?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Chief Data Officer · Privacy · Records Management functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A public-sector body operates identity, citizen-service, procurement, records, and interagency platforms across long replacement cycles and multiple authorities.
What is at stake
Cryptographic transition must preserve public-service continuity, sovereign control, accessibility, records obligations, and interoperability across agencies and suppliers.
Situation
Government modernization moves data repeatedly while retention, public-record, archive, and privacy duties make simple deletion impossible.
Event that forces action
Cloud migration, records consolidation, or quantum-risk assessment.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
citizen record repositories
agency exchange channels
archive encryption
backup, restoration, and key destruction
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Government modernization moves data repeatedly while retention, public-record, archive, and privacy duties make simple deletion impossible.
Frame the decision the owners must make
Which identity, tax, health, benefits, and justice records need protection beyond the next platform replacement?
Apply QNSI to the controlled boundary
Map QNSI-observed cryptography to record series, retention, transfer paths, owners, and future re-protection decisions.
Leave the team with a concrete result
A citizen-record confidentiality horizon map with priority transfers, archives, and accountable exceptions.
Prove the result in the organisation's environment
Records, privacy, and legal authorities decide classification, disclosure, retention, sovereign location, and acceptable encryption.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A citizen-record confidentiality horizon map with priority transfers, archives, and accountable exceptions.
Independent validation boundary
Records, privacy, and legal authorities decide classification, disclosure, retention, sovereign location, and acceptable encryption.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.