PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.10.7: 12.10.7 Response procedures for PAN found in unexpected locations

Incident response procedures must exist, to be started whenever stored PAN is found where it is not expected, and must include: deciding what to do with PAN found outside the CDE, such as retrieving it, securely deleting it and/or moving it into the defined CDE as applicable; determining whether sensitive authentication data is stored alongside the PAN; establishing the source of the account data and how it reached the unexpected location; and fixing the data leaks or process gaps that caused it. Objective under the customized approach: processes exist to respond quickly, analyse and resolve cases where cleartext PAN is detected where it should not be. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 44 controls across 16 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 22301:2019 · 5 controls

ISO 27002:2022 · 5 controls

  • 5.24 Information security incident management planning and preparation
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence
  • 8.12 Data leakage prevention

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-3.13 Deploy a Data Loss Prevention Solution

ISO 27001:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence
  • 8.12 Data leakage prevention

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

AWS Well-Architected Security Pillar · 2 controls

  • SEC07-BP03 Automate identification and classification
  • SEC10-BP04 Develop and test security incident response playbooks

FedRAMP High · 2 controls

  • IR-4 Incident Handling
  • IR-9 Information Spillage Response (IR-9)

FedRAMP Moderate · 2 controls

  • IR-4 Incident Handling
  • IR-9 Information Spillage Response (IR-9)

APRA CPS 234 · 1 control

  • CPS234-P24 Information Security Response Plans

C5 (Germany) · 1 control

  • C5-SIM-03 Documentation and reporting of security incidents

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

ISO/IEC 42001:2023 · 1 control

  • 10.2 Nonconformity and corrective action

NIST SP 800-172 · 1 control

  • 3.14.5e Review Persistent Storage and Remove CUI No Longer Needed

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 12: Information Security Policies

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

PCI DSS 4.0 12.10.7 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 44 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls