RegionUnited States · NSA · NIST · OMB

US national-security purchases go post-quantum on 1 January 2027

The United States has several layers of post-quantum rules: NSA's CNSA 2.0 for national security systems, an executive order and OMB memorandum for federal agencies, and NIST's standards and transition dates, which much of industry follows through FIPS validation and federal procurement.

—Days
—Hours
—Minutes
—Seconds

To 1 January 2027, Eastern time — CNSA 2.0 required in all new national-security-system acquisitions.

The timeline

Each date is labelled by what kind of instrument sets it: BindingGuidanceProposalRecommendation

  1. 4 May 2022

    NSM-10 Binding

    Directs agencies, with the goal of mitigating “as much of the quantum risk as is feasible by 2035” and an annual inventory of vulnerable federal systems. White House archive

  2. 21 Dec 2022

    Quantum Computing Cybersecurity Preparedness Act Binding

    Federal agencies must maintain an inventory of IT vulnerable to quantum decryption and plan their migration (Pub. L. 117-260). GovInfo

  3. 13 Aug 2024

    NIST publishes FIPS 203, 204 and 205 Binding

    ML-KEM, ML-DSA and SLH-DSA become Federal Information Processing Standards. NIST

  4. 22 Jun 2026

    Executive Order 14412 Binding

    “Securing the Nation Against Advanced Cryptographic Attacks”: dated post-quantum deadlines for federal high-value and high-impact systems, a NIST pilot, and a contractor rule to be proposed. White House

  5. 22 Oct 2026

    Agency migration plans due Binding

    OMB M-26-15 required each agency's PQC migration plan within 120 days. OMB

  6. 27 Oct 2026

    NIST IR 8547 final Guidance

    Quantum-vulnerable public-key cryptography deprecated after 2030 and disallowed after 2035. NIST

  7. Dec 2026

    FAR contractor rule to be proposed Proposal

    EO 14412 directs the FAR Council to propose, within 180 days, a rule requiring covered contractors to comply with NIST FIPS, including the PQC standards, by 31 December 2030. Not yet published. EO 14412

  8. 1 Jan 2027

    CNSA 2.0 for new NSS acquisitions Binding

    “CNSA 2.0 algorithms will be required in all new acquisitions for NSS.” NSA CNSA 2.0 FAQ

  9. 2 Jan 2030

    Agencies support TLS 1.3 Binding

    Agencies must support TLS 1.3 or a successor “not later than January 2, 2030”. OMB M-26-15

  10. 31 Dec 2030

    Federal key establishment; NSS phase-out Binding

    High-value assets and high-impact systems use PQC for key establishment (EO 14412). NSS equipment that cannot support CNSA 2.0 is phased out unless excepted. EO 14412

  11. 31 Dec 2031

    Federal signatures; CNSA 2.0 mandated Binding

    The same federal systems use PQC for digital signatures (EO 14412), and CNSA 2.0 algorithms are mandated for use in NSS. NSA CNSA 2.0 FAQ

  12. 2035

    RSA and ECC disallowed Guidance

    NIST deprecates quantum-vulnerable public-key cryptography after 2030 and disallows it under its standards after 2035; NSM-10's 2035 goal for federal migration stands. NIST IR 8547

National security systems: CNSA 2.0

NSA's Commercial National Security Algorithm Suite 2.0 binds national security systems (NSS) and the vendors that sell into them. Its FAQ (v2.2, October 2026) quotes the binding dates from CNSS Policy 15: CNSA 2.0 required in all new NSS acquisitions by 1 January 2027, non-compliant equipment phased out by 31 December 2030, and CNSA 2.0 mandated for use by 31 December 2031. It adds that from 2027 “no new product for NSS should have a burned-in root of trust relying on a non-QR primitive”, and that the federal deadlines in EO 14412 do not change CNSS Policy 15.

FunctionCNSA 2.0 requirement
Key establishmentML-KEM-1024, for all classification levels
Digital signaturesML-DSA-87, for all classification levels
Firmware and software signingLMS or XMSS (NIST SP 800-208); HSS and XMSSMT not allowed
Symmetric and hashingAES-256; SHA-384 or SHA-512

NSA's original 2022 advisory also gave “support and prefer by” / “exclusively use by” years by product type — for example 2025 and 2030 for software and firmware signing, and 2025 and 2033 for web browsers, servers and cloud services — with NSS transition expected to be complete by 2035. The current FAQ no longer carries that table; the dates above are the binding ones.

Federal agencies: EO 14412 and OMB M-26-15

The federal timeline was reset in June 2026. Executive Order 14412 (signed 22 June 2026) requires OMB guidance that moves high-value assets and high-impact systems to PQC key establishment by 31 December 2030 and PQC digital signatures by 31 December 2031. It excludes national security systems, which CNSA 2.0 covers.

OMB M-26-15 (24 June 2026) operationalises it: the objective is “mitigating as much quantum risk as feasible by December 31, 2030”; agency migration plans were due within 120 days; the work runs in five phases from inventory and strategy (2026–27) through pilots, key establishment, signatures (2031) and full migration (2035); and plans must align with NIST IR 8547. Agencies are pointed to automated inventory that feeds a cryptographic bill of materials, and EO 14412 tells CISA to publish minimum elements for one.

This builds on earlier steps: OMB M-23-02 (annual prioritised inventories from May 2023 until 2035), EO 14144 (January 2025) and EO 14306 (June 2025), which kept the TLS 1.3 deadline of 2 January 2030 and the CISA product-category list. A July 2024 White House report to Congress put the cost of migrating prioritised non-national-security federal systems between 2025 and 2035 at about $7.1 billion in 2024 dollars.

NIST: the standards everyone inherits

NIST published FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) on 13 August 2024. The final NIST IR 8547 (27 October 2026) deprecates quantum-vulnerable public-key cryptography after 2030 and disallows it under NIST standards after 2035, regardless of key size, while noting that this window does not relax the earlier federal deadlines. A standard for FN-DSA (FIPS 206) and one for HQC are still under development. More in our glossary and algorithm explorer.

Contractors and vendors

Section 6(c) of EO 14412 directs the FAR Council to publish, within 180 days, a proposed rule requiring covered contractors to comply with NIST FIPS, including the post-quantum standards, by 31 December 2030. As of 8 November 2026 no proposed rule has been published, and “covered contractors” will be defined in the rulemaking. Meanwhile CISA's product-category list tells buyers that where PQC-capable products are widely available, they “should plan acquisitions to procure only PQC-capable products in that category”, and CNSA 2.0 already reaches the defence industrial base through NSS acquisitions.

Financial services

No US financial regulator has a binding post-quantum requirement. The OCC's June 2026 cybersecurity report says banks “should consider how to effectively monitor developments in quantum computing”; NYDFS's September 2026 industry letter asks that risk assessments consider “advances in quantum computing”; and Treasury's G7 roadmap statement is explicitly “not prescriptive”.

Where KavachQ fits

Every framework on this page starts in the same place: know where your cryptography is, rank it by risk, plan the move, and be able to show the evidence.

  • Inventory. KavachQ Discover builds a CycloneDX 1.7 CBOM from live TLS and SSH probes, an in-network collector, code, configuration, keystores and certificates, and exports from cloud, HSM and other platforms.
  • Risk ranking. A T1–T4 quantum-risk tier for every asset, weighing harvest-now-decrypt-later exposure, and a 0–100 PQC-Ready score for each scan.
  • Plan. KavachQ Migrate builds a phased P0 / P1 / P2 plan with a replacement algorithm for each asset. For national security systems, check the plan against CNSA 2.0's parameter sets (ML-KEM-1024, ML-DSA-87); KavachQ's own signatures use ML-DSA-65.
  • Evidence. KavachQ Seal signs the CBOM with ML-DSA-65 (FIPS 204), verifiable offline against our published trust anchor.
  • Your environment. Self-hosted in your VPC, on-premises or air-gapped; your inventory stays inside your boundary.

KavachQ does not certify compliance with any framework on this page — the regulator or buyer decides what it accepts.

United States: frequently asked questions

When must US federal agencies migrate to post-quantum cryptography?

Under Executive Order 14412 and OMB M-26-15, high-value assets and high-impact systems must use post-quantum key establishment by 31 December 2030 and post-quantum digital signatures by 31 December 2031. Agencies must support TLS 1.3 by 2 January 2030, NSM-10 keeps 2035 as the goal for mitigating as much quantum risk as feasible, and M-26-15 plans full migration by 2035.

What is CNSA 2.0 and when does it apply?

CNSA 2.0 is NSA's algorithm suite for national security systems: ML-KEM-1024, ML-DSA-87, LMS or XMSS for firmware signing, AES-256 and SHA-384 or SHA-512. It is required in all new national security system acquisitions from 1 January 2027, non-compliant equipment must be phased out by 31 December 2030, and CNSA 2.0 is mandated for use by 31 December 2031.

Does NIST IR 8547 ban RSA and elliptic-curve cryptography?

The final report, published 27 October 2026, deprecates quantum-vulnerable public-key algorithms such as RSA and elliptic-curve cryptography after 2030 and disallows them under NIST standards and guidelines after 2035, regardless of key size.

Do federal contractors have to adopt post-quantum cryptography?

Not yet by rule. EO 14412 directs the FAR Council to propose, by around December 2026, a rule requiring covered contractors to comply with NIST FIPS, including the post-quantum standards, by 31 December 2030. As of 8 November 2026 the proposed rule had not been published. Vendors selling into national security systems already face CNSA 2.0.

Are US banks required to migrate to post-quantum cryptography?

No US financial regulator has a binding post-quantum requirement as of November 2026. The OCC has said banks should monitor developments in quantum computing, and NYDFS has asked that risk assessments consider advances in quantum computing.

Sources

Primary sources, checked on 8 November 2026. Read them alongside this summary and your own compliance team.

  1. NSM-10 (4 May 2022)
  2. Quantum Computing Cybersecurity Preparedness Act, Pub. L. 117-260
  3. OMB M-23-02 (18 Nov 2022)
  4. White House report to Congress on PQC migration cost (July 2024)
  5. NSA — CNSA 2.0 FAQ (v2.2, Oct 2026)
  6. NSA — CNSA 2.0 algorithms advisory (2022, re-issued May 2025)
  7. Executive Order 14144 (16 Jan 2025)
  8. Executive Order 14306 (6 Jun 2025)
  9. Executive Order 14412 (22 Jun 2026)
  10. OMB M-26-15 (24 Jun 2026)
  11. NIST FIPS 203 (13 Aug 2024)
  12. NIST IR 8547 final (27 Oct 2026)
  13. CISA — PQC product categories
  14. OCC — Cybersecurity and Financial System Resilience Report (June 2026)
  15. NYDFS — industry letter (10 Sep 2026)
  16. US Treasury — G7 Cyber Expert Group PQC statement

Other regions

Start with the inventory

Every timeline here starts with knowing your cryptography

Scan a public domain free in seconds, then scope a pilot that inventories a real slice of your estate.