Crypto agility (also called cryptographic agility) is the ability to change the encryption algorithms, key sizes, keys and certificates your systems rely on quickly and safely, without redesigning the applications, devices and processes that use them. It is less a technology than a design and operating discipline: knowing where cryptography is used, keeping it configurable, and having a tested way to roll changes out.
At a glance
- Crypto agility is a capability, not a product: inventory, configurable design and a repeatable change process.
- It matters most when an algorithm has to be retired, such as the planned move to post-quantum algorithms.
- The hardest part is usually finding every place cryptography is used, including inside vendor products and devices.
- Certificate automation, central key management and up-to-date libraries make change much easier.
- Much of the work sits with vendors and service providers, so contracts and roadmaps matter.
What problem it solves
Cryptography ages. Algorithms that were standard a decade ago, such as SHA-1 for signatures or older versions of SSL, were eventually weakened and had to be replaced. Each time, organizations discovered that the algorithm was buried in applications, appliances, scripts and partner integrations, and that changing it meant code changes, firmware updates and outages. Replacements often took years, leaving weak cryptography in place long after it was known to be a problem.
The same problem now looms larger. Post-quantum cryptography (PQC) is expected to replace the public-key algorithms behind most secure connections, digital signatures and public key infrastructure (PKI). Organizations that can swap algorithms through configuration and automation will handle that change as a managed project. Those with hard-coded cryptography face a long, expensive hunt. Crypto agility also helps with smaller events: a compromised certificate authority, a vulnerable library, or a customer or regulator requiring a stronger setting.
How it works
Inventory. The starting point is a cryptographic inventory, sometimes called a cryptographic bill of materials: which protocols, algorithms, key lengths, certificates, libraries and hardware are used where, and who owns each. Discovery tools scan networks, code and certificate stores, but interviews and vendor questionnaires usually fill gaps.
Abstraction. Agile systems call cryptography through shared libraries, services or configuration rather than embedding a specific algorithm in application code. Changing the algorithm then means updating a library or a setting, not rewriting software. Protocols such as Transport Layer Security (TLS) already negotiate algorithms, which helps if both ends are kept current.
Central key and certificate management. Automated certificate lifecycle management (CLM) and centralized key storage, sometimes in a hardware security module (HSM), make it possible to reissue keys and certificates at scale instead of by hand.
Process and testing. A defined change process covers who decides an algorithm must go, how replacements are tested for compatibility and performance, how both old and new options are supported during a transition, and how the old option is finally switched off.
When it matters for buyers
- When planning for post-quantum cryptography. An inventory and agility assessment is the usual first step in a PQC roadmap.
- When buying long-lived systems. Devices, operational technology and software expected to run for ten years or more should be able to receive cryptographic updates.
- When certificate lifetimes shorten. Shorter public certificate lifetimes push organizations toward the automation that agility depends on.
- When customers or regulators ask. Some government guidance and large customers now ask suppliers about cryptographic inventories and transition plans; requirements vary by sector and country.
- After a cryptographic incident. A compromised key, certificate authority or library tests how quickly you can change course.
Questions to ask vendors
- Which algorithms, key sizes and protocols does your product use, and can we see that list?
- Can algorithms be changed through configuration or updates, or are they fixed in hardware or code?
- What is your roadmap for post-quantum algorithms, and how will existing customers receive them?
- How do you notify customers of cryptographic changes, and what do we have to change on our side?
- Do you support automated certificate issuance and renewal, and with which certificate authorities and protocols?
- Can your product help us discover and inventory cryptography across our environment?
Our governance, risk and compliance team helps buyers fold cryptographic inventory and transition planning into wider risk programs.
How it differs from post-quantum cryptography
Post-quantum cryptography is a set of new algorithms designed to resist attacks from future quantum computers. Crypto agility is the ability to move from one algorithm to another, whatever the reason. PQC is the most prominent reason to build agility right now, but they are different things: an organization could adopt PQC in a single painful, one-off migration without becoming agile, and an agile organization will still need agility long after its PQC migration is finished. In practice, the two are planned together, because the inventory and automation work that agility needs is the same work a PQC migration needs. Agility also applies to symmetric encryption and hashing, not only to the public-key algorithms that PQC replaces.