Cross-Framework Mapping

OWASP ASVSvsNIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)

See exactly how OWASP ASVS controls map to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). Pre-computed mappings, identified gaps, and coverage analysis.

9
Controls Mapped
5
Gaps Found
21%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OWASP ASVS maps to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) with 21% coverage across 3 directly mapped controls. Analysis of 14 OWASP ASVS controls identifies 11 compliance gaps — primarily concentrated in V14 Configuration.

Source: TheArtOfService Knowledge Graph | 14 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 9 of 9 mapped controls across 3 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

V1 Architecture and Threat Modelling(1 mappings)

OWASPASVS-1Architecture, Design and Threat Modelling (V1)
PQC-4FIPS 205 SLH-DSA Implementation - Stateless Hash-Based Digital Signature

V6 Cryptography at Rest(4 mappings)

OWASPASVS-6Stored Cryptography (V6)4 targets
PQC-2FIPS 203 ML-KEM Implementation - Module-Lattice Key-Encapsulation Mechanism
PQC-5Cryptographic Inventory and PQC Migration Roadmap
PQC-7FIPS Validated Modules, HSM Readiness, and Algorithm Validation
PQC-8Implementation Requirements - RNG, Side-Channel, Key Management, Operations, Incident Response

V9 Communication(4 mappings)

OWASPASVS-9Communication Security (V9)4 targets
PQC-2FIPS 203 ML-KEM Implementation - Module-Lattice Key-Encapsulation Mechanism
PQC-5Cryptographic Inventory and PQC Migration Roadmap
PQC-7FIPS Validated Modules, HSM Readiness, and Algorithm Validation
PQC-8Implementation Requirements - RNG, Side-Channel, Key Management, Operations, Incident Response

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between OWASP ASVS and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

OWASP ASVS has 14 controls across its framework, while NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) covers 8 controls. Direct mapping analysis identifies 3 overlapping controls (21% coverage). The frameworks diverge most significantly in V14 Configuration, where 1 OWASP ASVS controls have no direct NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) equivalent.

How many controls map between OWASP ASVS and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

Of 14 total OWASP ASVS controls, 3 map directly to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) controls — representing 21% coverage. The remaining 11 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OWASP ASVS to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

11 OWASP ASVS controls have no direct equivalent in NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). The highest concentration of gaps is in V14 Configuration with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between OWASP ASVS and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

The domain with the highest gap count is V14 Configuration (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.