Cryptographic Agility.

Cryptographic agility, or crypto agility, is the design discipline of building systems so algorithms, key sizes, certificate types, and protocols can be upgraded without rewriting application code or breaking interoperability. It is achieved through algorithm identifiers and negotiation (TLS cipher suites, JOSE alg parameters), abstraction layers like PKCS#11 and KMS interfaces, configurable libraries, automated certificate lifecycle (ACME), and a maintained inventory of where cryptography is used — a cryptographic bill of materials (CBOM).

The agile-swap loop

flowchart LR
  A[Crypto inventory / CBOM] --> B[Algorithm behind an interface]
  B --> C[Negotiation or config selects algo]
  C --> D{Threat or standard change?}
  D -->|SHA-1 broken, PQC mandate| E[Update config / rotate keys]
  E --> C
  D -->|Stable| F[Continue operating]

Agility became urgent as SHA-1 (practically broken by the 2017 SHAttered collision), RSA-1024, and 3DES were deprecated, and it is now the prerequisite for the post-quantum migration. In August 2024 NIST finalized FIPS 203 (ML-KEM) for key encapsulation, FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for signatures; the NSA's CNSA 2.0 suite sets timelines pushing many systems to adopt them well before 2035. Because "harvest-now, decrypt-later" adversaries record encrypted traffic today, agile systems roll out hybrid schemes (e.g. X25519 + ML-KEM) through configuration rather than code rewrites. Systems lacking agility — hard-coded algorithms, opaque firmware, expired protocol libraries — face multi-year, high-risk retrofits whenever a primitive falls.