SECTOR, read 13 Nov 2026
A telecom auditor asks who opened customer network information and whether any third party saw it
The FCC rules treat customer proprietary network information, CPNI, as data about the services a customer uses, including call details and billing. A carrier's analytics team builds churn, usage and fraud reports from exactly that data. The auditor asks which of those reports show CPNI and who in the business opened them.
The rule is specific about records. A carrier must be able to say when CPNI was provided to third parties or when they were allowed access, and an officer certifies compliance each year. For an analytics stack that makes the viewer stage and the agent stage central: the question is who, or which program, saw call-level fields.
What an auditor asks
- Can you show the customer's approval status before CPNI is used? Basis: 47 CFR 64.2009(a) requires "a system by which the status of a customer's CPNI approval can be clearly established prior to the use of CPNI." (47 CFR 64.2009 (Cornell LII), read 13 Nov 2026). Map stages: Warehouse column, Transformation. Show the approval flag as a column and trace it into the models that build marketing audiences. The column and transformation cells show which tools follow a flag across that step.
- Do you keep a record of every time CPNI was disclosed to or accessed by third parties? Basis: 47 CFR 64.2009(c) says carriers "shall maintain a record of all instances where CPNI was disclosed or provided to third parties, or where third parties were allowed access to CPNI." (47 CFR 64.2009(c) (Cornell LII), read 13 Nov 2026). Map stages: Report, Viewer, Agent. Show a log that names each external recipient of a CPNI-bearing report or dataset, including a connected agent. The report, viewer and agent cells show where tools document that.
- Who reviews compliance before CPNI is used for outbound marketing? Basis: 47 CFR 64.2009(d) requires carriers to "establish a supervisory review process" for outbound marketing and keep records for a minimum of one year. (47 CFR 64.2009(d) (Cornell LII), read 13 Nov 2026). Map stages: BI field, Report. Show reviewer approvals tied to the dashboards or audience extracts built from CPNI fields. The BI field and report cells show whether a tool can point to those fields in a report.
- What reasonable measures protect against unauthorized access to CPNI? Basis: 47 CFR 64.2010(a) says carriers "must take reasonable measures to discover and protect against attempts to gain unauthorized access to CPNI." (47 CFR 64.2010 (Cornell LII), read 13 Nov 2026). Map stages: Viewer, Agent. Show access rules and alerts for the BI tool and any agent connection that reaches call detail. The viewer and agent cells show which tools document them; see what an agent is told.
- If CPNI is breached, can you say which records were exposed? Basis: 47 CFR 64.2011 sets the notification process for CPNI breaches, starting with law enforcement; the section is the basis for an ask about scope. (47 CFR 64.2011 (Cornell LII), read 13 Nov 2026). Map stages: Report, Viewer. Show that you can list the reports and viewers who touched a CPNI field in a given window. The report and viewer cells show where that list exists.
The map cells that answer these asks
These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation.
| Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total |
|---|---|---|---|---|---|---|---|---|
| Alation | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 |
| Euno | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 |
| Atlan | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 |
| Snowflake Horizon | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 |
| Databricks Unity Catalog | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 |
| Microsoft Purview | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 |
| Select Star | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 |
| Informatica | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 |
| Securiti | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 |
| DataHub | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 |
| Secoda | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 |
| Collibra | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 |
| Immuta | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 |
| Ataccama ONE | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 |
| Privacera | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 |
| OneTrust | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 |
Other sectors
Sources
- 47 CFR 64.2009, Safeguards required (Cornell LII), read 13 Nov 2026
- 47 CFR 64.2010, Safeguards on release of CPNI (Cornell LII), read 13 Nov 2026
- 47 CFR 64.2011, Notification of CPNI security breaches (Cornell LII), read 13 Nov 2026
- 47 CFR 64.2005, Use of CPNI without customer approval (Cornell LII), read 13 Nov 2026
Last reviewed 13 Nov 2026.