Conformance guides
Every quantakrypto guide tagged Conformance, with what each one covers.
Conformance testing for post-quantum crypto: why passing the KATs is not enough
Passing NIST's ACVP known-answer vectors, conforming to FIPS 203/204/205, and passing a security audit are three different things. What the KATs miss, how conformance testing actually works, and why an audited, popular library is not evidence of conformance.
ConformanceComplianceA FIPS 203 conformance checklist for ML-KEM implementations
The concrete checks a conformant ML-KEM implementation must pass: §7.2/§7.3 input validation, implicit rejection, exact sizes and encoding, versioning and adversarial vectors, as a checklist you can run against any library.
ConformanceML-KEMComplianceACVP vs conformance vs FIPS 140-3: what each one actually proves
"ACVP-tested," "conformant," and "FIPS 140-3 validated" are three different claims that answer three different questions. What each one covers, what it silently leaves out, and how to ask which axis a vendor's assurance really lives on.
ConformanceComplianceHow to verify a QuantaKrypto attestation
A QuantaKrypto attestation is a post-quantum-signed, independently checkable record of a project's cryptographic posture. It is what turns the self-reported score in a crypto-agility.json manifest into evidence. Here is what it contains, how it is signed, and the exact steps to verify one yourself, without trusting us.
ConformanceSignaturesTools