Defense & national security | Modelled case study
Modernize signing for defense software delivered into disconnected enclaves
How will an offline enclave verify the release, signer authority, dependency evidence, and revocation state?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the DevSecOps · Release Authority · Configuration Management functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A national-security programme spans mission systems, disconnected enclaves, coalition interfaces, long-life platforms, controlled releases, and supplier-delivered components.
What is at stake
Silent downgrade, unverifiable software, or an incomplete transition boundary can affect mission assurance and confidentiality well beyond the service life of current equipment.
Situation
Air-gapped delivery removes online validation while long-lived trust stores and removable media amplify the consequences of a compromised build signer.
Event that forces action
Software-factory accreditation, signing-key rotation, or adoption of post-quantum release signatures.
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.
defense software factory
release authority
offline transfer media
enclave verification and revocation
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
Air-gapped delivery removes online validation while long-lived trust stores and removable media amplify the consequences of a compromised build signer.
Frame the decision the owners must make
How will an offline enclave verify the release, signer authority, dependency evidence, and revocation state?
Apply QNSI to the controlled boundary
Bind QNSI-supported signature evidence to release manifests, build provenance, signer generation, and offline trust bundles.
Leave the team with a concrete result
An enclave-verifiable release packet containing artifact digests, signer chain, SBOM reference, revocation snapshot, and expiry.
Prove the result in the organisation's environment
The programme validates build isolation, media handling, approved algorithms, key ceremony, offline verification, and rollback.
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 enclave-verifiable release packet containing artifact digests, signer chain, SBOM reference, revocation snapshot, and expiry.
Independent validation boundary
The programme validates build isolation, media handling, approved algorithms, key ceremony, offline verification, and rollback.
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.