CYRUS’SCloud CornerTECHNOLOGY · TRUST · PERSPECTIVE
Home / PQC / NIST and PQC

NIST and PQC

Distinguish a finalized standard from an algorithm selected for future standardization. Both are milestones, but they support different implementation decisions.

NIST and post-quantum security illustrated with Evaluation, Standardization, Implementation, Migration planning
NIST and post-quantum security — an illustrated overview of the topics on this page.

Content reviewed: October 25, 2026

The finalized baseline

StandardAlgorithmPurpose
FIPS 203ML-KEMEstablish shared key material through a key encapsulation mechanism
FIPS 204ML-DSALattice-based digital signatures
FIPS 205SLH-DSAHash-based digital signatures

These three standards were published August 13, 2024. ML-KEM is not a bulk file-encryption algorithm; applications use established symmetric encryption with appropriately established keys.

Selected is not finalized

NIST selected HQC in March 2025 for standardization as an additional key-establishment option. Selection should not be described as completion of a published FIPS standard. Consult NIST’s current publications for later algorithms and draft status.

NIST and PQC topic map: The finalized baseline, Selected is not finalized, Algorithm, module, and system assurance, Practical adoption
NIST and PQC — topic overview

Algorithm, module, and system assurance

An implementation supporting a standardized algorithm is not automatically a validated cryptographic module or an approved end-to-end system. Confirm the relevant module validation, configuration, protocol profile, and agency or contractual requirements.

Practical adoption

  • Use maintained implementations and supported protocol profiles.
  • Separate confidentiality migration from signature and trust-chain migration.
  • Keep an inventory of library versions and dependent hardware.
  • Test negative cases, fallback behavior, and recovery before production rollout.

Sources & further reading