Skip to content

FIPS 203

ML-KEM migration guide

FIPS 203 (ML-KEM) is the NIST-standardized key encapsulation mechanism for post-quantum TLS — available now.

Framework

Module-Lattice-Based Key-Encapsulation Mechanism standard

Deadline: Available 2024

The three standards

FIPSAlgorithmPrimary use
203ML-KEMKey encapsulation (TLS)
204ML-DSADigital signatures
205SLH-DSAHash-based signatures

Hybrid TLS first

Most production migrations combine classical ECDHE with ML-KEM (e.g. X25519MLKEM768) for backward compatibility. Google and Cloudflare deploy hybrid KEX at scale — inventory must identify which endpoints are still RSA/ECDSA-only.

Handshake proof

Qtangl demo captures hybrid handshake traces attachable to signed reports. Auditors verify signatures at /verify — migration evidence, not lab-only claims.

Rollout playbook

  1. Inventory endpoints by algorithm and client compatibility requirements
  2. Pilot on internal services with controlled client base
  3. Expand to external APIs with monitoring for handshake failures
  4. Re-scan after each wave; attach proof to Convert backlog items

SLH-DSA and firmware

FIPS 205 supports code signing and firmware where stateful hash signatures (SP 800-208) apply — tag signing infrastructure separately from TLS in your CBOM.

Qtangl mapping

  • Hybrid ML-KEM handshake proof in demo and reports
  • Per-asset playbook for load balancer rollout
  • Re-scan verification after hybrid KEX deployment

References & further reading

Authoritative primary sources cited in this article. Summaries are our own — follow links for full context.

Last verified 2026-06-03