DES, MD5, SHA-1, RC4, TLS 1.0: every one of these was once standard and later had to be removed, usually painfully and over many years. Post-quantum migration is the next big change, but not the last. New attacks will appear, and some post-quantum algorithms may themselves need replacing. Crypto-agility is the ability to change cryptographic algorithms, parameters and implementations quickly, safely and at low cost.

What makes systems inflexible

  • Algorithms hard-coded throughout application code.
  • Fixed-size database fields and message formats that assume, for example, 256-byte signatures.
  • Protocols with no algorithm negotiation.
  • Devices with cryptography burned into hardware or firmware that can't be updated.
  • No inventory, so nobody knows where an algorithm is used.
  • Vendor products with no roadmap for new algorithms.

Patterns for agility

1. Centralise cryptography behind an abstraction

Application code should ask for a capability ("encrypt this for storage", "sign this document") rather than a specific algorithm. A central library or service decides which algorithm to use, based on policy. Changing the policy then changes behaviour everywhere without code changes.

2. Make algorithms configuration, not code

Algorithm choices, key sizes and protocol suites belong in configuration managed centrally: TLS cipher suites and groups in load balancer templates, signing algorithms in build pipelines, KMS key specs in infrastructure as code.

3. Label everything with its algorithm

Store an algorithm identifier with every ciphertext, signature and key, so systems know how to process old data while new data uses new algorithms. Many formats (JOSE, CMS, X.509) already support this; custom formats often don't.

4. Size for growth

Post-quantum keys and signatures are much larger. ML-DSA signatures are several kilobytes compared with about 64 bytes for ECDSA. Avoid fixed-length fields, check protocol and header size limits, and test with realistic sizes. See the NIST standards field guide.

5. Use protocols that negotiate

Prefer protocols where both sides can negotiate algorithms, such as TLS 1.3, SSH and modern IPsec, and keep implementations current so new options (such as hybrid post-quantum key exchange) become available through upgrades.

6. Support transition modes

Plan for periods where old and new algorithms coexist: hybrid key exchange, dual or composite signatures, and re-encrypting stored data in the background. Design data migration paths before you need them.

7. Manage keys and certificates centrally

A certificate lifecycle management platform and a central KMS or HSM estate make it possible to reissue certificates and rotate keys at scale. Short certificate lifetimes, automated issuance (for example through the ACME protocol) and an accurate certificate inventory are agility in practice.

Agility is also a process

  • Inventory. Maintain a cryptographic bill of materials. See the migration roadmap.
  • Policy. A cryptographic standard listing approved, deprecated and prohibited algorithms, reviewed yearly.
  • Monitoring. Detect use of deprecated algorithms in scans and code analysis.
  • Rehearsal. Practise a change: rotate a root CA in a test environment, or switch a service's key-exchange group, and time it.

Procurement

Ask vendors:

  • Which algorithms do you support, and how do customers change them?
  • What is your roadmap for the NIST post-quantum standards?
  • Can cryptography be updated in the field, including firmware?
  • Will you provide a cryptographic bill of materials?

Prefer products that answer clearly. Agility you can't buy has to be built around, at greater cost.

Learn more

Crypto-agility is a theme of India's 2026 quantum-safe roadmap. See India's quantum-safe roadmap. For cryptography, PKI and secure architecture fundamentals, see the free CISSP and CCSP tracks.

Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.

Strengthen your crypto fundamentals

Cryptography lessons and practice questions in the free CISSP track.

Create a free account