Certification
Prove your post-quantum crypto actually conforms
Migrating to ML-KEM, ML-DSA, or SLH-DSA is the easy part. Certification answers the load-bearing question your auditors and customers will ask: does the implementation you shipped actually follow FIPS 203/204/205 — including the input checks the test vectors never touch?
What certification covers
A passing test-vector run is not conformance. We exercise the malformed-input and edge-case behaviour the vectors omit, and give you evidence you can defend.
- Conformance testing against FIPS 203, 204, and 205 — the §7.2/§7.3 input validation and encoding behaviour, not just the known-answer vectors.
- Any implementation, any language, driven through a small stdin/stdout protocol — no source access required.
- A signed conformance report you can hand to auditors, customers, and regulators.
- Re-testing on every release, so conformance is a continuous property, not a one-off certificate.
Related reading
guideConformance testing for post-quantum crypto: why passing the KATs is not enough7 minstandardFIPS 203 (ML-KEM)Module-Lattice-Based Key-Encapsulation Mechanism · formerly CRYSTALS-KyberstandardFIPS 204 (ML-DSA)Module-Lattice-Based Digital Signature Algorithm · formerly CRYSTALS-DilithiumstandardFIPS 205 (SLH-DSA)Stateless Hash-Based Digital Signature Algorithm · from SPHINCS+
Get started
Turn quantum risk into a credential.
Book a discovery call and get an indicative scope and pricing for your organisation.