Skip to content
Need to Know

SECTOR, read 13 Nov 2026

A retail auditor asks where card and customer data show up in reports and who or what can open them

The exposure mapThe Finder

A retailer's sensitive data comes in two kinds: payment account data under PCI DSS and shoppers' personal information under state privacy law. Analytics teams copy both into sales, loyalty and fraud dashboards. The auditor's first question is whether card data left the cardholder data environment and ended up in a report.

The privacy side asks a different question: what the business collected, why and with whom it shared it. California's attorney general frames those as consumer rights, and each one needs a map from a customer to the tables, reports and recipients that hold their data.

What an auditor asks

  • Is access to cardholder data restricted by business need to know? Basis: PCI DSS v4.x Requirement 7 covers restricting access to system components and cardholder data by business need to know; the Council's PCI DSS page describes the standard as a "baseline of technical and operational requirements designed to protect payment account data." (PCI Security Standards Council: PCI DSS, read 13 Nov 2026). Map stages: BI field, Report, Viewer. Show which dashboards and reports carry card-related fields and the role list allowed to open them. The BI field, report and viewer cells show which tools document that link.
  • Do you log and monitor all access to cardholder data? Basis: PCI DSS v4.x Requirement 10 covers logging and monitoring access to system components and cardholder data; the full text is in the PCI DSS document in the Council's library. (PCI Security Standards Council: document library, read 13 Nov 2026). Map stages: Viewer, Agent. Show log entries naming the user or agent that opened a report with card-adjacent fields. The viewer and agent cells show which tools record this beyond warehouse query logs.
  • What can a shopper learn about who your business shared their data with? Basis: California's CCPA page says the right to know covers "The categories of third parties with whom the business shares the personal information." (California Attorney General: CCPA, right to know, read 13 Nov 2026). Map stages: Report, Agent. Show that you can list the external recipients of reports and agent outputs built from customer tables. The report and agent cells show where a tool documents recipients.
  • Can a shopper limit how you use their sensitive personal information? Basis: California's CCPA page lists a right to direct businesses to limit their use of your sensitive personal information, for example "financial account information" and "precise geolocation data." (California Attorney General: CCPA, sensitive information, read 13 Nov 2026). Map stages: Warehouse column, BI field. Show sensitive-field tags on loyalty and location columns and the dashboard fields that display them. The column and BI field cells show which tools carry the tag that far.
  • Do you maintain reasonable security procedures for personal information? Basis: California's CCPA page says consumers may sue when personal information was stolen in a data breach because of a failure "to maintain reasonable security procedures and practices." (California Attorney General: CCPA, data breach, read 13 Nov 2026). Map stages: Viewer, Transformation. Show the access reviews and the masked copies that limit what a stolen extract would hold. The viewer and transformation cells show where tools document those controls.

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.

Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026.
ToolWarehouse columnTransformationBI fieldReportViewerAgentDocumentedTotal
Alationdocumentedpartialdocumenteddocumentedpartialdocumented4 of 654.0
Eunodocumentedpartialdocumenteddocumentedpartialpartial3 of 667.0
Atlandocumentedpartialpartialpartialpartialdocumented2 of 665.5
Snowflake Horizondocumentedpartialpartialpartialpartialdocumented2 of 655.5
Databricks Unity Catalogdocumentedpartialpartialpartialpartialdocumented2 of 655.0
Microsoft Purviewdocumentedpartialpartialdocumentedpartialpartial2 of 654.5
Select Starpartialpartialdocumenteddocumentedpartialpartial2 of 653.5
Informaticadocumenteddocumentedpartialnone foundpartialpartial2 of 630.0
Securitidocumentedpartialpartialnone foundpartialdocumented2 of 629.5
DataHubpartialpartialpartialpartialpartialdocumented1 of 661.0
Secodadocumentedpartialpartialpartialpartialpartial1 of 647.5
Collibradocumentedpartialpartialpartialpartialpartial1 of 646.5
Immutadocumentednone foundnone foundpartialpartialpartial1 of 645.0
Ataccama ONEdocumentedpartialpartialpartialnone foundpartial1 of 641.5
Privaceradocumentednone foundnone foundnone foundpartialpartial1 of 630.0
OneTrustdocumentednone foundnone foundnone foundnone foundpartial1 of 626.5

Other sectors

Sources

  1. PCI Security Standards Council, PCI DSS, read 13 Nov 2026
  2. PCI Security Standards Council, document library, read 13 Nov 2026
  3. California Attorney General, CCPA, read 13 Nov 2026
  4. California Attorney General, privacy, read 13 Nov 2026

Last reviewed 13 Nov 2026.