PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.10.2: 12.10.2 Annual review and testing of the incident response plan

On a cycle of no more than 12 months, the entity must review its security incident response plan, updating the content where needed, and must test it, with the test covering every element listed in Requirement 12.10.1. The guidance explains that tests can take the form of simulated incidents or table-top exercises involving relevant personnel, and that reviewing how well the simulated response went helps confirm nothing required is missing from the plan. Customized approach objective: the plan stays current and undergoes periodic testing.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 7 controls

  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • CP-4 Contingency Plan Testing
  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-8 Incident Response Plan

FedRAMP Moderate · 7 controls

  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • CP-4 Contingency Plan Testing
  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-8 Incident Response Plan

NIST SP 800-53 Rev 5 · 6 controls

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
  • NIST-CSF-ID.IM-01 Improvements are identified from evaluations
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

CIS Controls v8 · 4 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.7 Conduct Routine Incident Response Exercises

ISO 27002:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation
  • 5.30 ICT readiness for business continuity
  • 8.34 Protection of information systems during audit testing

SOC 2 · 3 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC7.4 CC7.4 Responding to security incidents

AWS Well-Architected Security Pillar · 2 controls

Azure Security Benchmark · 2 controls

  • ASBv3-IR-1 Preparation - update incident response plan and handling process
  • ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

ISO 22301:2019 · 2 controls

  • 8.5 Exercise programme
  • 8.6 Evaluation of business continuity documentation and capabilities

ISO 27001:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.30 ICT readiness for business continuity

ISO 27701:2019 · 2 controls

  • 5.7.3 Management review
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 234 · 1 control

  • CPS234-32 Annual Review and Testing of Response Plans

Australia Consumer Data Right - Banking (CDR) · 1 control

C5 (Germany) · 1 control

  • C5-BCM-04 Verification, updating and testing of the business continuity

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

NIS2 Directive · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171A - Assessing Security Requirements for Controlled Unclassified Information (CUI) · 1 control

NIST SP 800-172 · 1 control

  • 3.2.2e Practical Exercises in Awareness Training

PCI 3DS Core Security Standard · 1 control

  • P1-7.1.3 P1-7.1.3 Plan reviewed and tested every year

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.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.

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 64 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls