Medical devices | Modelled case study
Bind a medical-device SBOM to the exact released firmware
Can a hospital or assessor verify that the SBOM, vulnerability status, and firmware image describe the same release?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Product Security · Quality Systems · Regulatory Affairs functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A medical-device manufacturer supports embedded products across development, regulatory submission, manufacturing, hospital deployment, servicing, and field update lifecycles.
What is at stake
Trust changes must preserve safe boot and update behavior on constrained devices while maintaining traceability from released software to regulatory evidence.
Situation
SBOM files are often generated separately from release artifacts and lose trustworthy linkage after vendor portals, distributors, or service teams copy them.
Event that forces action
Premarket submission, vulnerability disclosure, field update, or customer security review.
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 and dependency inventory
SBOM generator
firmware build and signer
released device configuration
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
SBOM files are often generated separately from release artifacts and lose trustworthy linkage after vendor portals, distributors, or service teams copy them.
Frame the decision the owners must make
Can a hospital or assessor verify that the SBOM, vulnerability status, and firmware image describe the same release?
Apply QNSI to the controlled boundary
Record signature policy and provenance for firmware, SBOM, build evidence, and release approval using QNSI-supported primitives.
Leave the team with a concrete result
A signed release manifest linking component inventory, firmware digest, signer, build identity, and approval state.
Prove the result in the organisation's environment
The manufacturer proves SBOM completeness, build reproducibility, vulnerability triage, signing-key protection, and distribution integrity.
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 signed release manifest linking component inventory, firmware digest, signer, build identity, and approval state.
Independent validation boundary
The manufacturer proves SBOM completeness, build reproducibility, vulnerability triage, signing-key protection, and distribution integrity.
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.