Public sector | Modelled case study
Accelerate federal HVA PQC migration under EO 14412
Which high-value asset systems can meet the accelerated PQC key-establishment deadline, and in what sequence?
Reviewed as of 2026-10-26 · primary scenario
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Federal Program Lead · Cryptography Lead · CISO 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, records obligations, and interoperability across agencies and suppliers.
Situation
EO 14412 (June 2026) accelerates federal HVA and high-impact-system PQC key-establishment migration ahead of earlier timelines, and suppliers must show inventory, CBOM and a dated migration plan.
Event that forces action
EO 14412 direction and agency CIO milestones, alongside FedRAMP 2026 consolidated-rules reporting.
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.
HVA crypto inventory and CBOM
key establishment and TLS endpoints
migration waves and FIPS boundaries
agency reporting evidence
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
EO 14412 (June 2026) accelerates federal HVA and high-impact-system PQC key-establishment migration ahead of earlier timelines, and suppliers must show inventory, CBOM and a dated migration plan.
Frame the decision the owners must make
Which high-value asset systems can meet the accelerated PQC key-establishment deadline, and in what sequence?
Apply QNSI to the controlled boundary
Classify HVA cryptography from inventory/CBOM records, plan FIPS 203/204/205 transitions, and publish signed migration evidence.
Leave the team with a concrete result
An HVA crypto migration plan with dated waves, FIPS-boundary notes and agency-ready evidence.
Prove the result in the organisation's environment
The program office validates agency milestones; cryptography confirms FIPS boundaries and enclave/HSM constraints.
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
An HVA crypto migration plan with dated waves, FIPS-boundary notes and agency-ready evidence.
Independent validation boundary
The program office validates agency milestones; cryptography confirms FIPS boundaries and enclave/HSM constraints.
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.