Cryptographic Agility
The designed-in ability to replace cryptographic primitives over a device's supported lifetime.
Definition
Cryptographic agility is the architectural property that lets a system replace its cryptographic primitives - algorithms, key sizes, protocol versions - without redesign. For medical devices fielded for 10–20 years, crypto agility is essential because algorithms (e.g., SHA-1, RSA-1024, TLS 1.0) become deprecated long before the device is retired. NIST's Post-Quantum Cryptography (PQC) program (FIPS 203/204/205, 2024) makes crypto agility newly urgent for any device whose data must remain confidential into the post-quantum era.What this means in practice
Achieving crypto agility means abstracting algorithms behind interfaces, supporting algorithm negotiation at every protocol layer, planning OTA updates that can deliver new crypto, and budgeting compute headroom for PQC algorithms (which have larger keys/signatures than ECC).Examples
- A ventilator designed with crypto agility can receive an over-the-air update to switch from a legacy encryption algorithm to a quantum-resistant one, ensuring patient data remains secure as cryptographic standards evolve.
- An implantable cardiac device incorporates cryptographic agility by using modular software architecture, allowing its communication protocols to be updated from TLS 1.2 to TLS 1.3 without requiring a physical recall or hardware modification.
- A medical imaging system achieves crypto agility by abstracting its cryptographic functions behind a well-defined interface, enabling the seamless replacement of a deprecated hash function like SHA-1 with a stronger alternative like SHA-256 through a software patch.
- •Hardcoding cipher suites in firmware that cannot be updated.
- •Choosing a hardware crypto accelerator that cannot be augmented with PQC algorithms.
- •Treating crypto as 'set and forget' for a 15-year device lifetime.
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsRemote, network-delivered software or firmware updates to a fielded medical device.
The bundle of cybersecurity artifacts a sponsor includes in a 510(k), De Novo, PMA, or HDE submission for a cyber device.
The federal statute that gives FDA explicit premarket authority over cybersecurity for cyber devices.
A chain-of-trust mechanism that ensures only cryptographically signed firmware and software can run on a device.
More in Cybersecurity
· Same categoryAAMI/ANSI standard establishing requirements for medical-device cybersecurity activities throughout the lifecycle.
AAMI Technical Information Report providing MedTech-specific guidance on cybersecurity risk management.
AAMI Technical Information Report on post-market security risk management for medical device manufacturers, the operational companion to TIR57.
Unauthorized remote control of an implanted neurostimulator (e.g., DBS) to alter stimulation parameters and harm a patient.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
3 sourcesSources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.
- 1NIST Post-Quantum CryptographyTier 2 VerifiedNISTcsrc.nist.gov
- 2NIST IR 8547 PQC Migration GuidanceTier 2 VerifiedNISTcsrc.nist.gov
- 3FDA Cybersecurity Guidance (Sept 2023)Tier 2 VerifiedFDAfda.gov
Inline markers like [1] jump to the matching reference above.