Medical devices · Device Security Architect · Firmware Lead · Quality
Qualify post-quantum signing for medical-device secure boot
Can the boot chain verify a new signature scheme within memory, timing, safety, and update constraints?
Operational pain
A standards-compliant signature implementation does not prove that a constrained device, boot ROM, recovery image, and manufacturing process form a safe deployable trust chain.
Trigger
A new device platform, secure-boot redesign, or threat model extending beyond the product's service life.
QNSI contribution
Connect the decision to a controlled security path
Use QNSI algorithm and conformance evidence to select candidate signatures and record test results without claiming hardware execution.
Decision artifact
A secure-boot qualification dossier covering signer custody, image format, verification timing, rollback, and failure behavior.
What still requires validation
The manufacturer performs safety analysis, hardware tests, regulatory review, and production-key ceremony validation.
External problem context
Primary sources
These sources establish the external requirement or risk context. They do not endorse HEOSSI or prove that QNSI completed this scenario.
Evidence boundary
What this page does—and does not—prove
This is a product evaluation pattern, not a customer case study, certification, legal opinion, regulator endorsement, or claim that a production deployment completed the described work.