How is the cryptographic choice made — configurable, hard-coded, embedded in a product, or controlled by a third party?
Why it matters
Cryptographic risk becomes operational risk when change is difficult.
Algorithms can be deprecated, standards can change, vulnerabilities can emerge and quantum-safe migration can become necessary. The risk is not only whether weak cryptography exists, but how quickly affected services can move to an acceptable alternative.
Migration can be constrained by legacy applications, embedded algorithms, vendor roadmaps, unsupported protocols, certificate ecosystems, hardware dependencies, testing effort and business availability requirements. Crypto-agility reduces the friction and uncertainty around those changes.
Risk lens
Agility is not a binary property.
An organisation may be agile in one technology domain and highly constrained in another. Risk assessment should therefore focus on where change is slow, uncertain or dependent on factors outside direct control.
Risk lens
Two systems can use the same algorithm and have very different risk. One may support a controlled configuration change; the other may require a vendor release, hardware replacement, protocol redesign and coordinated downtime.
What alternatives are already supported, approved and interoperable?
How much testing, certification, downtime or coordinated change would a migration require?
Which vendors, platforms, hardware or external counterparties control the migration path?
Can old and new cryptography coexist temporarily during a staged transition?
How quickly can the organisation identify affected services and prioritise them by business impact?
What enables agility
Crypto-agility depends on more than configurable algorithms.
Visibility
A current view of cryptographic use and dependencies so affected services can be identified quickly.
Approved alternatives
Defined standards and transition options so teams know what they are allowed to move toward.
Flexible implementation
Designs that avoid unnecessary hard-coding and support controlled replacement of algorithms, libraries, keys or protocols.
Interoperability planning
Understanding whether clients, servers, partners and products can support a staged or hybrid transition.
Change & testing capability
Repeatable processes for validating security, functionality, performance and operational impact before migration.
Vendor readiness
Roadmaps, contractual expectations and lifecycle information for products that constrain cryptographic choices.
Governance connection
Agility must be governed before it is needed.
Reactive migration asks:
“What do we need to change now?”
Resilient governance asks:
“What would make future cryptographic change faster, safer and more predictable?”
This shifts crypto-agility from an emergency response concept to a design and governance principle. Architecture standards, procurement requirements, lifecycle decisions, supplier management and exception processes can all influence how difficult the next transition will be.
Evidence for risk management
What should Information Security Risk Management expect to see?
Migration constraintsKnown systems where cryptographic change is hard, slow or dependent on unsupported technology.
Supported alternativesEvidence of approved algorithms, protocols or product capabilities that can support transition.
OwnershipClear technical and business ownership for migration decisions, testing and risk acceptance.
Vendor dependencyRoadmaps, support statements, contractual commitments or documented uncertainty for critical suppliers.
Transition planningDefined approaches for coexistence, sequencing, rollback, interoperability and business continuity.
Agility metricsIndicators such as time-to-identify, time-to-plan, time-to-test and time-to-migrate for priority cryptographic changes.
Connection to quantum readiness
PQC makes crypto-agility visible — but the capability is broader than PQC.
NIST frames crypto-agility as the capability to replace and adapt cryptographic algorithms while preserving security and ongoing operations. The current post-quantum transition is a major driver because it exposes how deeply cryptography is embedded across systems and how difficult coordinated migration can be.
The same capability also supports future algorithm deprecation, vulnerability response, protocol changes and technology refresh.
Authoritative sources
Further reading
NIST CSRCCrypto Agility ProjectNIST CSWP 39upd1Considerations for Achieving Crypto Agility: Strategies and PracticesNIST NCCoEMigration to Post-Quantum Cryptography
This page synthesises public guidance for educational purposes. Source material should be consulted directly for normative requirements and implementation-specific guidance.