Response procedures must be ready to be triggered whenever cleartext PAN turns up outside the CDE and must include: deciding what to do with it, covering retrieving it, deleting it securely and/or moving it into the defined CDE as applicable; working out how the data came to be outside the CDE; fixing the data leaks or process gaps that caused it; identifying the data's source; and determining whether any track data is stored alongside the PANs. Guidance: contributing factors such as business processes, user behaviour or misconfiguration should be addressed to stop recurrence. Applies only to designated entities. Objective under the customized approach: not eligible for the customized approach; only the defined approach can be used.
PCI DSS 4.0 A3.2.5.2 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.