PCI DSS 4.0
Appendix A3: Designated Entities Supplemental Validation (DESV) – PCI DSS 4.0

PCI DSS 4.0 A3.2.5.1: A3.2.5.1 Annual confirmation of data-discovery effectiveness

The entity must confirm its data-discovery methods by: testing their effectiveness; making sure they can find cleartext PAN on every type of system component and every file format in use; and confirming that effectiveness at least every 12 months. Linked to the PCI DSS scoping section. Guidance: one approach is planting test PANs on in-use platforms and formats and checking they are detected. Applies only to designated entities. Customized approach objective: not eligible for the customized approach; only the defined approach can be used.

Maintained by Gerard BlokdykControl text last updated

Other controls in Appendix A3: Designated Entities Supplemental Validation (DESV) – PCI DSS 4.0

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 A3.2.5.1 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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls