Post-Quantum Algorithms & Protocols

Compare post-quantum algorithms and track their support across IETF protocols

What this means for you

Executive / Business Leader
The “What one high-assurance profile specifies” box explains that CNSA 2.0 names ML-KEM-1024 and ML-DSA-87 for US National Security Systems without presenting that profile as a universal federal mandate.
GRC / Risk & Compliance
The Transition Guide lists candidate PQC migration paths, region, publication status, and transition timing. It is educational evidence—not a compliance determination—so confirm applicability in the primary policy and product documentation.
Developer / Engineer
Detailed Comparison sorts objective size and RAM fields, labels heterogeneous catalogue performance text as illustrative, and includes a same-harness hardware case study. Validation › “Known-answer checks” runs pinned vectors in your browser.
Security Architect
The Protocol Support tab tracks each protocol across pure-KEM, hybrid-KEM, pure-Sig and hybrid-Sig, each marked RFC, Draft, Experimental or None, with filters for OSS, commercial and live deployment.
Researcher / Academic
The "Research needed" toggle narrows to algorithms with an incomplete data row; Validation › "Implementation Attacks" gives side-channel and fault-injection notes per family; the Region filter includes KpqC, CACR and CRYPTREC.
Certification & Validation Engineer
On the Validation tab, "Implementation Attacks" gives side-channel and fault-injection notes per family and the known-answer tests run in the browser; a CAVP algorithm validation is a prerequisite for a module certificate, not the certificate itself.
IT Ops / DevOps
The “Final NIST standards” preset shows algorithms published in final NIST FIPS standards; it does not mean your implementation is validated. Protocol Support separates specification maturity from reviewed deployment evidence.
Curious Explorer
You get a short preview of three common starting points from the published NIST standards — ML-KEM-768, ML-DSA-65, SLH-DSA-SHA2-128s — then "Show full algorithm comparison" or "Learn the basics first".

What are you trying to do?

Showing 38 of 193
Family:
Function:
Security:
Region:
Status:

Algorithm Transition

A migration path is not a drop-in replacement. A KEM establishes key material; it does not encrypt application data by itself. Use these rows to start a comparison, then check the protocol construction, API and object model, key lifecycle, message and certificate sizes, implementation support, and validation needs. Empty cells mean no reviewed path or date is recorded—not “no change required.”

What are you replacing?

KEM

Signature

Related content

Next step

Try the algorithms in the Playground

The Playground runs ML-KEM, ML-DSA and SLH-DSA in your browser.