PCI DSS · Requirement 12: Support information security with organizational policies and programs
12.10.3
Incident response staff available around the clock
frameworkPCI DSS v4.0.1
sectionRequirement 12: Support information security with organizational policies and programs
csf 2.0DE.AE-06 GV.RR-03 ID.IM-04 RC.CO-03 RC.CO-04 RC.RP-01 RS.CO-02 RS.MA-01 RS.MA-04
topicsIncident Response
frameworks7 5 1
Official text · not licensableSummary (ControlMapping's wording): Incident response staff available around the clock. The requirement text is PCI SSC's copyright; see PCI DSS v4.0.1.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | ID.IM-04RS.MA-01RS.MA-02RS.MA-03RS.MA-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved; The incident response plan is executed in coordination with relevant third parties once an incident is declared… | Crosswalk | Same topic: Incident Response6 loosely related (not mappings)DE.AE-06 Information on adverse events is provided to authorized staff and tools Only shares CSF DE.AE-06: related, not a mapping GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies Only shares CSF GV.RR-03: related, not a mapping RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders Only shares CSF RC.CO-03: related, not a mapping RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Only shares CSF RC.CO-04: related, not a mapping RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process Only shares CSF RC.RP-01: related, not a mapping RS.CO-02 Internal and external stakeholders are notified of incidents Only shares CSF RS.CO-02: related, not a mapping |
| ISO 27001 | A.5.24A.5.25A.5.26 | Information security incident management planning and preparation; Assessment and decision on information security events… | Crosswalk | Same topic: Incident Response7 loosely related (not mappings)A.5.27 Learning from information security incidents Only shares CSF ID.IM-04, RS.MA-01: related, not a mapping |
| CIS v8.1 | CIS 17.4CIS 17.1CIS 17.5CIS 17.7CIS 17.9 | Establish and Maintain an Incident Response Process; Designate Personnel to Manage Incident Handling… | Crosswalk | Same topic: Incident Response7 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04, RS.CO-02: related, not a mapping CIS 17.6 Define Mechanisms for Communicating During Incident Response Only shares CSF RC.CO-04: related, not a mapping CIS 11.1 Establish and Maintain a Data Recovery Process Only shares CSF ID.IM-04, RC.RP-01: related, not a mapping CIS 17.3 Establish and Maintain an Enterprise Process for Reporting Incidents Only shares CSF RS.CO-02: related, not a mapping |
| SOC 2 | CC7.3CC7.4 | Evaluating security events to determine if they are incidents; Responding to identified security incidents | Editorial | Same topic: Incident Response (editorial pick)6 loosely related (not mappings)CC7.5 Recovering from identified security incidents Only shares CSF ID.IM-04, RC.CO-03, RC.CO-04, RC.RP-01: related, not a mapping CC2.3 Communication with external parties Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02: related, not a mapping CC1.2 Board independence and oversight of internal control Only shares CSF GV.RR-03: related, not a mapping CC1.3 Structures, reporting lines, authorities and responsibilities Only shares CSF GV.RR-03: related, not a mapping CC1.5 Accountability for internal control responsibilities Only shares CSF GV.RR-03: related, not a mapping |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3 | Incident Handling; Incident Response Testing | Crosswalk | Same topic: Incident Response1 loosely related (not mappings)IR.L2-3.6.2 Incident Reporting Only shares CSF RC.CO-03, RS.CO-02, RS.MA-01, RS.MA-04: related, not a mapping |
| 800-53 | IR-4IR-8IR-2IR-3 | Incident Handling; Incident Response Plan… | Crosswalk | Same topic: Incident Response |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response11 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RC.CO-03, RS.CO-02, RS.MA-01, RS.MA-04: related, not a mapping §164.314(a)(2)(i) Business Associate Contracts Only shares CSF RC.CO-03, RS.CO-02, RS.MA-01, RS.MA-04: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF RC.CO-03, RS.CO-02, RS.MA-01, RS.MA-04: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Only shares CSF RC.CO-03, RS.CO-02, RS.MA-01, RS.MA-04: related, not a mapping §164.308(a)(7)(ii)(B) Disaster Recovery Plan Only shares CSF ID.IM-04, RC.CO-04, RC.RP-01: related, not a mapping §164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Only shares CSF ID.IM-04, RC.CO-04, RC.RP-01: related, not a mapping §164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF ID.IM-04, RC.CO-04: related, not a mapping …and 3 more in the downloads |
| GDPR | Art.33(1)Art.33(5) | Notification of a personal data breach to the supervisory authority; Notification of a personal data breach to the supervisory authority | Editorial | Same topic: Incident Response (editorial pick) |
| NIS2 | 3.13.5 | Incident handling policy; Incident response | Crosswalk | Same topic: Incident Response6 loosely related (not mappings) |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick)4 loosely related (not mappings)ISM-0123 Cyber security incidents are reported to the chief information security officer, or one… Only shares CSF RS.CO-02: related, not a mapping ISM-0140 Cyber security incidents are reported to ASD as soon as possible after they occur or… Only shares CSF RS.CO-02: related, not a mapping ISM-1228 Cyber security events are analysed in a timely manner to identify cyber security incidents Only shares CSF DE.AE-06: related, not a mapping ISM-1906 Event logs from internet-facing servers are analysed in a timely manner to detect cyber… Only shares CSF DE.AE-06: related, not a mapping |
| DORA | Art.11(2)(b)Art.17(1)Art.17(3)Art.18(1) | Response and recovery; ICT-related incident management process… | Editorial | Same topic: Incident Response (editorial pick)12 loosely related (not mappings)Art.12(6) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF ID.IM-04, RC.RP-01: related, not a mapping …and 4 more in the downloads |
| CPS 234 | Para 23Para 24Para 25Para 26 | Detect and respond to incidents in a timely manner; Maintain information security response plans… | Editorial | Same topic: Incident Response (editorial pick)4 loosely related (not mappings)Para 13 Board ultimately responsible for information security Only shares CSF GV.RR-03: related, not a mapping Para 14 Define information security roles and responsibilities Only shares CSF GV.RR-03: related, not a mapping Para 35 Notify APRA of material incidents within 72 hours Only shares CSF RS.CO-02: related, not a mapping Para 36 Notify APRA of material control weaknesses within 10 business days Only shares CSF RS.CO-02: related, not a mapping |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.