The procurement gate: CNSA 2.0 and the 579-day clock
The average FIPS 140-3 cryptographic module certificate takes 579 days to emerge from the government’s validation queue. The National Security Agency’s procurement gate for new national-security-system acquisitions opened January 1, 2027. An organization that submitted its ML-KEM-1024 module for validation in mid-2026 will receive that certificate in early 2028, twelve months after the gate.
The gap was predictable. What created it goes back to September 10, 2022, when the NSA published Commercial National Security Algorithm Suite 2.0 — a list of algorithms and a timetable. The list dropped RSA and elliptic-curve cryptography entirely; in their place stood ML-KEM-1024 for key establishment, ML-DSA-87 for digital signatures, and hash-based schemes for firmware signing. The timetable ran to 2033, with category-by-category deadlines and one anchor date at the front: January 1, 2027. After that date, any new acquisition for a National Security System would have to arrive CNSA 2.0-compliant. No exceptions at delivery.
CNSA 2.0 replaced CNSA 1.0, the NSA’s 2015 cryptographic floor for NSS equipment. That suite had prescribed RSA at 3072 bits and elliptic curves on the P-384 curve — the same mathematics running most of the commercial internet. The 2022 update discarded both. ML-KEM-1024, built on equations in high-dimensional lattices, is designed to stay hard even after a capable quantum computer exists. NIST had not yet standardized these algorithms when CNSA 2.0 appeared; the final FIPS standards — 203, 204, and 205 — came in August 2024, two years later. CNSA 2.0 was, in effect, a procurement commitment made before the certified product existed.
The transition timeline is long and graduated: exclusive post-quantum use for firmware signing by 2025, networking equipment by 2030, cloud services by 2033. But the January 2027 procurement gate was the first hard enforcement point, and it arrived with a structural problem built in. Defense acquisition cycles run eighteen to thirty-six months. A program office writing solicitations in mid-2025 for systems delivered in early 2027 had to specify CNSA 2.0 requirements in that document, or the delivered system would arrive non-compliant the day it crossed the threshold. The gate does not grandfather contracts already in progress; it filters every new one.
Three deadlines compressed into five months through the autumn of 2026 to make the problem concrete. In September, existing FIPS 140-2 validations moved to Historical status, restricting what new procurements could use. In November, CMMC 2.0 Phase 2 enforcement began, requiring current FIPS 140-3 validation for defense contractors. In January 2027, the procurement gate activated. Each deadline collected the dependencies the previous one had created.
The organizations that read the September 2022 advisory, started their FIPS 140-3 submissions in early 2024, and got certificates before the gate are compliant. The ones that treated CNSA 2.0 as a 2030 concern are queued — hunting for waivers, scrambling for previously validated modules, or racing the remaining clock. The NSA published the advisory four years and three months before the deadline. For some vendors, it was not enough.
The cryptographic mathematics resolved in 2024; what remained was certification queues, acquisition cycles, and contract language. Cryptography has always had two phases: the mathematical breakthrough, and the decade of paperwork that makes it stick.
Sources
- Commercial National Security Algorithm Suite — Wikipedia — history of CNSA 1.0 (2015) and CNSA 2.0 (September 2022), algorithm specifications, transition rationale
- CNSA 2.0 and the 2027 Inflection Point — SafeLogic — procurement gate mechanics, acquisition cycle timelines, cascading deadline structure
- CNSA 2.0 January 2027 Procurement Gate — postquantum.com — FIPS 140-3 validation bottleneck (579-day median), September/November/January deadline compression, defense supply chain scope
- What Is CNSA 2.0? — Encryption Consulting — CNSA 1.0 vs. CNSA 2.0 comparison, algorithm parameter set choices, category-specific transition deadlines through 2033