Government | Modelled case study
Require a cryptographic bill of materials in government procurement
Does a proposed product expose enough algorithm, library, certificate, and key-custody detail to plan future transition?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Procurement · Agency Security · System Owner 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
Security questionnaires produce broad assurances while opaque dependencies and fixed cryptographic choices appear only after award.
Event that forces action
A major software, cloud, device, or managed-service solicitation.
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.
supplier product inventory
cryptographic bill of materials
contract acceptance evidence
vulnerability and support commitments
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
Security questionnaires produce broad assurances while opaque dependencies and fixed cryptographic choices appear only after award.
Frame the decision the owners must make
Does a proposed product expose enough algorithm, library, certificate, and key-custody detail to plan future transition?
Apply QNSI to the controlled boundary
Define QNSI-compatible CBOM fields and evidence status for bidders, then normalize accepted product records into the agency inventory.
Leave the team with a concrete result
A scored procurement schedule covering crypto components, ownership, agility, conformance, support dates, and qualification gaps.
Prove the result in the organisation's environment
The agency verifies supplier evidence, contract remedies, update commitments, accessibility, and mission-specific requirements.
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 scored procurement schedule covering crypto components, ownership, agility, conformance, support dates, and qualification gaps.
Independent validation boundary
The agency verifies supplier evidence, contract remedies, update commitments, accessibility, and mission-specific requirements.
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.