United States (FCC)

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

13 controls. 28 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

13 controls 28 frameworks share controls with it United States (FCC) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
CPNI-64.2001_2003Basis, purpose and definitions (47 CFR 64.2001 + 64.2003)24
CPNI-64.2004Customer approval mechanisms - opt-in and opt-out (47 CFR 64.2004)2
CPNI-64.2005_2007Use of CPNI without customer approval + approval required for use (47 CFR 64.2005-64.2007)0
CPNI-64.2008Notice requirements for use of CPNI (47 CFR 64.2008)0
CPNI-64.2009Safeguards required for use of CPNI (47 CFR 64.2009)1
CPNI-64.2010Safeguards on disclosure - authentication for account access (47 CFR 64.2010)6
CPNI-64.2011Notification of CPNI security breaches (47 CFR 64.2011)25
CPNI-AnnualCertAnnual compliance certification - 1 March deadline (47 CFR 64.2009(e))4
CPNI-Marketing-OBMOutbound marketing (OBM) records and supervisory review (47 CFR 64.2009(b)-(c))0
CPNI-PersonnelPersonnel training and disciplinary process (47 CFR 64.2009(a))0
CPNI-RecordkeepingRecordkeeping requirements (multi-rule)0
CPNI-StatusFCC CPNI - corpus status, enforcement landscape, broadband privacy0
CPNI-VendorThird party and joint venture CPNI restrictions (47 CFR 64.2007 + 64.2009)0

Tell me when FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Processor register
  • KVKK-compliant data processing agreements in Turkish
  • Processor security assessments
  • Audit rights and audit evidence
  • Data processing agreements
  • Sub-processor list and approvals

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for FCC Customer Proprietary Network Information (CPNI) and Data Breach Rules (47 CFR 64.2001-2011), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition