Software & SaaS | Modelled case study
Give SaaS customers verifiable release-signing provenance
Can a customer verify which build produced an artifact and which authorized identity approved it?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Release Engineering · Product Security · Customer Trust functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A software provider ships frequent releases through source, build, package, deployment, dependency, and customer-assurance systems.
What is at stake
Customers and regulators need to distinguish an authorized release and evidenced control from a claim assembled after an incident.
Situation
A valid package signature alone does not expose source revision, dependency set, build worker, approval, or whether the key was used outside policy.
Event that forces action
Enterprise procurement, software-supply-chain review, or migration to post-quantum 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.
source revision
CI build identity
artifact registry
release approval and customer verification
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
A valid package signature alone does not expose source revision, dependency set, build worker, approval, or whether the key was used outside policy.
Frame the decision the owners must make
Can a customer verify which build produced an artifact and which authorized identity approved it?
Apply QNSI to the controlled boundary
Bind QNSI-supported signature metadata to artifact digests, build provenance, key generation, and release approval.
Leave the team with a concrete result
A customer-verifiable release manifest with artifact, source, builder, signer, algorithm, and evidence links.
Prove the result in the organisation's environment
The vendor validates build isolation, source controls, dependency integrity, key custody, transparency, and verification tooling.
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 customer-verifiable release manifest with artifact, source, builder, signer, algorithm, and evidence links.
Independent validation boundary
The vendor validates build isolation, source controls, dependency integrity, key custody, transparency, and verification tooling.
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.