FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011)vsSWIFT CSCF
See exactly how FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls map to SWIFT CSCF. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) maps to SWIFT CSCF with 23% coverage across 3 directly mapped controls. Analysis of 13 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls identifies 10 compliance gaps — primarily concentrated in FCC CPNI: Use, Approval and Notice (64.2004-64.2008).
Source: TheArtOfService Knowledge Graph | 13 controls analysed | 718 frameworks | 330K+ cross-framework mappings
Control Mappings
Showing 3 of 3 mapped controls across 3 domains. Sign up to explore all 330K+ mappings across 718 frameworks.
FCC CPNI: Basis, Purpose and Definitions (64.2001-64.2003)(1 mappings)
FCC CPNI: Safeguards on Use and Disclosure (64.2009-64.2010)(1 mappings)
FCC CPNI: Data Breach Notification (64.2011)(1 mappings)
Related Comparisons
Other FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) comparisons
Other SWIFT CSCF comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.
Free
- ✓ 718 framework browser
- ✓ Cross-framework mappings (330K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and SWIFT CSCF?
FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) has 13 controls across its framework, while SWIFT CSCF covers 8 controls. Direct mapping analysis identifies 3 overlapping controls (23% coverage). The frameworks diverge most significantly in FCC CPNI: Use, Approval and Notice (64.2004-64.2008), where 3 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls have no direct SWIFT CSCF equivalent.
How many controls map between FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and SWIFT CSCF?
Of 13 total FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls, 3 map directly to SWIFT CSCF controls — representing 23% coverage. The remaining 10 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 SWIFT CSCF?
10 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) controls have no direct equivalent in SWIFT CSCF. The highest concentration of gaps is in FCC CPNI: Use, Approval and Notice (64.2004-64.2008) 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 FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) and SWIFT CSCF?
The domain with the highest gap count is FCC CPNI: Use, Approval and Notice (64.2004-64.2008) (3 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.