Framework overlap

Does SSAE 18 cover NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

You hold SSAE 18 and have been told to do NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). Here is how much overlaps, control by control.

63% of NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) you already have

SSAE 18 already covers about 63% of NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205), leaving 3 of 8 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 3

No control in SSAE 18 maps directly to one in NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in SSAE 18 reaches these. This is the list to scope.

PQC-1
PQC Scope, Quantum Resistance Rationale, and Mathematical Foundations
PQC-3
FIPS 204 ML-DSA Implementation - Module-Lattice Digital Signature
PQC-6
Crypto-Agility Architecture and Hybrid Composite Mode Strategy
Show the 5 you already have
PQC-2
FIPS 203 ML-KEM Implementation - Module-Lattice Key-Encapsulation Mechanism
PQC-4
FIPS 205 SLH-DSA Implementation - Stateless Hash-Based Digital Signature
PQC-5
Cryptographic Inventory and PQC Migration Roadmap
PQC-7
FIPS Validated Modules, HSM Readiness, and Algorithm Validation
PQC-8
Implementation Requirements - RNG, Side-Channel, Key Management, Operations, Incident Response

How this is calculated

Already covered means a mapping runs from a control in SSAE 18 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition