Articles

CNSA 2.0 Requirements, Algorithms, and Timelines Explained

See the algorithms CNSA 2.0 requires for National Security Systems, key deadlines from 2027 to 2031, and how to start preparing.

Q Marketing
Q Marketing
|
Nov 17, 2026
CNSA 2.0 timeline from 2027 to 2033, shown as glass cubes along a path with the 2027 milestone highlighted

If you supply technology to the US defense or intelligence community, or use NSA guidance as a yardstick for your own post-quantum planning, CNSA 2.0 is probably already on your desk. It names the exact algorithms National Security Systems must use and sets binding dates, starting with a procurement gate on January 1, 2027. For PQC leads and compliance teams, the real work is turning those requirements into an inventory, a plan, and evidence. This guide explains what CNSA 2.0 is, how it fits into wider US policy, which algorithms it requires, and what the key dates are, and finishes with some practical first steps.

Key Takeaways

  • CNSA 2.0 is the NSA's quantum-resistant algorithm suite for National Security Systems (NSS), announced in 2022 and refined several times since.
  • It allows only the strongest parameter sets, meaning Category 5 lattice-based algorithms for key establishment and signatures, AES-256, SHA-384 or SHA-512, and stateful hash-based signatures for firmware.
  • New NSS acquisitions must support CNSA 2.0 from January 1, 2027; equipment that can’t support it must be phased out by December 31, 2030, and CNSA 2.0 is mandated across NSS by December 31, 2031.
  • It's only mandatory for NSS and their suppliers, although some commercial organizations use it as a reference point.
  • Preparation starts with inventory, because you can't map systems to deadlines without knowing what cryptography they use.

What Is CNSA 2.0 (Commercial National Security Algorithm Suite 2.0)?

CNSA 2.0 is the set of quantum-resistant cryptographic algorithms the National Security Agency (NSA) approves for protecting National Security Systems. NSA announced it in September 2022 as the replacement for CNSA 1.0, whose public-key algorithms (RSA, Diffie-Hellman and elliptic-curve cryptography) a future cryptanalytically relevant quantum computer (CRQC) could break.

It applies to NSS owners and operators, including classified networks and systems supporting military, intelligence and defense functions, and to the vendors whose products and services protect those systems. NSA also addresses the Defense Industrial Base with its guidance.

In its CNSA 2.0 FAQ, NSA says it isn't dictating algorithms to organizations outside NSS, and the Defense Industrial Base gets guidance, not requirements. Its influence reaches further in practice, since named algorithms and concrete dates make CNSA 2.0 a reference point for some financial institutions, critical infrastructure operators and technology vendors, especially the ones that sell to the government.

How CNSA 2.0 Fits With NSM-10 and NIST PQC Standards

CNSA 2.0 sits inside a wider US policy picture that includes several other pieces:

  • NSM-10 (National Security Memorandum 10, May 2022) set 2035 as the goal for moving federal systems to quantum-resistant cryptography, and CNSA 2.0 aims for most NSS to finish earlier than that.
  • NIST PQC standards supply the algorithms. NSA picked CNSA 2.0's public-key algorithms from the standards NIST finalized in August 2024 (FIPS 203 and FIPS 204) and added NIST's stateful hash-based signatures from SP 800-208.
  • NIST IR 8547, finalized in October 2026, is NIST's broader transition plan, deprecating quantum-vulnerable public-key algorithms after 2030 and disallowing them after 2035 (NIST IR 8547).
  • Executive Order 14412 (June 2026) sets earlier dates for federal high-value assets and high-impact systems outside NSS, with PQC key establishment due by 2030 and PQC signatures by 2031, as NIST summarizes.
  • CNSSP 15, the Committee on National Security Systems policy that specifies algorithms for NSS, is the binding instrument and has been updated to incorporate CNSA 2.0.

Put simply, NIST sets the standards, NSA picks the strictest options for NSS and CNSSP 15 makes them binding. Organizations that run both NSS and non-NSS systems, defense contractors for example, often end up on two tracks, with NIST-based plans for corporate IT and CNSA 2.0 for the products and systems they deliver into national security programs.

The CNSA 2.0 Algorithms

CNSA 2.0 keeps the symmetric algorithms from CNSA 1.0 and swaps the public-key algorithms for quantum-resistant ones. NSA specifies ML-KEM-1024 and ML-DSA-87 for every classification level.

AlgorithmPurposeSpecificationParameters
AESSymmetric encryptionFIPS 197256-bit keys
ML-KEM-1024Key establishmentFIPS 203Category 5
ML-DSA-87Digital signatures, any use caseFIPS 204Category 5
SHA-384 / SHA-512HashingFIPS 180-4Either
SHA-3Internal hardware integrity only, such as boot integrity checksFIPS 202SHA3-384 or SHA3-512
LMSSoftware and firmware signingNIST SP 800-208All; LMS SHA-256/192 recommended
XMSSSoftware and firmware signingNIST SP 800-208All

‍

Each one has a specific job in practice.

  • ML-KEM (formerly CRYSTALS-Kyber) protects session keys when two systems set up a secure connection, such as in TLS or IPsec. This is where harvest now, decrypt later (HNDL) risk sits, because captured key exchanges could be broken later.
  • ML-DSA (formerly CRYSTALS-Dilithium) signs and verifies data, certificates, software and firmware.
  • LMS and XMSS are stateful hash-based signatures. NSA wants firmware signing to move first because firmware verification code is often fixed for the whole life of a device, and both algorithms need careful state management, ideally in hardware such as an HSM.
  • AES-256 and SHA-384/512 remain quantum-resistant at these sizes, so most symmetric cryptography can stay as it is.

It's just as useful to know what's left out. NSA doesn't approve SLH-DSA (FIPS 205), the multi-tree variants HSS and XMSSMT (multi-tree), or larger RSA and ECC keys for NSS, and it has no plans to add future NIST PQC standards such as FN-DSA to the suite.

The CNSA 2.0 Timeline

NSA's original 2022 guidance set dates by technology category, and each category has two milestones. Use it to sequence the work, and take your deadlines from the binding milestones below. The "support and prefer" date is when CNSA 2.0 should be available and the default, and the "exclusive use" date is the point after which only CNSA 2.0 is accepted.

Technology categorySupport and prefer byExclusively use by
Software and firmware signing2025 (begin immediately)2030
Web browsers, servers and cloud services20252033
Traditional networking equipment (VPNs, routers)20262030
Operating systems20272033
Niche equipment (constrained devices, large PKI systems)20302033
Custom applications and legacy equipmentUpdate or replace2033

‍

NSA's CNSA 2.0 FAQ (version 2.2, October 2026) restates the binding CNSSP 15 milestones to plan against:

  • January 1, 2027: all new NSS acquisitions must be CNSA 2.0 compliant, unless otherwise noted.
  • December 31, 2030: equipment and services that can't support CNSA 2.0 must be phased out.
  • December 31, 2031: CNSA 2.0 algorithms are mandated for use across NSS, unless otherwise noted.
  • 2035: the NSM-10 goal for all NSS to be quantum-resistant.

In practice, the 2027 procurement gate is what drives action now, because anything bought today will still be in service well past 2030, and that's the main point to take away from the CNSA 2.0 timeline.

How to Prepare for CNSA 2.0 Compliance

Whether CNSA 2.0 binds you directly or you're using it as a benchmark, the first steps look much the same.

  1. Confirm your scope. Identify which systems qualify as NSS, which products you sell into NSS, and which contracts carry CNSA 2.0 clauses, and treat everything else as a reference case.
  2. Build the inventory. Find where public-key cryptography is used across code, certificates, PKI, protocols, and firmware, then map each use to its CNSA 2.0 category and deadline. A PQC readiness assessment is a good way to structure the work.
  3. Prioritize by business risk and deadline. For NSS work, firmware roots of trust and long-lived systems come first, followed by networking equipment due by 2030, with everything weighted by the business impact of what it protects.
  4. Plan remediation in waves, grouping the work by category and deadline with owners, milestones and validation criteria. Our guide to post-quantum cryptography migration covers the planning steps in more detail.
  5. Engage vendors early. Ask suppliers for dated CNSA 2.0 roadmaps and confirm they'll ship the required parameter sets instead of lower-strength defaults.
  6. Track evidence. Keep a record that links each system to its algorithms, its deadline, and proof of the fix, so you can show progress against PQC compliance requirements to auditors and customers.

If you don't supply NSS, CNSA 2.0 still works as a planning benchmark. Its category view is a useful checklist for your own plan; the order of work should still follow your business risk and HNDL exposure, which often puts external data in motion first.

CNSA 2.0 won't be the last mandate either. Requirements keep evolving, and other frameworks bring their own dates, which is why it pays to run PQC as a continuous program instead of a one-off response.

Q.security is built for exactly that. The Q platform turns PQC remediation into a business-first program you run over a single system of record, and because your assets are already inventoried and business-scored, a new mandate becomes a re-run of the program where you update priorities against the new deadlines and drive the next wave from discovery to done. Q provides regulatory context starting with the NIST PQC standards.

FAQ

What is the difference between CNSA 1.0 and CNSA 2.0?

CNSA 1.0 relies on RSA, Diffie-Hellman and elliptic-curve cryptography for public-key functions, all of which a quantum computer could break. CNSA 2.0 replaces them with quantum-resistant lattice-based and hash-based algorithms, while the symmetric side (AES-256 and SHA-384) stays largely the same, with SHA-512 now allowed as well.

Is there a CNSA 2.1 or CNSA 2.2?

No. CNSA 2.0 is still the current algorithm suite. The version numbers you'll see belong to NSA's CNSA 2.0 and Quantum Computing FAQ, which NSA revises as standards and policy change, most recently as version 2.1 in December 2024 and version 2.2 in October 2026.

Does CNSA 2.0 allow hybrid cryptography?

Yes, in specific cases. NSA doesn't require hybrid solutions because it has confidence in the CNSA 2.0 algorithms. It allows them in the exceptions it specifically recommends for standardization or interoperability reasons, with IKEv2 the named example. CNSA 2.0 algorithms still have to be selected by each deadline.

Is quantum key distribution part of CNSA 2.0?

No. NSA doesn't consider quantum key distribution (QKD) a practical security solution for National Security Systems, partly because it only handles key distribution, covers a limited set of threats and needs significant engineering changes. NSA advises NSS owners not to use QKD without consulting the agency directly.

Who enforces CNSA 2.0?

NSA sets CNSA 2.0 requirements for National Security Systems and CNSSP 15 makes them binding. Authorizing officials report on adoption under NSM-10, and NIAP validation of commercial products used in NSS will generally require CNSA 2.0 compliance. Suppliers usually meet the requirement through contract clauses.

Prepare for the Next Mandate

Start with your public footprint and a few applications, identify your highest priorities and get an actionable plan for your first remediation wave. Talk to Q.security.

‍

On this page

Remediate now.
Stay secure.

Get a Demo

See Q in context

Scan your public footprint

Plan your first wave