Post-Quantum, Explained · Part 02 of 04 · 5 min read

The new standards, in plain English

After an eight-year public competition, NIST picked replacements built on math that quantum computers aren’t known to shortcut. You won’t implement them yourself. You’ll buy products that do, so it helps to know the names on the spec sheet.

Meet the replacements

FIPS 203FINAL · AUG 2024
ML-KEM
Module-Lattice Key Encapsulation · formerly CRYSTALS-Kyber KEY EXCHANGE

How two computers agree on a secret key over the internet. The one to prioritize, because it protects against harvest-now attacks.

REPLACESRSA and ECDH key exchange
FIPS 204FINAL · AUG 2024
ML-DSA
Module-Lattice Digital Signature · formerly CRYSTALS-Dilithium SIGNATURES

The main general-purpose signature: proves a website, software update or document is genuine.

REPLACESRSA and ECDSA signatures
FIPS 205FINAL · AUG 2024
SLH-DSA
Stateless Hash-Based Digital Signature · formerly SPHINCS+ SIGNATURES

A conservative backup built only on hash functions. Larger and slower, but rests on very well-understood math.

REPLACESRSA and ECDSA where caution matters most
FIPS 206DRAFT
FN-DSA
FFT over NTRU-Lattice Digital Signature · formerly FALCON SIGNATURES

Compact signatures for places where size matters, like certificates and constrained devices.

REPLACESRSA and ECDSA in size-sensitive uses
Selected Mar 2025STANDARD IN DEVELOPMENT
HQC
Hamming Quasi-Cyclic KEY EXCHANGE

A backup to ML-KEM built on different math (error-correcting codes), in case lattices ever show a weakness.

ROLEA fallback for ML-KEM
Infographic

Bigger keys, same job

Post-quantum keys and signatures are much larger. That’s why old firewalls, VPNs and embedded devices sometimes choke on them, and why testing matters.

Bytes. ML-KEM-768 and ML-DSA-65 are the common general-purpose settings. FN-DSA-512 signature size is an average. Linear scale within each group.

Infographic · How the transition actually happens

Hybrid: belt and suspenders

Most systems won’t switch overnight. They run the old and new algorithms together and combine the results, so an attacker has to break both. This is already the default in Chrome and is supported by OpenSSL 3.5 and later.

The takeaway

When you buy or renew a VPN, firewall, identity provider or hosting plan, ask for FIPS 203 (ML-KEM) support by name, and whether the product can switch algorithms with a software update.

Get the vendor questions Six questions to send every key vendor, ready to copy. See the questions