Medical devices | Modelled case study
Build the cryptography section of a medical-device premarket file
Is every cryptographic claim connected to a design requirement, implementation, verification result, and residual risk?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Regulatory Affairs · Product Security · Systems Engineering 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
Algorithm lists and architecture diagrams fail review when they omit key generation, update, recovery, certificate, third-party, and lifecycle evidence.
Event that forces action
A connected-device submission or significant cybersecurity design change.
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.
product threat model
cryptographic design inventory
verification evidence
regulatory submission package
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
Algorithm lists and architecture diagrams fail review when they omit key generation, update, recovery, certificate, third-party, and lifecycle evidence.
Frame the decision the owners must make
Is every cryptographic claim connected to a design requirement, implementation, verification result, and residual risk?
Apply QNSI to the controlled boundary
Export scoped QNSI algorithm, key, policy, provenance, and conformance references into the manufacturer's controlled technical file.
Leave the team with a concrete result
A traceable crypto evidence index mapping claims to tests, artifacts, owners, and unresolved qualification work.
Prove the result in the organisation's environment
The manufacturer owns the quality record, threat model, safety case, submission conclusions, and regulator interaction.
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 traceable crypto evidence index mapping claims to tests, artifacts, owners, and unresolved qualification work.
Independent validation boundary
The manufacturer owns the quality record, threat model, safety case, submission conclusions, and regulator interaction.
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.