Back to Guides
Post-QuantumPKI

Post-Quantum Cryptography: The PKI Transition Guide

NIST finalized the first quantum-resistant standards in August 2024. Here's what your team needs to know.

~15 min readJanuary 2026
Post-Quantum Cryptography - The algorithms that will secure the next 50 years, showing transition from RSA to ML-KEM with 2024-2035 timeline
Aug 2024
First 3 NIST PQC standards finalized
2026
First PQC certificates available
2035
Deadline to deprecate vulnerable algorithms
Now
Move from planning to deployment

What Is Post-Quantum Cryptography?

Post-quantum cryptography (PQC) refers to cryptographic algorithms designed to resist attacks from both classical computers AND future quantum computers.

The Problem

RSA, ECC, and Diffie-Hellman algorithms that secure virtually all internet communications today can be broken by a sufficiently powerful quantum computer using Shor's algorithm.

The Solution

New algorithms based on mathematical problems that quantum computers can't efficiently solve—lattice-based, hash-based, and code-based cryptography.

The timeline: NIST spent 8 years evaluating 82 submissions from cryptographers worldwide. In August 2024, they finalized the first three standards. Your organization needs to transition before January 2035.

TODAY → FUTURE
RSA/ECCquantum computerBROKEN
TODAY → FUTURE
ML-KEMquantum computerSECURE

The "Harvest Now, Decrypt Later" Threat

You might think: "Quantum computers are decades away. Why worry now?"

Because adversaries are already harvesting encrypted data today, planning to decrypt it once quantum computers arrive. This is called the "Harvest Now, Decrypt Later" (HNDL) attack.

What's at risk:

  • TLS certificates (your web traffic)
  • Code signing certificates (software integrity)
  • S/MIME certificates (email encryption)
  • Document signing (legal validity)
  • VPN tunnels (network security)

The Math That Matters:

  • 10-30 yearsData encrypted today may need to remain confidential
  • 10-20 yearsQuantum computers capable of breaking RSA-2048 may arrive
  • 5-10 yearsMigration to PQC algorithms takes for large organizations
  • Result:You're already behind schedule.

"The time to start transitioning is now, even though a cryptographically relevant quantum computer may be years or decades away."— NIST IR 8547

NIST's Post-Quantum Cryptography Standards

After 8 years of global evaluation, NIST finalized three standards in August 2024, with a fourth in 2025:

ML-KEM

FIPS 203 - Finalized

Module-Lattice Key Encapsulation Mechanism (formerly CRYSTALS-Kyber)

Replaces:RSA, ECDH
Public Key:~1,184 bytes
Use case: TLS handshakes, VPNs, general key exchange

ML-DSA

FIPS 204 - Finalized

Module-Lattice Digital Signature Algorithm (formerly CRYSTALS-Dilithium)

Replaces:RSA, ECDSA
Public Key:~1,952 bytes
Signature:~3,293 bytes
Use case: Code signing, certificates, authentication

SLH-DSA

FIPS 205 - Finalized

Stateless Hash-Based Digital Signature Algorithm (formerly SPHINCS+)

Replaces:RSA, ECDSA
Public Key:~32-64 bytes
Signature:~7,856-49,856 bytes
Use case: Long-term document signing, conservative choice

FN-DSA

FIPS 206 - Finalized

FFT-based NTRU Digital Signature Algorithm (formerly FALCON)

Replaces:RSA, ECDSA
Public Key:~897-1,793 bytes
Signature:~666-1,280 bytes
Use case: Compact signatures where size matters

Coming Soon

AlgorithmExpectedNotes
HQC2027Backup KEM using different math than ML-KEM

Good News: Symmetric Crypto Is Safe

Not everything needs to change. Symmetric cryptographic algorithms are NOT significantly vulnerable to quantum attacks:

Safe (Keep Using)

  • AES-128, AES-256 (encryption)
  • SHA-256, SHA-384, SHA-512 (hashing)
  • HMAC (message authentication)
  • SHA-3, ChaCha20

Vulnerable (Must Replace)

  • RSA (key exchange and signatures)
  • ECDSA, EdDSA (signatures)
  • ECDH, DH (key exchange)
  • DSA (signatures)

Why the difference?

Quantum computers use Shor's algorithm to break algorithms based on integer factorization (RSA) and discrete logarithms (DH/ECDH/ECDSA). Symmetric algorithms use different math that quantum computers can't efficiently attack.

Where Are We Now?

2024
2025
NOW
2027
2030
2035
2024Standards Finalized

FIPS 203, 204, 205 published

2025FN-DSA Finalized

FIPS 206 published, HQC selected

2026Early AdoptionYOU ARE HERE

First PQC certificates available

2027HQC Standard

Backup KEM option ready

2030Deprecation

112-bit algorithms deprecated

2035Migration Complete

Full transition required

Your Post-Quantum Migration Checklist

You don't need quantum computers to exist to start preparing. Here's what to do now:

Phase 3: Testing & Early Deployment

NOW - 2026
  • Deploy hybrid TLS - ML-KEM alongside classical algorithms
  • Validate interoperability - Browsers, clients, servers
  • Performance testing - PQC algorithms have different characteristics
  • Update certificate policies - Prepare for PQC certificate issuance
  • Pilot PQC certificates - First commercial certs now available

Crypto-Agility is Key

The biggest lesson from PQC: your systems should be able to swap cryptographic algorithms without a complete rebuild. If you're locked into RSA forever, you have a bigger problem than quantum computers.

The Hybrid Approach: Belt and Suspenders

During the transition, many organizations will use "hybrid" cryptography—combining classical and post-quantum algorithms together.

Example Hybrid TLS Key Exchange:

ML-KEM-768+X25519=Hybrid Key Agreement

Why Hybrid?

  • If ML-KEM has an undiscovered weakness, X25519 protects you
  • If quantum computers arrive early, ML-KEM protects you
  • You get the security of both until confidence in PQC grows

Current Hybrid Support:

Cloudflare

X25519Kyber768 (preliminary ML-KEM)

Google Chrome

X25519Kyber768

AWS

ML-KEM in AWS-LC

Most CAs

Planning for 2026

Check your browser: Visit pq.cloudflareresearch.com to see if your browser already supports post-quantum key exchange.

What Changes for TLS/SSL Certificates?

Certificates themselves will change to use PQC algorithms:

Current Certificates

Signature Algorithm: SHA256withRSA
Public Key: RSA 2048-bit

Future PQC Certificates

Signature Algorithm: ML-DSA-65
Public Key: ML-DSA-65

Key Differences:

AspectRSA-2048ML-DSA-65
Public key size256 bytes~1,952 bytes
Signature size256 bytes~3,293 bytes
Security level112-bit classical128-bit quantum

Larger Sizes Matter:

  • Increased TLS handshake overhead
  • More data in certificate chains
  • May require infrastructure updates

Frequently Asked Questions

When will quantum computers break current encryption?

Nobody knows for certain. Estimates range from 10-30 years. But the "harvest now, decrypt later" threat means adversaries are collecting encrypted data today to decrypt later. Long-lived secrets are already at risk.

Is AES-256 quantum-safe?

Yes. Symmetric algorithms like AES are not significantly weakened by quantum computers. A 256-bit AES key provides 128-bit security against quantum attacks, which is still extremely strong.

Should I wait for the industry to figure this out?

No. NIST explicitly recommends starting now. The migration will take years, and early adopters will have smoother transitions. Begin with discovery and planning immediately.

What about my existing certificates?

Existing RSA/ECC certificates remain valid until they expire. The urgency is about new certificate issuance and long-term encrypted data, not immediately replacing every certificate.

Will my HSMs support PQC?

Most HSM vendors are adding PQC support. Check with your vendor for their roadmap. This is a critical planning consideration.

What if NIST's algorithms are broken later?

This is why NIST standardized multiple algorithms and continues evaluating alternatives. SLH-DSA uses different math than ML-DSA specifically as a backup. Crypto-agility lets you adapt.

Related Resources

Learn More

Official NIST Resources:

FixMyCert Related Content: