If you worry that today’s encrypted data could be read by future quantum computers, post-quantum cryptography is the fix. It swaps vulnerable public-key methods for new NIST standards, and migration should start now.
Post-quantum cryptography sits inside the wider field of quantum technology, which the hub page maps out.
| Item | Value |
|---|---|
| First NIST post-quantum standards | FIPS 203, FIPS 204, FIPS 205 |
| Default ML-KEM parameter set in NIST IR 8547 | ML-KEM-768 |
| Federal high-value-asset deadline, key establishment | December 31, 2030 |
| Federal high-value-asset deadline, digital signatures | December 31, 2031 |
| Federal TLS 1.3 enforcement date | January 2, 2030 |
| Classical public-key algorithms fully disallowed | After 2035 |
These figures come from NIST’s PQC project presentation and a Quantum Computing Report article on NIST IR 8547. Deadlines and standards can change, so check the sources before you rely on them.
Why quantum computers threaten today’s encryption
The threat is aimed at public-key cryptography, the part of encryption that sets up secure connections and proves identity. The Quantum Computing Report’s October 27, 2026 article on NIST IR 8547 lists RSA, Diffie-Hellman, ECDH, ECDSA and EdDSA as the quantum-vulnerable algorithms that post-quantum cryptography is meant to replace.
The most pressing worry is harvest now, decrypt later. The report says adversarial intelligence agencies routinely siphon encrypted traffic from public networks, intending to decrypt it once cryptanalytically relevant quantum computers mature. Data that must stay secret for many years is exposed to that plan today.
The sources used here do not give a date for when such a machine will exist. Not every quantum application is a threat, either: quantum sensing is a separate branch of the field with a different purpose.
Which post-quantum cryptography standards has NIST published?
As of NIST’s September 24, 2025 presentation, the first set of post-quantum standards is FIPS 203, FIPS 204 and FIPS 205. The same talk covers the selection of HQC in the 4th round and an ongoing process for new on-ramp digital signature algorithms.

The report’s migration table pairs each quantum-vulnerable algorithm with a post-quantum replacement:
- ML-KEM (FIPS 203) is the standard listed for key establishment, in place of RSA, DH and ECDH.
- ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) cover general digital signatures.
- HQC and FN-DSA are listed as under development.
- Stateful signatures such as LMS and XMSS are approved strictly for software, firmware and secure boot signing, because tracking their state adds operational overhead.
NIST is also writing guidance for key encapsulation mechanisms (KEMs), such as SP 800-227, which the September 2025 presentation names alongside the transition guidance in NIST IR 8547.
Migration deadlines for federal systems and the wider market
The dates below are the ones the sources give, as of NIST’s September 2025 presentation and the Quantum Computing Report’s October 27, 2026 article.
- The September 2025 presentation describes a mandatory U.S. government migration to post-quantum cryptography by 2035.
- Federal high-value assets and high-impact systems face binding deadlines: December 31, 2030 for key establishment and December 31, 2031 for digital signatures.
- Across the broader IT ecosystem, classical quantum-vulnerable public-key algorithms will be deprecated after 2030 and disallowed after 2035.
- Federal agencies must enforce TLS 1.3 by January 2, 2030.
The report presents IR 8547 as a blueprint for federal agencies, commercial enterprises and standard-setting bodies. If you run systems outside government, treat these dates as a planning benchmark and check which rules apply to you.
Why key exchange comes before signatures
Key exchange is the immediate priority. Intercepted ciphertext cannot be re-encrypted after the fact, so protocols such as TLS and Internet Key Exchange need early attention. The report says NIST advises deploying hybrid key exchange, pairing ML-KEM with classical Diffie-Hellman, right away.
Hybrid designs are accommodated. A post-quantum shared secret can be concatenated with a classical one without invalidating FIPS 140 module validation, and dual signatures are accepted as long as at least one component algorithm is NIST-approved.
Signatures are different. They are inherently immune to harvest-now collection, because authenticity is checked at the time of signing. The hard part is logistics: replacing PKI certificates, root certificate authorities, smart cards and hardware security modules has historically demanded decade-long conversion cycles.
Symmetric tools are in better shape. The report says AES, SHA-2, SHA-3 and Ascon meet the quantum-resistant criteria and remain approved.
How can you prepare your own systems?
You do not need to guess where to begin. The sources point to an order of work that you can adapt to your own environment:
- Inventory where public-key cryptography is used. The report cites tooling that automates discovery of cryptographic artifacts and generates Cryptography Bills of Materials (CBOMs), and names IBM’s Quantum Safe suite as one example.
- Rank data by how long it must stay confidential, since long-lived secrets are the harvest-now targets.
- Start with key exchange in TLS and similar protocols, using hybrid ML-KEM where your software supports it.
- Plan the signature and PKI replacement early, because certificates, root authorities and hardware modules take years to change.
- Keep symmetric cryptography that is still approved, and retire legacy 112-bit primitives, which the report says are disallowed after 2030.
Curious how quantum machines are reached by researchers and businesses? Our guide to quantum cloud computing covers that side of the field.
Frequently asked questions
What is post-quantum cryptography?
Show answer
It is a set of algorithms designed to replace classical public-key methods such as RSA and elliptic-curve schemes. As of NIST’s September 2025 presentation, the first standards are FIPS 203, FIPS 204 and FIPS 205.
Do I need to replace AES?
Show answer
According to the Quantum Computing Report’s October 27, 2026 article, AES, SHA-2, SHA-3 and Ascon remain approved. The primitives flagged for replacement are the public-key ones, plus legacy 112-bit primitives after 2030.
Can I combine post-quantum and classical algorithms?
Show answer
Yes. The same report says NIST accommodates hybrid key establishment and dual signatures, provided at least one signature component is NIST-approved.
When must migration be finished?
Show answer
For U.S. government systems, NIST’s September 2025 presentation names 2035 as the mandatory migration date. The October 2026 report sets earlier deadlines of December 31, 2030 and December 31, 2031 for federal high-value assets, so check which one applies to you.



