The Crypto Agility Maturity Model: 5 Levels, and Where Most Teams Actually Sit
A practical 5-level maturity model for crypto agility, what separates each level, and how it lines up with the four-tier model NIST sketches in CSWP 39.

- Crypto agility is the ABILITY to swap cryptographic algorithms quickly. A CBOM is the INVENTORY of what you have. You need the inventory first; agility is what you build on top of it.
- NIST's final CSWP 39 (December 2025, updated June 2026) sketches a four-tier crypto agility maturity model adapted from its Cybersecurity Framework, while noting no single model fits every organization.
- The most granular framework is CAMM, a 5-level academic model from Hochschule Darmstadt (0 Initial through 4 Sophisticated), but it ships no self-assessment tool teams can run against it.
- In our experience, most organizations sit at Level 1 or 2: they know roughly what cryptography they use, but swapping an algorithm still means a multi-quarter project, not a config change.
- FIPS 203, 204, and 205 (ML-KEM, ML-DSA, SLH-DSA) were finalized on August 13, 2024. The algorithms you'll need to migrate to already exist. Agility is what determines how fast you actually can.
Ask a security team how long it would take to replace every use of RSA in their stack with a post-quantum algorithm, and you'll usually get a long pause before a guess. Not because nobody knows RSA is there. Because nobody's ever actually tried to swap it out at scale, and there's no map for how hard that would be. That gap, between knowing your cryptography and being able to change it fast, is what crypto agility measures.
Crypto agility is the ability to replace or update cryptographic algorithms, keys, and protocols across your systems without a multi-year rebuild. It's not a tool you buy. It's a capability you build, and like any capability, some organizations have more of it than others. This is a maturity model for figuring out where you actually stand, and what the next level looks like.
Crypto agility isn't the same thing as a CBOM, and mixing them up costs you time
These two get confused constantly, and it's an easy mistake to make since they're both about managing your cryptography. But they answer different questions, and one is a prerequisite for the other.
| CBOM (cryptographic inventory) | Crypto agility | |
|---|---|---|
| Question it answers | What cryptography do we have? | How fast can we change it? |
| What it produces | A list: algorithms, keys, certificates, protocols | A capability: modular crypto, no hardcoded algorithm IDs, tested rollback |
| Where it sits | Foundational, done first | Built on top of the inventory |
| Failure mode without it | You don't know what to migrate | You know what to migrate, but it takes 18 months per system |
NIST draws this same line in its own white paper on the subject (CSWP 39, final December 2025). Crypto agility, in NIST's words, refers to "the capabilities needed to replace and adapt cryptographic algorithms in protocols, applications, software, hardware, firmware, and infrastructures while preserving security and ongoing operations." Notice what's missing from that definition. An inventory. It's assumed. Agility is what you do once you already have one.
NIST sketches a maturity model, but not a scoring tool
Here's the part that surprises people. NIST doesn't hand you a ready-made, scored model. Its final Considerations for Achieving Crypto Agility (CSWP 39, December 2025, updated June 2026) says "there is not a single crypto maturity model that effectively serves all needs," and tells organizations to adapt their existing risk frameworks. It then sketches four tiers adapted from the NIST Cybersecurity Framework: Partial, Risk-Informed, Repeatable, and Adaptive.
Read that carefully: NIST's tiers are organization-level criteria you adapt to your own risk framework, not a certification. If a vendor tells you they follow "the NIST crypto agility maturity model," ask which tier criteria they actually measure against.
If you want levels you can apply system by system, there's a second framework, and NIST cites it. It's just not from NIST.
The more granular maturity model: CAMM
CAMM (the Crypto-Agility Maturity Model) comes out of the UCS Research Group at Hochschule Darmstadt, a German university. Version 1.1 was published in September 2022. It defines five levels. Even if you never adopt the model wholesale, they're worth knowing, because they map cleanly onto real organizational states.
- Level 0, Initial: the default state. At least one system violates the basic conditions for agility, usually meaning algorithms are hardcoded somewhere with no abstraction layer.
- Level 1, Possible: the foundational conditions are met. Systems are theoretically capable of swapping cryptography, but nothing has been tested end to end.
- Level 2, Prepared: agility measures exist, but preparatory work remains before you could actually execute a swap under pressure.
- Level 3, Practiced: migration between cryptographic methods is demonstrably, effectively, and securely feasible. You've done it, not just planned for it.
- Level 4, Sophisticated: advanced agility capabilities, applied consistently across your broader infrastructure, not just one system.
CAMM is rigorous. It's real academic work, not marketing. What it isn't is operational. There's no self-assessment questionnaire a security team can run through in an afternoon. There's no benchmark against peer organizations. We haven't found vendor tooling built around it. It's a model you'd cite in a paper, not one you'd hand to your engineering team on a Monday.
“The gap isn't a missing framework. It's a missing bridge between the academic model and a Tuesday-afternoon self-assessment your team can actually run.”
Where most organizations actually sit
In our experience, most teams land at Level 1 or the low end of Level 2 on a model like CAMM's, and it's worth being specific about what that looks like, because "we're pretty agile" is doing a lot of unearned work in most conversations.
- Level 0 signs: cryptographic algorithm names are hardcoded in application code with no configuration layer. Nobody can tell you every place RSA-2048 is used without a manual audit.
- Level 1 signs: you have a partial inventory (maybe a CBOM), you know roughly where your cryptography lives, but no system has ever had its cryptography swapped without a code change and a full regression cycle.
- Level 2 signs: some systems use crypto-agnostic libraries or configurable algorithm selection, but it's inconsistent across the estate, and a full swap would still take a dedicated project, not a deployment.
- Level 3 signs (rare): you've actually executed at least one algorithm migration end to end, on a live system, and documented what broke and what didn't.
- Level 4 signs (very rare): agility is a design requirement enforced at build time, not a retrofit, across your whole environment, not one flagship system.
If you can't answer "how long would it take to replace SHA-256 across our estate" without convening a meeting, you're not past Level 1, no matter how confident the answer to "do we know our cryptography" was.
Why the gap matters now, not in 2030
The algorithms you'll eventually need to migrate to already exist. NIST finalized FIPS 203 (ML-KEM, for key establishment), FIPS 204 (ML-DSA, for digital signatures), and FIPS 205 (SLH-DSA, a stateless hash-based signature scheme) on August 13, 2024. The math is done. What isn't done, for most organizations, is the operational muscle to actually deploy a new algorithm without a year-long project.
That's the entire point of measuring agility separately from inventory. You can have a perfect CBOM and still be months away from a real migration if every algorithm change requires touching application code, re-certifying a compliance boundary, and coordinating a dozen teams. Agility is what collapses that timeline.
A practical self-assessment, in the absence of a formal one
Until a vendor or standards body ships a real interactive assessment, here's a rough, honest way to place yourself using the CAMM levels above. Answer these in order and stop at the first one you can't confidently answer yes to.
- Do you have a current, accurate inventory of every cryptographic algorithm, key, and protocol in use across your systems? (No: you're at Level 0. This is the CBOM step, and it comes first.)
- Is that cryptography abstracted behind a configuration layer, or is it hardcoded into application logic? (Hardcoded: Level 0 to 1. Configurable in at least some systems: Level 1 to 2.)
- Have you tested swapping an algorithm on a non-production system and measured what broke? (Never: Level 1 to 2. At least once: Level 2 to 3.)
- Have you executed a real algorithm migration on a production system, end to end, with a documented rollback plan? (Level 3.)
- Is agility a build-time requirement for new systems, enforced by policy, not left to individual teams? (Level 4, and genuinely rare.)
Most teams stop at question two or three. That's not a failure. It's an honest starting point, and it tells you exactly what the next investment should be: not another inventory tool, but a rehearsed migration.
The bottom line
Crypto agility and a cryptographic inventory get talked about as if they're the same project. They're not. The inventory tells you what you have. Agility tells you how fast you can act on it, and right now, there's no settled industry framework for measuring that. NIST's four tiers are a high-level sketch, and CAMM is academic, not operational. Until that changes, the honest move is to run the five questions above against your own environment, be specific about where you actually land, and treat the gap between "we know our cryptography" and "we can change it in a weekend" as the real project.
Frequently asked questions
What is a crypto agility maturity model?
+
What's the difference between crypto agility and a CBOM?
+
Does NIST have an official crypto agility maturity model?
+
What is CAMM (Crypto-Agility Maturity Model)?
+
What level of crypto agility maturity are most organizations at?
+
Why does crypto agility matter if post-quantum algorithms already exist?
+
Sources
- https://csrc.nist.gov/pubs/cswp/39/considerations-for-achieving-cryptographic-agility/2pd
- https://camm.h-da.io/model/
- https://csrc.nist.gov/pubs/fips/203/final
- https://csrc.nist.gov/pubs/fips/204/final
- https://csrc.nist.gov/pubs/fips/205/final
- https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.39-upd1.pdf
- https://csrc.nist.gov/pubs/cswp/39/considerations-for-achieving-cryptographic-agility/final