PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.10.1: 12.10.1 Incident response plan ready for activation

An incident response plan must exist and be ready to activate if a security incident is suspected or confirmed. At minimum it covers: roles and duties, plus approaches for communication and for contacting parties, including at least notifying payment brands and acquirers; response procedures giving specific containment and mitigation steps per incident type; procedures for business recovery and continuity; processes for backing up data; an analysis of the legal duties to report compromises; coverage of, and responses covering, every critical system component; and reference to, or inclusion of, the payment brands' incident response procedures. Objective under the customized approach: a thorough incident response plan meeting card brand expectations is kept.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 106 controls across 29 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 · 10 controls

  • CP-1 Policy and Procedures
  • CP-2 Contingency Plan
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan

FedRAMP Moderate · 10 controls

  • CP-1 Policy and Procedures
  • CP-2 Contingency Plan
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan

CIS Controls v8 · 9 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-17.1 Designate Personnel to Manage Incident Handling
  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.5 Assign Key Roles and Responsibilities
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

NIST SP 800-53 Rev 5 · 8 controls

ISO 22301:2019 · 7 controls

  • 7.1 Resources
  • 8.1 Operational planning and control
  • 8.4.1 General
  • 8.4.2 Response structure
  • 8.4.3 Warning and communication
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery

NIST Cybersecurity Framework 2.0 · 7 controls

  • NIST-CSF-GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
  • 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-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
  • NIST-CSF-RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
  • NIST-CSF-RS.MI-01 Incidents are contained

ISO 27001:2022 · 6 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 5.30 ICT readiness for business continuity
  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

APRA CPS 234 · 4 controls

  • CPS234-30 Detection and Response Mechanisms
  • CPS234-35 APRA Notification of Material Incidents within 72 Hours
  • CPS234-P24 Information Security Response Plans
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

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

CMMC 2.0 · 3 controls

ISO 27002:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents
  • 6.8 Information security event reporting

AWS Well-Architected Security Pillar · 2 controls

  • SEC10-BP01 Identify key personnel and external resources
  • SEC10-BP02 Develop incident management plans

Azure Security Benchmark · 2 controls

  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • ASBv3-IR-1 Preparation - update incident response plan and handling process

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

  • CFTC-SS-16 Security Incident Response Plan and Testing
  • CFTC-SS-19 Prompt Notification to the Commission

ISO 27701:2019 · 2 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

NIS2 Directive · 2 controls

  • Art.21.2.b Incident handling
  • Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

PCI 3DS Core Security Standard · 2 controls

  • P1-7.1.1 P1-7.1.1 Incident-management policy and procedures
  • P1-7.1.2 P1-7.1.2 Incident response plan with its required elements

SOC 2 · 2 controls

  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-P6.6 P6.6 Notifying breaches and incidents

ACSC Essential Eight · 1 control

  • E8-APP-ML2 Application Control (ML2)

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

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

APPI · 1 control

  • APPI-A26 Report of Leakage to the Commission and Notification to the Person

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

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

  • AEO-12 Crisis Management and Incident Recovery

C5 (Germany) · 1 control

  • C5-SIM-01 Policy for security incident management

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

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

MCP endpointAll PCI DSS 4.0 controls