TheArtOfService
Cross-Framework Mapping

FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011)vs3GPP Security Architecture (TS 33.501 — 5G Security)

See exactly how FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls map to 3GPP Security Architecture (TS 33.501 — 5G Security). Pre-computed mappings, identified gaps, and coverage analysis.

23
Controls Mapped
1
Gaps Found
33%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) maps to 3GPP Security Architecture (TS 33.501 — 5G Security) with 33% coverage across 8 directly mapped controls. Analysis of 24 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls identifies 16 compliance gaps — primarily concentrated in Use and Disclosure of CPNI.

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

Control Mappings

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

Scope and Definitions(11 mappings)

64.2003Definitions5 targets
→6.3SUPI and SUCI Privacy
→6.5AUSF and SEAF Functions
→6.7Security Key Establishment for Radio Bearers
→6.9Handover Security
→9.2Network Domain Security
64.2004Customer Approval Mechanisms
→6.5AUSF and SEAF Functions
Art. 2Consent Definition5 targets
→6.3SUPI and SUCI Privacy
→6.5AUSF and SEAF Functions
→6.7Security Key Establishment for Radio Bearers
→6.9Handover Security
→9.2Network Domain Security

Safeguards and Authentication(6 mappings)

64.2010(b)Telephone Authentication2 targets
→6.4Secondary Authentication
→6.5AUSF and SEAF Functions
64.2010(d)In-Store Authentication2 targets
→6.4Secondary Authentication
→6.5AUSF and SEAF Functions
64.2010(e)Password and Account Protection2 targets
→6.4Secondary Authentication
→6.5AUSF and SEAF Functions

Breach Notification Requirements(3 mappings)

64.2011(a)Definition of Breach3 targets
→6.3SUPI and SUCI Privacy
→6.5AUSF and SEAF Functions
→6.7Security Key Establishment for Radio Bearers

+3 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.

Create Free Account →

Free forever — no credit card required

Related Comparisons

Other FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) comparisons

FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs FAA Cybersecurity Framework for Aviation8 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs ISO/IEC 27400:20228 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs GLI-33 — Gaming Laboratories International Event Wagering Systems8 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs TISAX — Trusted Information Security Assessment Exchange8 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs RFC 2350 — Expectations for Computer Security Incident Response (BCP 21)8 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs 3GPP 5G Security Architecture (TS 33.501)8 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs NIST SP 800-53 Rev 57 mappingsFCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) vs 3GPP Security6 mappings

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

NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements vs 3GPP Security Architecture (TS 33.501 — 5G Security)15 mappingsNIS2 Directive Implementing Acts vs 3GPP Security Architecture (TS 33.501 — 5G Security)15 mappingsUK Telecommunications (Security) Act 2021 vs 3GPP Security Architecture (TS 33.501 — 5G Security)15 mappingsTISAX — Trusted Information Security Assessment Exchange vs 3GPP Security Architecture (TS 33.501 — 5G Security)13 mappingsFAA Cybersecurity Framework for Aviation vs 3GPP Security Architecture (TS 33.501 — 5G Security)13 mappingsSouth Korea ISMS-P vs 3GPP Security Architecture (TS 33.501 — 5G Security)13 mappingsNIST SP 800-82 Rev 3 — Guide to OT Security vs 3GPP Security Architecture (TS 33.501 — 5G Security)13 mappingsPAS 1192-5:2015 — Security-Minded Approach to BIM and Digital Built Environments vs 3GPP Security Architecture (TS 33.501 — 5G Security)13 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 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and 3GPP Security Architecture (TS 33.501 — 5G Security)?

FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) has 24 controls across its framework, while 3GPP Security Architecture (TS 33.501 — 5G Security) covers 22 controls. Direct mapping analysis identifies 8 overlapping controls (33% coverage). The frameworks diverge most significantly in Use and Disclosure of CPNI, where 4 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls have no direct 3GPP Security Architecture (TS 33.501 — 5G Security) equivalent.

How many controls map between FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and 3GPP Security Architecture (TS 33.501 — 5G Security)?

Of 24 total FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls, 8 map directly to 3GPP Security Architecture (TS 33.501 — 5G Security) controls — representing 33% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) to 3GPP Security Architecture (TS 33.501 — 5G Security)?

16 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls have no direct equivalent in 3GPP Security Architecture (TS 33.501 — 5G Security). The highest concentration of gaps is in Use and Disclosure of CPNI 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 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and 3GPP Security Architecture (TS 33.501 — 5G Security)?

The domain with the highest gap count is Use and Disclosure of CPNI (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.