Medical devices | Modelled case study
Rotate field-update trust on devices that cannot all reconnect
How can offline or intermittently connected devices learn a new update key without accepting an attacker-controlled root?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Fleet Operations · Device Engineering · Customer Support 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
Devices in homes, clinics, and remote sites may miss intermediate updates, leaving trust-anchor replacement dependent on insecure manual exceptions.
Event that forces action
Signing-key expiry, compromise response, manufacturer acquisition, or algorithm transition.
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.
deployed device cohorts
update signing keys
offline and intermittent update channels
rollback and revocation state
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
Devices in homes, clinics, and remote sites may miss intermediate updates, leaving trust-anchor replacement dependent on insecure manual exceptions.
Frame the decision the owners must make
How can offline or intermittently connected devices learn a new update key without accepting an attacker-controlled root?
Apply QNSI to the controlled boundary
Track device cohorts, accepted signer generations, overlap windows, and recovery policy as migration evidence in QNSI.
Leave the team with a concrete result
A fleet trust-transition matrix with last-safe versions, staged bundles, fallback media, and retirement criteria.
Prove the result in the organisation's environment
Device owners test every supported upgrade path, anti-rollback behavior, offline recovery, and patient-safety impact.
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 fleet trust-transition matrix with last-safe versions, staged bundles, fallback media, and retirement criteria.
Independent validation boundary
Device owners test every supported upgrade path, anti-rollback behavior, offline recovery, and patient-safety impact.
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.