Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Crypto Agility?

Crypto agility is the ability to replace an algorithm, key length, or protocol version across your systems quickly and without redesigning them. It is an architecture property, not a product.

Illustration for the cybersecurity term Crypto Agility
Home / Blog / Cybersecurity Terms / What Is Crypto Agility?
17 November 2026

What Is Crypto Agility?

What Is Crypto Agility?

Every cryptographic algorithm in use today will eventually be withdrawn. MD5 and SHA-1 were retired, DES and 3DES were retired, SSL 3.0 and TLS 1.0 were retired, and RSA and elliptic curves are now scheduled for replacement. Crypto agility is the discipline of building systems so that each of those transitions is a configuration change and a deployment, rather than a rewrite.

Organisations usually discover whether they have it at the worst moment. A certificate authority announces that it will stop issuing SHA-1 certificates, or a regulator sets a deadline, and someone has to find every place an algorithm name was compiled into a binary ten years ago.

What Makes a System Rigid

Rigidity has recognisable symptoms:

None of these is exotic. Most estates contain all six.

The Patterns That Buy You Agility

  1. Version every ciphertext. Prefix stored data with an identifier for the algorithm, mode, and key version. Migration then becomes decrypt-with-old, encrypt-with-new, performed lazily on access or in a background job, rather than a flag day.
  2. Centralise cryptographic operations. A shared library or an internal encryption service means one place to change, one place to audit, and one place to measure usage. Envelope encryption through a key management service fits this pattern well.
  3. Separate key material from key reference. Applications should hold key identifiers, not keys, so that rotation and algorithm change are invisible to the application.
  4. Negotiate rather than fix. Protocols that advertise supported suites, such as TLS, let both ends move independently. Bespoke protocols with a single hard-coded cipher cannot.
  5. Write migration into the contract. Supplier agreements and procurement requirements should state that the product will support new algorithms within a defined period, because much of your cryptography is not yours to change.

Why This Became Urgent

The driver is the post-quantum transition. NIST published the first post-quantum standards in August 2024, and the NCSC has set out a timeline in which UK organisations should have completed discovery by 2028 and migration of high-priority systems by 2031, with the remainder by 2035. That is the largest cryptographic change the industry has attempted, and it affects key exchange, signatures, certificates, hardware roots of trust, and every protocol built on them.

It is also not the last one. Agility is worth building because the next deprecation is always coming, whether it is driven by cryptanalysis, by regulation, or by an incident at a supplier.

Start With an Inventory

You cannot change what you cannot see, and almost no organisation has a reliable picture of its own cryptography. A cryptographic bill of materials records, for each system, which algorithms and key lengths are in use, where keys are stored, who owns them, which certificates and protocols are involved, and how long the protected data must stay confidential. Sources include TLS scanning of internal and external endpoints, static analysis of source for crypto API calls, certificate inventories, key management service logs, and vendor documentation.

NIST’s own guidance on the migration, published as draft NIST IR 8547, treats discovery as the first and longest phase for precisely this reason. Prioritise by data lifetime: anything that must stay confidential beyond 2035 is already exposed to harvest now, decrypt later collection and should move first.

Agility Has Limits

Hardware is the hard case. Smart cards, HSMs, TPMs, vehicle ECUs, smart meters, and industrial controllers often implement algorithms in silicon and cannot be upgraded in the field. For those, agility means planning the replacement cycle rather than the configuration change, and that planning has to start years earlier.

There is also a failure mode in the other direction. A system that accepts any algorithm a client offers is not agile, it is permissive, and it will happily negotiate a weak suite with an attacker. Agility means being able to change quickly while enforcing a single strict policy at any given moment. Our cyber risk analysis services include cryptographic discovery and prioritisation, which is usually the step that turns a vague migration ambition into a dated plan.

FAQ – Frequently Asked Questions

Is Crypto Agility a Product I Can Buy?

No, although key management platforms, certificate lifecycle tools, and discovery scanners all help. Agility is a property of how your systems are designed and operated: whether algorithms are configurable, whether ciphertext is versioned, whether keys are centrally managed, and whether suppliers are contractually obliged to keep up. Tools support those decisions; they do not replace them.

Where Should an Organisation Start?

With discovery. Scan external and internal TLS endpoints, inspect code for cryptographic API calls, pull certificate and key inventories, and ask suppliers what their products support. Then rank systems by how long their data must remain confidential and how hard they are to change. The slow, hard, long-lived systems are the ones to start planning first.

Does Crypto Agility Mean Supporting Many Algorithms at Once?

Only during transitions. Supporting several algorithms permanently widens the attack surface and invites downgrade attacks. The goal is a single enforced policy at any point in time, plus the ability to change that policy quickly. Hybrid key exchange during the post-quantum move is a deliberate, time-limited exception to that rule.

How Long Does a Cryptographic Migration Take?

In large estates, years. The SHA-1 to SHA-256 transition took the industry roughly a decade, and that affected only hashing and certificates. The post-quantum move touches key exchange, signatures, PKI, hardware, and supplier products at once, which is why national guidance sets milestones in 2028, 2031, and 2035 rather than months.

Related Terms

You May Be Interested In These

What Is an Advanced Persistent Threat (APT)?

Cybersecurity Terms

17 November 2026

What Is an Advanced Persistent Threat (APT)?

Read More
What Is Breach and Attack Simulation?

Cybersecurity Terms

17 November 2026

What Is Breach and Attack Simulation?

Read More
What Is a Business Impact Analysis?

Cybersecurity Terms

17 November 2026

What Is a Business Impact Analysis?

Read More