Government | Modelled case study
Pilot a dual-stack post-quantum PIV migration
How can new credentials and services be tested without locking out users or breaking relying applications?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Agency CIO · Identity Programme · PKI Authority 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
PIV authentication, signing, encryption, middleware, readers, and relying systems evolve on different procurement and accreditation schedules.
Event that forces action
PIV refresh planning, new federal guidance, or a major identity-platform replacement.
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.
PIV credentials
issuance and lifecycle systems
physical and logical access readers
federated application trust
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
PIV authentication, signing, encryption, middleware, readers, and relying systems evolve on different procurement and accreditation schedules.
Frame the decision the owners must make
How can new credentials and services be tested without locking out users or breaking relying applications?
Apply QNSI to the controlled boundary
Use QNSI inventory and policy to identify credential use, relying-party compatibility, algorithm cohorts, and exception lifetimes.
Leave the team with a concrete result
A PIV dual-stack pilot plan with relying-party matrix, test identities, rollback, and retirement gates.
Prove the result in the organisation's environment
The agency and accredited assessors approve profile conformance, issuance, middleware, accessibility, and authorization impacts.
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 PIV dual-stack pilot plan with relying-party matrix, test identities, rollback, and retirement gates.
Independent validation boundary
The agency and accredited assessors approve profile conformance, issuance, middleware, accessibility, and authorization impacts.
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.