CNSA 2.0 algorithms and timeline

The NSA's Commercial National Security Algorithm Suite 2.0 is the most specific post-quantum timeline in force. It binds U.S. national security systems, and it shapes the products their vendors sell worldwide.

What CNSA 2.0 is

The Commercial National Security Algorithm Suite 2.0 is the NSA's set of approved algorithms for U.S. national security systems (NSS), announced in September 2022 and updated after NIST finalised its post-quantum standards ^[1]. NSA's FAQ states that it intends all NSS to be quantum-resistant by 2035, in line with the goal of National Security Memorandum 10 ^[2]. NSM-10, signed on 4 May 2022, directs U.S. government agencies to migrate vulnerable cryptographic systems to quantum-resistant cryptography ^[3].

The algorithms

Sources: NSA advisory ^[1]; summary ^[4]. NSA's FAQ recommends LMS with SHA-256/192 for firmware signing and requires validated implementations for NSS signers ^[2].

Category timeline

Sources: NSA advisory ^[1]; summary ^[4].

Acquisition and enforcement dates

NSA's FAQ (version 2.1, December 2024) adds dates that matter for procurement ^[2]:

• NSS validated against a NIAP or CSfC profile remain approved for the life of that validation, and no transition requirement is enforced before 31 December 2025.
• By 1 January 2027, all new acquisitions for NSS will be required to be CNSA 2.0 compliant unless otherwise noted.
• By 31 December 2030, equipment and services that cannot support CNSA 2.0 must be phased out unless otherwise noted.
• By 31 December 2031, CNSA 2.0 algorithms are mandated for use unless otherwise noted.

Positions worth knowing

• Hybrid. NSA has confidence in standalone CNSA 2.0 algorithms and does not require hybrid solutions for security, though interoperability may require them in limited cases ^[2]. This differs from some other agencies' guidance.
• QKD. NSA does not generally consider quantum key distribution a practical security solution for protecting NSS ^[2].

Who should care outside the U.S.

CNSA 2.0 applies to U.S. national security systems, but vendors that sell to them build products to its requirements. Suppliers in India and elsewhere that serve U.S. defence customers will see the 2027 acquisition date in contracts. Others can use CNSA 2.0 as a reference for the strictest parameter choices.

The dates are also stricter than NIST's draft transition timeline in places. NIST IR 8547 proposes disallowing quantum-vulnerable algorithms after 2035 ^[5], while CNSA 2.0 expects exclusive use of quantum-resistant algorithms for signing and networking equipment by 2030. Where both apply, plan to the CNSA 2.0 date. A side-by-side view is in post-quantum compliance timelines.

Mapping CNSA 2.0 into a QBOM

1. Tag each asset with its CNSA 2.0 category (signing, networking, operating system and so on).
2. Check the parameter set, not just the algorithm: ML-KEM-768 or ML-DSA-65 does not meet CNSA 2.0 (see NIST PQC standards).
3. Set the category's exclusive-use year as the due date, and flag any supplier roadmap that misses it.
4. For firmware signing, link the signing key to the devices that trust it through the HBOM.

How IntelliXBOM helps

IntelliXBOM maps cryptographic and hardware inventory to framework controls, including CNSA 2.0, and produces timestamped evidence of compliance status. It correlates algorithms and parameter sets with the software, firmware and devices that use them, and keeps version history as categories migrate. This article summarises public guidance and is not legal advice; confirm requirements with NSA and your contracting authority.