Unit 1 gave you vocabulary. Unit 2 gives you judgment. The shift is significant: you move from being able to name the solutions to being able to evaluate whether a specific vendor's claim is real or marketing. This lesson starts with the most important distinction in PQC procurement: the difference between a product that implements an algorithm and a product that has had that implementation independently validated.
Unit 2 progress
By the end of this lesson you will be able to
Distinguish between algorithm compliance and FIPS-validated implementation
Explain what the CMVP is and how FIPS validation works in practice
Identify the five types of vendor PQC claims and rank them by evidentiary strength
Look up a CMVP validation certificate and interpret what it means
Explain why a correct implementation of ML-KEM is not the same as a validated one
Part 1 — The gap that costs organizations money
Here is the situation that plays out repeatedly in PQC procurement: an organization asks a vendor whether their product is quantum-safe. The vendor says yes. They point to documentation that shows their product uses ML-KEM. The organization accepts this and moves on. Two years later, during a compliance audit, it becomes clear that the vendor's implementation was never independently validated, it was written by developers who read the FIPS 203 specification and implemented it themselves, with no third-party testing.
This is not fraud. It is a category error, the vendor genuinely implemented the algorithm correctly in most cases. But "correctly implemented by developers who read the spec" is not the same as "validated against the NIST test vectors by an accredited laboratory under the Cryptographic Module Validation Program." Those are different claims, with different evidentiary weight, different compliance implications, and different levels of assurance.
Learning to tell them apart is what PQCMM Level 2 requires. The definition of Level 2 is not "uses a post-quantum algorithm." It is "has at least one quantum-safe algorithm available in production that meets relevant standards." That phrase, meets relevant standards, is doing significant work. Understanding what it means is the entire point of this lesson.
Part 2 — Algorithm vs implementation: the core distinction
The distinction between an algorithm and an implementation is fundamental to reading any cryptographic compliance claim.
The algorithm
A mathematical specification
FIPS 203 specifies ML-KEM as a precise mathematical procedure. It defines exactly what inputs produce what outputs, what the security parameters are, and what the test vectors look like. The algorithm itself is free to use, anyone can read FIPS 203 and implement ML-KEM.
"Our product implements ML-KEM as specified in FIPS 203", an algorithm compliance claim
The implementation
Code running on a specific platform
An implementation is the actual software or hardware that executes the algorithm. Implementations can have bugs, side-channel vulnerabilities, incorrect parameter handling, or entropy failures, even when the underlying algorithm is sound. Validation tests the implementation, not the algorithm.
"Our ML-KEM implementation is FIPS 203 validated under CMVP certificate #XXXX", a validation claim
An analogy: a recipe and a restaurant meal are not the same thing. FIPS 203 is the recipe. Every vendor can read it. What FIPS validation tests is whether this particular kitchen, with this particular chef, using this particular equipment, produces the dish correctly and safely every time. Two restaurants using the same recipe can produce dramatically different results.
Part 3 — The CMVP: what it is and how it works
The Cryptographic Module Validation Program (CMVP) is a joint program run by NIST and the Communications Security Establishment Canada (CSEC). It is the official process by which cryptographic implementations are independently tested and validated against FIPS standards. A CMVP certificate is the gold standard for cryptographic compliance in US federal procurement and many regulated industries globally.
Key term
CMVP — Cryptographic Module Validation Program
The joint NIST/CSEC program that independently validates cryptographic module implementations against FIPS 140-series and FIPS algorithm standards. Validation is performed by NIST-accredited third-party testing laboratories (CMTLs). A successful validation produces a CMVP certificate with a unique certificate number, which is publicly searchable at csrc.nist.gov/projects/cryptographic-module-validation-program. FIPS 140-3 is the current validation standard for cryptographic modules.
The CMVP validation process has specific stages. Understanding the timeline explains why "pending validation" is a meaningful claim, and why it is not the same as "validated."
1
Vendor prepares documentation and test environment
The vendor documents their cryptographic module, what algorithms it implements, what security parameters it uses, what platforms it runs on. This documentation must conform to FIPS 140-3 requirements. Preparation typically takes months and requires specialized expertise.
Vendor-controlled
2
Accredited laboratory (CMTL) performs testing
One of NIST's accredited Cryptographic Module Testing Laboratories tests the implementation against the FIPS specification, including running the official NIST test vectors for each algorithm. The lab issues a test report to NIST. Testing can take months and often requires multiple rounds of remediation.
3–12 months typical
3
NIST reviews and issues certificate
NIST reviews the lab's test report and, if everything is in order, issues a CMVP certificate with a unique certificate number. The certificate is published in the public CMVP database. Certificate issuance can take additional months due to NIST review queue depth.
2–6 months typical
Certificate active — publicly searchable
The validated module appears in the CMVP database with its certificate number, the vendor name, the validated algorithms, the platforms covered, and the expiry date. Anyone can look up a certificate number and verify a vendor's claim in under two minutes.
Total: 6–18+ months from submission
The total timeline, from a vendor beginning the validation process to receiving a certificate, is typically 6 to 18 months or more. This matters enormously for PQC: the FIPS 203/204/205 standards were finalized in August 2024. CMVP validation for ML-KEM, ML-DSA, and SLH-DSA implementations is actively underway but the queue is long. As of late 2024, very few products hold CMVP certificates specifically for the finalized PQC standards, most are in the testing or review pipeline.
BFor an SMB decision-maker evaluating vendors: the 6–18 month validation timeline means that in 2024–2025, almost no vendor will have a CMVP certificate for FIPS 203/204/205 specifically, because the standards were only finalized in August 2024. This does not mean all vendors are lying. It means you need to ask whether they are in the CMVP pipeline, not whether they already have a certificate. A vendor with no validation plan is a different situation from a vendor with a testing lab engagement already underway.
Part 4 — Reading vendor claims: a spectrum
Vendor PQC claims exist on a spectrum from strong evidence to pure marketing. The five claim types below represent the range you will encounter. Select each claim to understand what it means and how much weight to give it.
StrongestModerateWeakest
AAs a motivated learner building career credibility: being able to categorize a vendor's PQC claim by type, and explain the difference between algorithm compliance and FIPS validation, is a genuine differentiator. Most people in security roles cannot do this today. It is the skill that lets you contribute meaningfully to procurement decisions, vendor assessments, and compliance conversations immediately after completing this course.
CFor IT professionals evaluating your existing stack: start with your TLS libraries. OpenSSL 3.x has FIPS 140-3 validated modules via OpenSSL FIPS Provider, but FIPS validation for the PQC algorithms specifically is on the roadmap, not yet complete as of late 2024. AWS-LC (Amazon's fork) and BoringSSL are similarly in process. Check the CMVP database directly rather than trusting vendor announcements, the database is the authoritative source.
Part 5 — How to look up a CMVP certificate
NIST's CMVP database is publicly searchable at csrc.nist.gov/projects/cryptographic-module-validation-program. You can search by vendor name, certificate number, algorithm, or module name. The mock database below shows what real results look like, and what to look for when evaluating a vendor's claim.
The most important thing to check in a CMVP certificate is not just whether the vendor has one, it is whether the specific algorithm and platform you are purchasing is covered by the certificate. A certificate for a Windows x64 build does not cover an ARM embedded implementation. A certificate covering AES and SHA does not cover ML-KEM. Read the algorithm list, not just the headline.
Part 6 — What "algorithm-compliant" means when FIPS validation doesn't exist yet
Here is a reality you need to hold clearly: for ML-KEM, ML-DSA, and SLH-DSA specifically, CMVP validation certificates are extremely rare in 2024–2025 because the standards were only finalized in August 2024 and the validation queue takes 6–18+ months. This does not mean that every vendor claiming ML-KEM support is lying or that their implementation is insecure.
For PQC specifically, the right framework is a three-tier assessment:
1
CMVP certificate exists for this algorithm on this platform
Highest assurance. Independent testing confirmed. Look up the certificate number. This is the bar for US federal procurement and regulated industries. Rare for PQC in 2024–2025, treat it as a positive differentiator when you find it.
2
CMVP submission in progress, open-source implementation from a reputable library
Moderate assurance. Acceptable for non-regulated environments and early deployments. The vendor should be able to name their testing lab and provide a submission date. Open-source implementations like liboqs (Open Quantum Safe) have had significant community review even before formal validation.
3
Vendor claims "quantum-safe" with no algorithm specifics, no validation reference, no roadmap
Lowest assurance. Could be marketing. Ask directly: which FIPS standard? Which algorithm? Which CMVP certificate or submission? If the vendor cannot answer, they are making a claim they cannot substantiate. This is the claim type that costs organizations money.
Comprehension check
Question 1 of 3
A vendor says their product "implements ML-KEM as specified in FIPS 203." What type of claim is this, and what is missing?
Question 2 of 3
Why do very few vendors hold CMVP certificates specifically for ML-KEM, ML-DSA, or SLH-DSA as of late 2024?
Question 3 of 3
You are reviewing a vendor's CMVP certificate and see it covers AES-256, SHA-384, and RSA-3072 on Windows x64. The vendor claims their product is "FIPS-validated for quantum-safe key exchange." What is wrong with this claim?