TheArtOfService
Cross-Framework Mapping

3GPP Security Architecture (TS 33.501 — 5G Security)vsFIDO2 and W3C WebAuthn Standard

See exactly how 3GPP Security Architecture (TS 33.501 — 5G Security) controls map to FIDO2 and W3C WebAuthn Standard. Pre-computed mappings, identified gaps, and coverage analysis.

9
Controls Mapped
13
Gaps Found
23%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP Security Architecture (TS 33.501 — 5G Security) maps to FIDO2 and W3C WebAuthn Standard with 23% coverage across 5 directly mapped controls. Analysis of 22 3GPP Security Architecture (TS 33.501 — 5G Security) controls identifies 17 compliance gaps — primarily concentrated in Subscriber Privacy and Service Security.

Source: TheArtOfService Knowledge Graph | 22 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 9 of 9 mapped controls across 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Subscriber Privacy and Service Security(1 mappings)

6.12Subscription Identifier Privacy
→SEC-5Channel Binding

Authentication and Key Management(6 mappings)

6.4Secondary Authentication3 targets
→SEC-1Data Integrity Proofs
→SEC-2Enveloping Proofs
→SEC-5Channel Binding
6.5AUSF and SEAF Functions3 targets
→SEC-1Data Integrity Proofs
→SEC-2Enveloping Proofs
→SEC-5Channel Binding

Radio and Access Network Security(1 mappings)

6.7Security Key Establishment for Radio Bearers
→SEC-5Channel Binding

Non-3GPP and Inter-Network Security(1 mappings)

9.1N32 Interface Security (PRINS/TLS)
→SEC-5Channel Binding

Related Comparisons

Other 3GPP Security Architecture (TS 33.501 — 5G Security) comparisons

3GPP Security Architecture (TS 33.501 — 5G Security) vs NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements15 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs NIS2 Directive Implementing Acts15 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs UK Telecommunications (Security) Act 202115 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs TISAX — Trusted Information Security Assessment Exchange13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs FAA Cybersecurity Framework for Aviation13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs South Korea ISMS-P13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs NIST SP 800-82 Rev 3 — Guide to OT Security13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs PAS 1192-5:2015 — Security-Minded Approach to BIM and Digital Built Environments13 mappings

Other FIDO2 and W3C WebAuthn Standard comparisons

FDA 21 CFR Part 11 vs FIDO2 and W3C WebAuthn Standard3 mappingsCNCF Cloud Native Security (Cloud Native Computing Foundation) vs FIDO2 and W3C WebAuthn Standard3 mappingsHL7 FHIR Security Framework vs FIDO2 and W3C WebAuthn Standard3 mappingsNIST SP 800-92 vs FIDO2 and W3C WebAuthn Standard3 mappingsNIST SP 800-124 Rev 2 — Mobile Device Security vs FIDO2 and W3C WebAuthn Standard3 mappingsCISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 vs FIDO2 and W3C WebAuthn Standard3 mappingsNIST SP 800-115 vs FIDO2 and W3C WebAuthn Standard3 mappingsISO/SAE 21434 vs FIDO2 and W3C WebAuthn Standard3 mappings

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • ✓ 693 framework browser
  • ✓ Cross-framework mappings (819K+)
  • ✓ 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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between 3GPP Security Architecture (TS 33.501 — 5G Security) and FIDO2 and W3C WebAuthn Standard?

3GPP Security Architecture (TS 33.501 — 5G Security) has 22 controls across its framework, while FIDO2 and W3C WebAuthn Standard covers 22 controls. Direct mapping analysis identifies 5 overlapping controls (23% coverage). The frameworks diverge most significantly in Subscriber Privacy and Service Security, where 4 3GPP Security Architecture (TS 33.501 — 5G Security) controls have no direct FIDO2 and W3C WebAuthn Standard equivalent.

How many controls map between 3GPP Security Architecture (TS 33.501 — 5G Security) and FIDO2 and W3C WebAuthn Standard?

Of 22 total 3GPP Security Architecture (TS 33.501 — 5G Security) controls, 5 map directly to FIDO2 and W3C WebAuthn Standard controls — representing 23% coverage. The remaining 17 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping 3GPP Security Architecture (TS 33.501 — 5G Security) to FIDO2 and W3C WebAuthn Standard?

17 3GPP Security Architecture (TS 33.501 — 5G Security) controls have no direct equivalent in FIDO2 and W3C WebAuthn Standard. The highest concentration of gaps is in Subscriber Privacy and Service Security 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 3GPP Security Architecture (TS 33.501 — 5G Security) and FIDO2 and W3C WebAuthn Standard?

The domain with the highest gap count is Subscriber Privacy and Service Security (4 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.