Standards, Certification & Compliance Bodies
Understand who creates PQC standards, who certifies products, and who mandates compliance — worldwide and by region.
Why this matters: PQC has no single global standard — NIST, ETSI, and regional bodies move at different speeds with different mandates, and knowing who requires what, where, is what keeps a global rollout from missing a jurisdiction.
Start here: Trace one of the four real scenarios from algorithm standard to certification programme to compliance mandate: three bodies, three different jobs, one chain.
For your role
- Executive / Business Leader
- Classify twelve organisations by type, scope and authority, then trace the chain from algorithm standard to certification programme to compliance mandate: who requires what, where.
- GRC / Risk & Compliance
- The Standards, Certification and Compliance chain and the five-region by four-type coverage grid are the map of which body's requirement applies in each jurisdiction; the scored scenarios test it.
- Researcher / Academic
- Twelve bodies with founding, scope and authority, the standard-to-certification-to-compliance chain and the regional grid: the reference for citing the right body.
- Certification & Validation Engineer
- The standard-to-certification-to-compliance chain separates who writes a standard, who certifies against it and who mandates it — the order in which a certificate should be read.
- IT Ops / DevOps
- The regional coverage grid says which certification programme a product in a given region has to hold; the scenarios show how to pick the right body for a question.
- Curious Explorer
- Who decides which cryptography is allowed, who checks products, and who makes rules: the module sorts the alphabet soup of organisations into three jobs and five regions.
Three Distinct Roles in the PQC Ecosystem
The PQC transition involves three fundamentally different types of organizations, each playing a distinct role. Confusing them is a common source of compliance mistakes.
Think of it like building construction: standardization bodies write the building codes (what materials are safe), certification bodies are the inspectors who verify that a specific building meets those codes, and compliance frameworks are the zoning laws that say "in this jurisdiction, meeting code is mandatory for these buildings." All three are necessary; none is redundant.
Create technical standards: algorithm specifications, security levels, protocol integration. Their output is a published document, not a certificate.
Certify that products/systems correctly implement standards. Their output is a certificate (or certificate number) tied to a specific product version.
Regulations and mandates that reference standards and require certifications. Their output is a legal/regulatory obligation, not a technical specification.
How the Three Roles Interact
The three roles form a chain: a standards body publishes an algorithm specification → a certification body validates that a product correctly implements it → a compliance framework mandates that regulated entities use certified products.
Publishes FIPS 203 (ML-KEM algorithm specification)
Certifies HSM implementations of FIPS 203 (FIPS 140-3 certificate)
Mandates that federal agencies use CMVP-certified modules implementing ML-KEM-1024
Key insight: You can comply with a framework, be certified against a standard, and the standard body writes the standard — three verbs, three different relationships.
Governmental vs Non-Governmental
Whether an organization is governmental or non-governmental determines whether its outputs can be legally mandatory or only advisory. This distinction matters enormously for compliance.
Government agencies with regulatory authority. Their technical guidelines and mandates can be legally binding. Authority derives from government statute, not membership consensus.
Industry consortia and open membership bodies. Their standards gain authority through broad adoption, not government mandate. Anyone can contribute; consensus drives output.
National Algorithm Divergence
Governments can mandate nationally-specific algorithms that differ from NIST standards. This creates interoperability challenges for multinational organizations.
China's Office of State Commercial Cryptography Administration (OSCCA) mandates SM2 (asymmetric), SM3 (hash), and SM4 (symmetric) algorithms for regulated sectors. These are not interoperable with NIST FIPS 203/204/205. Organizations operating in China may need a separate cryptographic stack.
Korea's KpqC competition (2022–2025) selected HAETAE and AIMer (signatures), SMAUG-T and NTRU+ (KEMs) as Korean national algorithms — distinct from NIST's selections. Target standardization by 2029. Korean telecom operators may require support for KpqC algorithms alongside FIPS 203/204/205.
Crypto-agile architectures (abstraction layers, pluggable algorithm providers) are essential for organizations operating across jurisdictions with divergent algorithm mandates. Design your key management and protocol stacks to support algorithm negotiation, not hard-coded algorithm choices.
Global Tier — Universal Authority
Global bodies gain authority through broad adoption and multi-country consensus, not government mandate. Their standards are recognized worldwide but not legally binding in themselves.
Regional Landscape
- • NIST — FIPS 203/204/205 algorithm standards (globally followed)
- • NSA — CNSA 2.0 mandate for National Security Systems
- • CISA — federal procurement guidance
- • CMVP/CAVP — module & algorithm validation
- • ETSI TC CYBER — TS 103 744 (quantum-safe cryptography standard)
- • ENISA — EUCC certification scheme, ACM list
- • EC — NIS2 Directive, eIDAS 2.0, DORA (legally binding regulations)
- • BSI — TR-02102 series (binding for German government)
- • ANSSI — PQC position papers, hybrid mandate (binding for French critical infra)
- • NCSC — three-phase roadmap (2025–2035), CAPS product assurance
- • BSI UK — post-Brexit standards alignment
- • KISA (Korea) — KpqC competition, HAETAE/AIMer/SMAUG-T/NTRU+
- • AIST/METI (Japan) — CRYPTREC cipher list, PQC guidance
- • OSCCA/NGCC (China) — SM2/SM3/SM4 mandate, parallel PQC track
- • MAS (Singapore) — Technology Risk Management (TRM) guidelines
Practical guidance: For most products, start with NIST FIPS 203/204/205 (US procurement), add ETSI TS 103 744 (EU interoperability), then layer national guidance (BSI TR-02102 for Germany, ANSSI hybrid for France). Check CMVP for US federal sales and EUCC for EU government sales.
Reading the App: The Compliance Page
The app's /compliance page tracks 48+ PQC compliance frameworks. Each framework maps directly to a body covered in this module.
| Framework | Enforcement Body | Body Type | Scope |
|---|---|---|---|
| FIPS 140-3 | NIST / CMVP | Standards + Certification | US |
| CNSA 2.0 | NSA | Regulatory Agency | US (NSS) |
| NIS2 Directive | EC / ENISA | Regulatory / Certification | EU |
| eIDAS 2.0 | European Commission | Regulatory | EU |
| ANSSI PQC | ANSSI | Regulatory Agency | France |
| BSI TR-02102 | BSI | Regulatory Agency | Germany |
| ETSI TS 103 744 | ETSI TC CYBER | Standards Body | EU/Global |
| EUCC | ENISA | Certification Body | EU |
Reading the App: The Migrate Page
The /migrate page shows PQC readiness for products across 7 infrastructure layers. Each product's FIPS validation badge maps to a specific certification body and program.
The product has a current CMVP certificate (FIPS 140-3 or 140-2 approved). CMVP is the certification body; NIST/CSE administers it. Vendor is on the official NIST CMVP database.
Covers FedRAMP authorization, WebTrust audit, or FIPS-mode operation — partial certification evidence but not a full CMVP certificate.
No CMVP certificate found. The product may claim PQC support but has not undergone formal certification.
Also shown: CC certification badges (Common Criteria CCRA / EUCC) and CAVP algorithm validation (algorithm-level, below module-level). These link back to ENISA (EUCC) and NIST CAVP respectively.
The Full Standards → Certification → Compliance Pipeline
Here is how NIST IR 8547, CMVP, and CNSA 2.0 work together in a single procurement scenario:
Defines the ML-KEM algorithm specification, parameters (ML-KEM-512/768/1024), and security levels.
An accredited lab tests the ML-KEM implementation through NIST’s ACVTS: ACVP delivers FIPS 203 test vector sets, the implementation returns its answers, and NIST issues a CAVP algorithm certificate once they are accepted.
An NVLAP-accredited lab tests the HSM against FIPS 140-3; CMVP (NIST/CSE) reviews the report and issues the certificate. The time this takes varies; the CMVP Modules in Process list shows where a submission is.
NSA CNSA 2.0 requires National Security Systems to use ML-KEM-1024 (from FIPS 203) for key establishment, with exclusive use phased in by 2030 (signing, networking) and 2033 (web/cloud, OS).
Federal agency buyers verify the product uses a module with an active CMVP certificate whose approved-algorithm list includes ML-KEM (with the parameter set they need, e.g. ML-KEM-1024 for CNSA 2.0), used in its validated configuration. The certificate states one overall security level for the module; it does not assign a level to each algorithm.
CMVP backlog warning: FIPS 140-3 validation can take a long time, and a place in the Modules in Process queue is not evidence of the outcome. Module certificates that list ML-KEM or ML-DSA as approved algorithms exist, but most active certificates list none. Plan procurement timelines around this certification lag.
IETF Working Groups & the RFC Process
The IETF integrates NIST PQC algorithms into Internet protocols. Unlike NIST (which defines the algorithm), IETF defines how the algorithm is used in specific protocols. Both are standards bodies, but with different domains of authority.
draft-ietf-pquip-pqc-engineers — comprehensive PQC guide for protocol designers. Not a protocol itself — coordinates across all other WGs.
RFC 9629 (KEM in CMS), RFC 9882 (ML-DSA in CMS), RFC 9814 (SLH-DSA in CMS), composite signature drafts.
RFC 9954 (hybrid design) and RFC 10024 (X25519MLKEM768), deployed in Chrome, Firefox and Cloudflare.
PQC algorithm profiles for COSE headers (ML-DSA, SLH-DSA for IoT).
Hybrid ML-KEM/X25519 key exchange for SSH protocol.
Reading the Standards Landscape
A quick reference for interpreting standard citations:
NIST published it (US standards body); CMVP certifies implementations; CNSA 2.0 mandates ML-KEM-1024 from it for NSS.
IETF LAMPS WG published it (global SDO); defines KEM use in CMS — a protocol standard built on FIPS 203.
ETSI TC CYBER published it (EU SDO); normative requirements for quantum-safe cryptography harmonized with NIST.
BSI published it (German governmental); binding for German critical infrastructure. Annual update.
NSA published it (US governmental); binding mandate for National Security Systems. References FIPS 203/204/205.
ENISA manages it (EU certification body); EU adaptation of Common Criteria; valid across all EU member states.
Workshop Overview
Apply what you learned in 5 interactive workshop steps:
Classify 12 organizations by type, scope, and authority. Color-coded feedback per attribute.
Deep-dive into 12 key bodies — founding, decision-making, PQC outputs, and library references.
Click-to-connect: trace 4 real-world chains from algorithm standard to certification to mandate.
Interactive 5-region × 4-type matrix. Click cells to see which bodies operate there.
5 scored workplace scenarios with detailed explanations after each submission.
Related Resources
Classify bodies, explore organizations, trace compliance chains, and tackle real scenarios.
Related modules
- Architect Quantum ImpactSame migration phase · Shares ML-DSA, ML-KEM, NIST SP 800-227
- Ops Quantum ImpactSame migration phase · Shares ML-DSA, ML-KEM, NIST SP 800-227
- PQC GRCSame migration phase · Shares ML-KEM, ML-DSA, NSA CNSA 2.0
- Quantum ThreatsSame migration phase · Shares ML-DSA, ML-KEM, NSA CNSA 2.0
Check your understanding
16 questions on Standards, Certification & Compliance Bodies, each with its answer and the reason.
Take the quizNext step
Produce the artifact: Compliance ChecklistThis module belongs to the Foundations phase; Compliance Checklist produces a deliverable of that phase in the Command Center.
Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.