Cross-Framework Mapping

ISO/IEC 23837 - Security Requirements for Quantum Key DistributionvsOWASP ASVS

See exactly how ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls map to OWASP ASVS. Pre-computed mappings, identified gaps, and coverage analysis.

10
Controls Mapped
32
Gaps Found
17%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO/IEC 23837 - Security Requirements for Quantum Key Distribution maps to OWASP ASVS with 17% coverage across 7 directly mapped controls. Analysis of 42 ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls identifies 35 compliance gaps — primarily concentrated in Part 2: Evaluation and Testing Methods.

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

Control Mappings

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

Clause 1-3: Introductory Provisions(5 mappings)

23837-1.1Scope
OWASPASVS-1Architecture, Design and Threat Modelling (V1)
23837-1.2Normative references2 targets
OWASPASVS-6Stored Cryptography (V6)
OWASPASVS-9Communication Security (V9)
27557-1Scope
OWASPASVS-1Architecture, Design and Threat Modelling (V1)
27557-3Terms and definitions
OWASPASVS-1Architecture, Design and Threat Modelling (V1)

Clause 5: Security Functional Requirements for Conventional Network Components(4 mappings)

23837-1.5.2Cryptographic module requirements2 targets
OWASPASVS-6Stored Cryptography (V6)
OWASPASVS-9Communication Security (V9)
23837-1.5.3Network device testing requirements2 targets
OWASPASVS-6Stored Cryptography (V6)
OWASPASVS-9Communication Security (V9)

Clause 7: Security Functional Requirements for QKD Protocol Implementation(1 mappings)

23837-1.7.3Authentication and classical post-processing
OWASPASVS-2Authentication and Credential Storage (V2 + V2.4)

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 ISO/IEC 23837 - Security Requirements for Quantum Key Distribution and OWASP ASVS?

ISO/IEC 23837 - Security Requirements for Quantum Key Distribution has 42 controls across its framework, while OWASP ASVS covers 14 controls. Direct mapping analysis identifies 7 overlapping controls (17% coverage). The frameworks diverge most significantly in Part 2: Evaluation and Testing Methods, where 4 ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls have no direct OWASP ASVS equivalent.

How many controls map between ISO/IEC 23837 - Security Requirements for Quantum Key Distribution and OWASP ASVS?

Of 42 total ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls, 7 map directly to OWASP ASVS controls — representing 17% coverage. The remaining 35 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO/IEC 23837 - Security Requirements for Quantum Key Distribution to OWASP ASVS?

35 ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls have no direct equivalent in OWASP ASVS. The highest concentration of gaps is in Part 2: Evaluation and Testing Methods with 4 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 ISO/IEC 23837 - Security Requirements for Quantum Key Distribution and OWASP ASVS?

The domain with the highest gap count is Part 2: Evaluation and Testing Methods (4 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.