PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.10.3: 12.10.3 Incident response personnel available 24/7

The entity must name specific personnel who are reachable around the clock (24/7) to handle any suspected or confirmed security incident. The guidance explains this is often arranged through a response team working a rotating schedule, made up of permanently assigned core members and on-demand specialists called in according to their expertise and the nature of the incident, so that someone trained and familiar with the plan is always on hand. Customized approach objective: incidents receive an immediate response where appropriate.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

  • CIS-17.1 Designate Personnel to Manage Incident Handling
  • 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

NIST SP 800-53 Rev 5 · 5 controls

SOC 2 · 4 controls

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

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

APRA CPS 234 · 2 controls

  • CPS234-30 Detection and Response Mechanisms
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

FedRAMP High · 2 controls

  • IR-2 Incident Response Training
  • IR-7 Incident Response Assistance

FedRAMP Moderate · 2 controls

  • IR-2 Incident Response Training
  • IR-7 Incident Response Assistance

ISO 22301:2019 · 2 controls

  • 8.4.2 Response structure
  • 8.4.3 Warning and communication

ISO 27001:2022 · 2 controls

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

ISO 27002:2022 · 2 controls

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

NIST SP 800-172 · 2 controls

  • 3.6.1e Establish Security Operations Center (SOC)
  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-28 Continuous incident detection and response (Excellent)

AWS Well-Architected Security Pillar · 1 control

  • SEC10-BP01 Identify key personnel and external resources

Azure Security Benchmark · 1 control

  • ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

NIS2 Directive · 1 control

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

NIST SP 800-171 Rev 3 · 1 control

  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

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

MCP endpointAll PCI DSS 4.0 controls