FIPS 140-3 Validation for Post-Quantum Cryptography: What Federal Buyers Should Check on a Module Certificate
A product that implements ML-KEM is different from a product that runs a FIPS 140-3 validated module with ML-KEM on its certificate. How to read a CMVP certificate for post-quantum algorithms, and what to ask suppliers.
Federal agencies are required to use validated cryptographic modules to protect sensitive information. That requirement did not change when NIST published its post-quantum standards. It means a migration to ML-KEM or ML-DSA has two parts: the algorithm has to be present in the product, and the module that implements it has to hold a certificate that lists it.
Vendor data sheets often blur the two. This post explains what the certificate says, where to look, and what to ask a supplier before a “supports post-quantum cryptography” claim goes into an acquisition or a migration plan.
Two changes landed in the same year
On September 22, 2026, NIST’s Cryptographic Module Validation Program (CMVP) moved every remaining FIPS 140-2 certificate to its Historical List, according to the FIPS 140-3 transition schedule. The same page says the program still supports the purchase and use of those modules for existing systems. The validated modules page adds that agencies should not include historical modules in new systems, and that continued use is a risk decision for the agency.
In the same period, the first FIPS 140-3 certificates that list post-quantum algorithms were issued. The program stopped accepting new FIPS 140-2 submissions in 2022, two years before FIPS 203, 204, and 205 were published, so a certificate that lists ML-KEM, ML-DSA, or SLH-DSA is a FIPS 140-3 certificate.
For a program office, the two changes combine into one task. Much of the installed base now sits on historical certificates, and its replacement needs to be both FIPS 140-3 validated and post-quantum capable. Our summary of federal PQC mandates covers the deadlines that apply: key establishment by the end of 2030 and digital signatures by the end of 2031 under Executive Order 14412.
Implemented, tested, and validated are three different states
A supplier can truthfully describe a product in any of these ways, and they mean different things.
Implemented. The product’s code contains the algorithm. Nothing has been independently checked.
Algorithm tested. The implementation passed NIST’s algorithm test vectors and holds an algorithm certificate (the “A” numbers that appear on module certificates). This shows the math is computed correctly. It says nothing about key storage, self-tests, or the module boundary.
Module validated. An accredited laboratory tested the whole module against FIPS 140-3 and the CMVP issued a certificate. The validated modules page states the distinction directly: implementing an approved security function does not by itself meet the FIPS 140 requirements.
Between the second and third states is the Modules in Process list. A module on that list has been submitted. It has no certificate yet, and the list does not say when it will get one.
What a certificate tells you
Each certificate page in the CMVP database lists the approved algorithms the module was validated with. The examples below were read from the public certificate pages in November 2026. They are examples, not a complete list.
| Certificate | Module | Type and level | Initial validation | Post-quantum algorithms listed |
|---|---|---|---|---|
| #5247 | Go Cryptographic Module | Software, Level 1 | April 27, 2026 | ML-KEM |
| #5298 | AWS-LC 3 Cryptographic Module (dynamic) | Software, Level 1 | June 3, 2026 | ML-KEM |
| #5450 | Luna T7 | Hardware, Level 3 | July 29, 2026 | ML-KEM, ML-DSA, LMS |
| #5497 | QASM Cryptographic Module | Hardware, Level 3 | August 19, 2026 | ML-KEM, ML-DSA, SLH-DSA, LMS |
Three things stand out.
First, coverage is uneven. The two software modules in the table list ML-KEM for key establishment and no post-quantum signature algorithm. A product built on one of them can make a validated claim about key establishment and cannot yet make one about ML-DSA.
Second, CISA’s list of product categories that use post-quantum standards (January 23, 2026) shows the same pattern at the product level. It names four categories where capable products are widely available (cloud platform and infrastructure services, chat and messaging software, web browsers and servers, and data-at-rest endpoint security) and notes that those categories have mostly adopted post-quantum key establishment, with signatures and authentication still to come. The list does not address FIPS validation, so a product can sit in a “widely available” category and still run an unvalidated implementation.
Third, each certificate has a sunset date five years after validation and a caveat line. The caveat on certificate #5298, for example, limits the validation to operation in approved mode, configured as its Security Policy describes.
An example: a remote access gateway refresh
Consider a hypothetical agency replacing remote access gateways whose cryptographic module is now on the Historical List. The details are illustrative.
The supplier’s data sheet says the new release “supports hybrid post-quantum key exchange” and is “FIPS 140-3 compliant.” The contracting officer’s technical representative asks for the certificate number and reads it against the product.
- The certificate is for an earlier version of the vendor’s cryptographic library and lists no post-quantum algorithms. A newer library version with ML-KEM is on the Modules in Process list.
- The hybrid key exchange in the new release is provided by that newer library. In approved mode on the currently validated module, the gateway negotiates classical key exchange only.
- The management interface uses a separate TLS stack that is not inside any validated module boundary.
None of this makes the product a poor choice. It changes what the agency can report. The gateway meets the validation requirement today with classical key exchange, and it will meet the post-quantum requirement after the newer module is validated and the agency installs that version. The agency writes both conditions into the contract: delivery of the validated version within a stated period after the certificate is issued, and notification if the submission is withdrawn.
Questions to put to suppliers
- What is the certificate number, and which exact module version does it cover? Which version ships in the product we are buying?
- Which post-quantum algorithms and parameter sets appear on the certificate and in the Security Policy? Programs with a required parameter set, such as ML-KEM-1024 for national security systems, should confirm that set specifically.
- Was the module tested on the operating system and hardware we will run it on?
- Does the product use the post-quantum algorithms when the module is in approved mode, or only when approved mode is off?
- Which cryptographic functions in the product run outside the validated module (management interfaces, update checks, log transport)?
- If the module is still in process, what is the supplier’s commitment when the certificate is issued, and what happens if it is delayed?
- When a patch changes the cryptographic library, how is the validation maintained?
National security systems have an additional step. Products for those systems go through NSA’s approval processes under CNSA 2.0, and a CMVP certificate alone does not settle that question.
Keeping the answer current after the purchase
The certificate describes a module version in a tested configuration. What runs in production can drift from it: a patch replaces the library, an administrator disables approved mode to fix an interoperability problem, or a peer that does not offer ML-KEM causes sessions to fall back to classical key exchange.
A cryptographic inventory is more useful for this purpose when each entry records the module version and its certificate number alongside the algorithm in use.
Sentinel helps organizations understand and change cryptography across many systems at once, which includes knowing which library or module provides each algorithm on each system. CAM provides asset-level cryptographic evidence for assets in production after migration, so a claim such as “these gateways negotiate ML-KEM from a validated module” can be checked per asset. Both products have a provisional patent issued.
If your program is replacing modules on the Historical List or writing post-quantum requirements into an acquisition, contact QuantumWorks.