Skip to content

FIPS 203, 204 and 205, what each standard actually covers

NIST finalised three post-quantum standards in August 2024. FIPS 203 specifies ML-KEM for key encapsulation, FIPS 204 specifies ML-DSA for signatures, and FIPS 205 specifies SLH-DSA as a hash-based signature alternative with different assumptions.

Standards are revised and national guidance changes. Check the current published version before making a compliance decision on the strength of any summary.

FIPS 203 · ML-KEM

Module-Lattice-Based Key-Encapsulation Mechanism, developed from the Kyber submission. This is the key establishment algorithm — the replacement for the elliptic-curve key exchange in a TLS handshake.

Parameter sets ML-KEM-512, ML-KEM-768 and ML-KEM-1024 target increasing security categories. ML-KEM-768 is the common choice for general use. How it works covers the mental model.

FIPS 204 · ML-DSA

Module-Lattice-Based Digital Signature Algorithm, from the Dilithium submission. The general-purpose signature replacement for ECDSA and RSA signatures, and the primary recommendation for most signing.

FIPS 205 · SLH-DSA

Stateless Hash-Based Digital Signature Algorithm, from SPHINCS+. Its security rests only on hash function properties rather than on lattice assumptions, which makes it a hedge: if lattice cryptanalysis advanced unexpectedly, SLH-DSA would be unaffected.

The cost is size and speed — signatures are substantially larger and signing is slower. It suits firmware and root signing, where signatures are rare, long-lived and the conservative assumption is worth paying for. The two signature schemes compared.

What compliance requires

Using an implementation validated for the standard, in an approved configuration, with the parameter set your security policy requires. Validation programmes cover these algorithms, and a vendor claiming support should be able to name a certificate rather than a roadmap.

What none of them specify

Where the randomness comes from. Every one of these algorithms consumes entropy for key generation, and ML-DSA consumes it per signature in its randomised mode. The standards specify the algorithm and defer the source to SP 800-90 — which is the dependency worth reading next.