A data-discovery methodology must be in place that: confirms PCI DSS scope; locates every source and location of cleartext PAN every three months at a minimum and after any significant change to the CDE or to processes; and addresses the possibility that cleartext PAN resides on networks and systems beyond the CDE as currently defined. Linked to the PCI DSS scoping section. Guidance: unexpected places include error logs or memory dumps, and methods may be commercial tools, in-house programs, manual searches, or a mix. Applies only to designated entities. Customized approach objective: not eligible for the customized approach; only the defined approach can be used.
PCI DSS 4.0 A3.2.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.