Comparison tables

Post-quantum cryptography deadlines compared: NIST IR 8547, EO 14412, OMB M-26-15 and CNSA 2.0

Post-quantum cryptography deadlines compared: NIST IR 8547, EO 14412, OMB M-26-15 and CNSA 2.0 Each number links to the cell's source. Cells checked unless the cell shows another date.
SourceWhat changesDateWho it binds
NIST IR 8547 (final, October 2026): digital signatures1What changesQuantum-vulnerable signature algorithms ECDSA, EdDSA and RSA (FIPS 186) are deprecated, then disallowed under NIST standards and guidelines. This replaces the projection in SP 800-57 Part 1 that NIST would disallow 112-bit public-key schemes on January 1, 2031. Post-quantum signatures listed: ML-DSA (FIPS 204), SLH-DSA (FIPS 205), and LMS, HSS, XMSS and XMSS^MT (SP 800-208).1DateDeprecated after 2030; disallowed after 20351Who it bindsUsers of NIST standards and guidelines; NIST will revise SP 800-131A, which covers federal agencies protecting controlled unclassified information, with detailed schedules. Federal high value assets and high impact systems face the earlier EO 14412 deadlines.1
NIST IR 8547 (final, October 2026): key establishment1What changesQuantum-vulnerable key establishment (finite field and elliptic curve Diffie-Hellman and MQV under SP 800-56A, and RSA under SP 800-56B) is deprecated, then disallowed. ML-KEM (FIPS 203) is the only approved post-quantum key-establishment scheme based on public-key cryptography; NIST recommends ML-KEM-768 as the default parameter set, and HQC will also be approved once published.1DateDeprecated after 2030; disallowed after 20351Who it bindsUsers of NIST standards and guidelines. Application-specific guidance may require or recommend earlier migration. Federal high value assets, high impact systems and other systems with highly sensitive data must use quantum-resistant key establishment by December 31, 2030 (OMB M-26-15).1
NIST IR 8547 (final, October 2026): symmetric cryptography and hashes1What changesNIST's few symmetric standards at the 112-bit security level are disallowed. SHA-1, already deprecated, is disallowed in FIPS-validated cryptographic modules. Approved symmetric primitives with at least 128 bits of classical security, such as AES, are believed to meet post-quantum security category 1.1Date112-bit symmetric standards: disallowed in 2030. SHA-1 in FIPS-validated modules: disallowed after 2030.1Who it bindsUsers of NIST standards and guidelines (SP 800-131A); FIPS-validated cryptographic modules for SHA-11
National Security Memorandum 10, as stated in NIST IR 85471What changesSets the target for completing the federal migration to post-quantum cryptography. NIST IR 8547 says this overall goal remains in place and that later directives require the most sensitive systems to migrate earlier.1Date20351Who it bindsNot stated in NIST IR 8547, which describes NSM-10 only as setting the target for completing the federal migration1
Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks, section 42What changesEach agency names a PQC migration lead within 30 days. OMB issues guidance within 90 days requiring agencies to review their high value assets and high impact systems, move them to post-quantum key establishment and post-quantum digital signatures, and submit a plan. NIST runs a post-quantum pilot on its own systems.2DateSigned June 22, 2026. Key establishment by December 31, 2030; digital signatures by December 31, 2031; NIST pilot complete by December 31, 2027.2Who it bindsFederal agencies; the system review excludes national security systems2
Executive Order 14412, sections 5 and 62What changesThe FAR Council publishes a proposed rule, within 180 days, requiring covered contractors to comply with NIST FIPS, including FIPS with post-quantum algorithms. NIST revises Cryptographic Module Validation Program processes to speed validations within 180 days. CISA and NIST release minimum elements for a cryptographic bill of materials within 270 days. Sector Risk Management Agencies work with CISA to help critical infrastructure owners and operators plan their migrations.2DateContractor compliance by December 31, 2030, under the proposed FAR rule the order directs; not in force as of 2026-11-142Who it bindsCovered federal contractors once a FAR rule is final (the order directs a proposed rule); critical infrastructure owners and operators receive assistance, not a deadline2
OMB Memorandum M-26-15, Execution of the Migration to Post-Quantum Cryptography3What changesAgencies run a prioritized migration with the objective of mitigating as much quantum risk as feasible, submit a PQC Migration Plan to OMB and the Office of the National Cyber Director within 120 days, and support TLS 1.3 or a successor version3DateIssued June 24, 2026. Migration plan within 120 days; TLS 1.3 no later than January 2, 2030; quantum-risk objective by December 31, 2030.3Who it bindsFederal agencies; it does not apply to national security systems3
FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard4What changesSpecifies ML-KEM for establishing a shared secret key; this standard, or other FIPS or NIST Special Publications that specify alternatives, must be used wherever a shared secret key is established for federal applications4DatePublished and effective August 13, 20244Who it bindsFederal agency information systems, including those run by contractors on an agency's behalf; not national security systems. Private and commercial organizations may adopt it.4
FIPS 204, Module-Lattice-Based Digital Signature Standard5What changesSpecifies ML-DSA. FIPS 204, FIPS 205, FIPS 186-5 or SP 800-208 must be used for public-key-based signatures.5DatePublished and effective August 13, 20245Who it bindsAll federal departments and agencies, for protecting sensitive unclassified information5
FIPS 205, Stateless Hash-Based Digital Signature Standard6What changesSpecifies SLH-DSA. FIPS 205, FIPS 204, FIPS 186-5 or SP 800-208 must be used for public-key-based signatures.6DatePublished and effective August 13, 20246Who it bindsAll federal departments and agencies, for protecting sensitive unclassified information6
NSA Commercial National Security Algorithm Suite 2.0 (CNSA 2.0) advisory7What changesNSA's selection of quantum-resistant algorithms for national security systems. NSA points to CNSS Policy 15, released March 4, 2025, and its CNSA 2.0 FAQ for the details.8DateAdvisory released September 7, 2022. The 2022 release said CNSA 2.0 algorithms will eventually be required and CNSA 1.0 compliance continues in the interim.7Who it bindsNational security system owners, operators and vendors: networks that hold classified information or are otherwise critical to military and intelligence activities7

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Method

We read NIST IR 8547 (final, October 2026) as a PDF, the Federal Register text of Executive Order 14412 on govinfo, OMB Memorandum M-26-15, the FIPS 203, 204 and 205 PDFs, and NSA's CNSA 2.0 press release and post-quantum resources page. Each cell was checked on 2026-11-14 against the source it cites. NIST dates are copied as NIST states them ('after 2030', 'after 2035', 'in 2030'); we did not turn them into calendar days. The NSA's CNSA 2.0 advisory and FAQ (media.defense.gov) and CNSS Policy 15 (cnss.gov) refused automated access, so the CNSA 2.0 transition milestones are left out (see Omitted). The FAR rule's status is as checked on 2026-11-14. This table explains the documents; it is not legal advice.

Omitted

What was left out, and why.

  • A row left out: The CNSA 2.0 transition milestones are in NSA's advisory and FAQ PDFs on media.defense.gov and in CNSS Policy 15 on cnss.gov; both refused automated access on 2026-11-14 (HTTP 403, and a certificate the browser does not trust), so the dates could not be checked.

Notes

  • NIST IR 8547 defines deprecated as usable with some security risk that the data owner must weigh, and disallowed as no longer allowed for the stated purpose.
  • NIST IR 8547 says it supports the implementation of Executive Order 14412 and OMB Memorandum M-26-15.
  • Executive Order 14412 defines a high impact system as one with at least one FIPS 199 security objective rated high.

Sources

  1. National Institute of Standards and Technology. NIST IR 8547, Transition to Post-Quantum Cryptography Standards (final, October 2026), sections 1 and 4. Checked .
  2. The White House (published in the Federal Register). Executive Order 14412 of June 22, 2026, Securing the Nation Against Advanced Cryptographic Attacks (91 FR 38483). Checked .
  3. Executive Office of the President, Office of Management and Budget. OMB Memorandum M-26-15, Execution of the Migration to Post-Quantum Cryptography (June 24, 2026). Checked .
  4. National Institute of Standards and Technology. FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard, announcement sections 6 and 11. Checked .
  5. National Institute of Standards and Technology. FIPS 204, Module-Lattice-Based Digital Signature Standard, announcement sections 6 and 12. Checked .
  6. National Institute of Standards and Technology. FIPS 205, Stateless Hash-Based Digital Signature Standard, announcement sections 6 and 12. Checked .
  7. National Security Agency. NSA Releases Future Quantum-Resistant (QR) Algorithm Requirements for National Security Systems (press release, September 7, 2022). Checked .
  8. National Security Agency. Post-Quantum Cybersecurity Resources. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.