Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
Rigidity has recognisable symptoms:
None of these is exotic. Most estates contain all six.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.