Find FIPS 140-3 validated modules with post-quantum cryptography (ML-KEM, ML-DSA)
Ask your AI assistant which FIPS 140-3 validated modules and Common Criteria certified products mention post-quantum algorithms such as ML-KEM, ML-DSA, SLH-DSA, LMS and XMSS. Plan your post-quantum migration from current certification data.
Add the Security Certifications brain to your AI assistant
NIST published its first post-quantum standards in 2024: ML-KEM (FIPS 203) for key establishment, ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) for signatures. Stateful hash-based signatures, LMS and XMSS, were approved earlier. Teams planning a post-quantum migration need products that implement these algorithms and are validated. The Security Certifications brain lets you search the certification records for them from your AI assistant.
How post-quantum support is detected
- For FIPS 140-3 modules, the algorithms come from the module record and its security policy, so ML-KEM or ML-DSA validated by the CAVP show up by name.
- For Common Criteria products, the algorithms come from keywords that sec-certs extracts from the security target and certification report.
- Names are normalised, so CRYSTALS-Kyber is reported as Kyber and MLKEM as ML-KEM. A document that only mentions "post-quantum" in general is not counted.
A mention in a certification document is a strong lead, not a guarantee that the algorithm is inside the validated boundary or enabled by default. Check the module security policy before relying on it.
Questions to try
- "Which active FIPS 140-3 modules mention ML-KEM or ML-DSA?"
- "List HSMs with a FIPS validation that supports LMS or XMSS signatures."
- "Which smart card certificates mention post-quantum algorithms, and which vendors hold them?"
- "For this vendor, which of its validated modules already include ML-DSA?"
Certificate data comes from sec-certs.org, built by the Centre for Research on Cryptography and Security (CRoCS) at Masaryk University from NIST CMVP and the Common Criteria Portal. KBrain refreshes it weekly and links it to the CVE brain.
Add the Security Certifications brain to your AI assistant
Check FIPS 140-3 and Common Criteria certificates, post-quantum algorithms, and the CVEs that may affect certified products from Claude, ChatGPT, or any MCP compatible assistant. Hosted and refreshed weekly from sec-certs.org, with nothing to set up.
Questions people ask.
Which post-quantum algorithms does the search recognise?
ML-KEM, ML-DSA, SLH-DSA and FN-DSA, the earlier names Kyber, Dilithium, Falcon and SPHINCS+, the stateful hash-based signatures LMS (with HSS) and XMSS, and other candidates such as HQC, BIKE, FrodoKEM, NTRU and Saber.
Does a match mean the module is approved for post-quantum use?
Not on its own. It means the algorithm appears in the certificate data. Check the module security policy for whether it is inside the validated boundary and in an approved mode.
Why would a product appear without a post-quantum match?
Its documents may not name the algorithm, the support may have been added after the evaluated version, or the certificate may be newer than the last weekly refresh.