NIST's 2030 and 2035 quantum deadlines explained: what they cover

In its draft transition report, NIST proposes that 112-bit quantum-vulnerable public-key algorithms be deprecated after 2030, and that all quantum-vulnerable public-key algorithms be disallowed after 2035. These are dates for NIST's own standards and federal use. They are not a law for private companies, and the report is a draft.

What the document is

NIST IR 8547, "Transition to Post-Quantum Cryptography Standards," was published as an initial public draft on 12 November 2024. The comment period closed on 10 January 2025, and NIST posted the comments on 21 January 2025. As of the NIST record I checked, it is still labeled an initial public draft, so check the NIST site for a final version before you cite dates in a policy.

The three status terms

NIST uses the language from SP 800-131A:

• Acceptable: approved for use under the associated guidance.
• Deprecated: may be used, but there is some security risk, and the data owner must weigh that risk and decide whether to keep using it.
• Disallowed: no longer allowed for the stated purpose.

Deprecated is not banned. It is a prompt to plan and document a decision.

What the tables propose

For digital signatures (ECDSA, EdDSA, RSA) and for key establishment (finite-field DH, elliptic curve DH, RSA), the draft says:

• 112 bits of security strength: deprecated after 2030, disallowed after 2035.
• 128 bits or more: disallowed after 2035.

The draft adds that for classical key establishment at 112 bits, NIST intends to deprecate rather than fully disallow, so organizations can continue while they migrate to ML-KEM. It also says application-specific guidance may require or recommend quantum-resistant key establishment earlier, to reduce harvest now, decrypt later risk.

Where 2035 comes from

The draft quotes National Security Memorandum 10, which sets 2035 as the goal for mitigating as much quantum risk as is feasible across US federal systems. NIST also notes that timelines will vary by system, and that long-term confidentiality needs may require earlier transitions.

What it means for your plan

• If you sell to US federal customers, treat 2030 and 2035 as planning markers and watch for final guidance and contract language.
• If you do not, use the dates as a reasonable outer bound and set your own earlier targets for long-lived data.
• Do not wait for 2035. Migration of inventory, vendors and hardware takes years.
• Do not claim your product is compliant with a draft. Describe what you have done and what you plan.

Never describe this as a requirement unless your contract or regulator says so. It is NIST's proposed schedule for its own standards.

Quick check

Sources

• NIST IR 8547 record
• NIST IR 8547 initial public draft, full text

Last reviewed: 19 October 2026.