Cross-Framework Mapping

FIDO2 / WebAuthnvsISO/IEC 23837 - Security Requirements for Quantum Key Distribution

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

5
Controls Mapped
11
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

FIDO2 / WebAuthn maps to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution with 12% coverage across 2 directly mapped controls. Analysis of 16 FIDO2 / WebAuthn controls identifies 14 compliance gaps — primarily concentrated in FIDO2/WebAuthn: CTAP2.1 Client-to-Authenticator Protocol.

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

Control Mappings

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

FIDO2/WebAuthn: Authenticators, Passkeys and User Verification(1 mappings)

FIDO2-Passkey-DiscoverablePasskeys (Discoverable Credentials) and Account Recovery
23837-1.7.3Authentication and classical post-processing

FIDO2/WebAuthn: Relying Party Implementation, Phishing Resistance and Security(4 mappings)

FIDO2-Phishing-ResistancePhishing Resistance, Channel Binding, Anti-Replay and Privacy4 targets
23837-1.2Normative references
23837-1.5.2Cryptographic module requirements
23837-1.5.3Network device testing requirements
23837-1.7.3Authentication and classical post-processing

Related Comparisons

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

FIDO2 / WebAuthn has 16 controls across its framework, while ISO/IEC 23837 - Security Requirements for Quantum Key Distribution covers 42 controls. Direct mapping analysis identifies 2 overlapping controls (12% coverage). The frameworks diverge most significantly in FIDO2/WebAuthn: CTAP2.1 Client-to-Authenticator Protocol, where 3 FIDO2 / WebAuthn controls have no direct ISO/IEC 23837 - Security Requirements for Quantum Key Distribution equivalent.

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

Of 16 total FIDO2 / WebAuthn controls, 2 map directly to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls — representing 12% coverage. The remaining 14 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

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

14 FIDO2 / WebAuthn controls have no direct equivalent in ISO/IEC 23837 - Security Requirements for Quantum Key Distribution. The highest concentration of gaps is in FIDO2/WebAuthn: CTAP2.1 Client-to-Authenticator Protocol with 3 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 FIDO2 / WebAuthn and ISO/IEC 23837 - Security Requirements for Quantum Key Distribution?

The domain with the highest gap count is FIDO2/WebAuthn: CTAP2.1 Client-to-Authenticator Protocol (3 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.