SECTOR, read 13 Nov 2026
A financial-services auditor traces a customer field to every dashboard and every user who could open it
A financial-services auditor starts with a customer field such as an account number or a tax ID and asks where it ends up. The answer has to run past the warehouse table into the transformation that copies it, the BI field that displays it and the report that carries it. Two rule sets set the frame: the FTC Safeguards Rule for non-bank financial institutions and New York's cybersecurity regulation for firms licensed by its Department of Financial Services.
The second half of the walk is about people. The text of both rules talks about authorized users, not only about outsiders, so the evidence is a list of who could open a given report and a log of who did. An AI agent that reads analytics data counts as one more user on that list. The five asks below quote the rules and name the map stages that answer each.
What an auditor asks
- Which customer information can each authorized user reach, and when did you last review that? Basis: 16 CFR 314.4(c)(1) calls for "Implementing and periodically reviewing access controls" that "Limit authorized users' access only to customer information" they need to do their jobs. (16 CFR 314.4 (Cornell LII), read 13 Nov 2026). Map stages: BI field, Report, Viewer. Show a current list of who can open each report that displays a customer field, and the date of the last review. The BI field, report and viewer cells answer this; 0 of 16 tools document the viewer stage on 13 Nov 2026.
- Do you know where customer data sits across your systems, ranked by importance? Basis: 16 CFR 314.4(c)(2) says to "Identify and manage the data, personnel, devices, systems, and facilities" that serve business purposes, in line with their relative importance. (16 CFR 314.4 (Cornell LII), read 13 Nov 2026). Map stages: Warehouse column, Transformation. Bring the field inventory: which warehouse columns hold customer data and which transformation models copy them. The column and transformation cells answer this; 14 tools document the column stage and 1 document the transformation stage.
- Can you show a log of what authorized users did with customer information? Basis: 16 CFR 314.4(c)(8) requires controls "designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information." (16 CFR 314.4(c)(8) (Cornell LII), read 13 Nov 2026). Map stages: Viewer, Agent. Show log lines that name a user or an agent and the report or dataset opened. Warehouse query history covers the database layer only. The viewer and agent cells show whether a tool joins the report view and the agent call to the field.
- Which users can read nonpublic information, and who limited their privileges? Basis: 23 NYCRR 500.7(a)(1) tells each covered entity to "limit user access privileges to information systems that provide access to nonpublic information to only those necessary to perform the user's job." (23 NYCRR 500.7 (Cornell LII), read 13 Nov 2026). Map stages: Viewer, Agent. Show role and group mappings for the BI tool and for any agent service account, with the approver of each grant. See who saw it against who could see it and approving an agent's access.
- How do you monitor authorized users of systems that hold nonpublic information? Basis: 23 NYCRR 500.14(a)(1) requires "risk-based policies, procedures and controls designed to monitor the activity of authorized users." (23 NYCRR 500.14 (Cornell LII), read 13 Nov 2026). Map stages: Report, Viewer. Show a recurring review of report-open events for reports that carry nonpublic fields, with exceptions followed up. The report and viewer cells show which tools produce that evidence.
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
- 16 CFR 314.4, Elements (Cornell LII), read 13 Nov 2026
- 23 NYCRR 500.7, Access privileges (Cornell LII), read 13 Nov 2026
- 23 NYCRR 500.14, Monitoring and training (Cornell LII), read 13 Nov 2026
- 16 CFR 314.4 (eCFR), read 13 Nov 2026
Last reviewed 13 Nov 2026.