PCI DSS · Requirement 12: Support information security with organizational policies and programs
12.10.4
Incident response staff trained
frameworkPCI DSS v4.0.1
sectionRequirement 12: Support information security with organizational policies and programs
csf 2.0DE.AE-08 PR.AT-02 RS.MA-02
topicsIncident Response
frameworks7 5 1
Official text · not licensableSummary (ControlMapping's wording): Incident response staff trained. 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 Response2 loosely related (not mappings)DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria Only shares CSF DE.AE-08: related, not a mapping PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind Only shares CSF PR.AT-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 Response6 loosely related (not mappings)A.5.2 Information security roles and responsibilities Only shares CSF PR.AT-02: related, not a mapping A.5.27 Learning from information security incidents Only shares CSF RS.MA-02: related, not a mapping A.6.3 Information security awareness, education and training Only shares CSF PR.AT-02: 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 Response11 loosely related (not mappings)CIS 14.9 Conduct Role-Specific Security Awareness and Skills Training Only shares CSF PR.AT-02: related, not a mapping CIS 14.2 Train Workforce Members to Recognize Social Engineering Attacks Only shares CSF PR.AT-02: related, not a mapping CIS 14.3 Train Workforce Members on Authentication Best Practices Only shares CSF PR.AT-02: related, not a mapping CIS 14.4 Train Workforce on Data Handling Best Practices Only shares CSF PR.AT-02: related, not a mapping CIS 14.5 Train Workforce Members on Causes of Unintentional Data Exposure Only shares CSF PR.AT-02: related, not a mapping …and 3 more in the downloads |
| 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) |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3 | Incident Handling; Incident Response Testing | Crosswalk | Same topic: Incident Response2 loosely related (not mappings) |
| 800-53 | IR-4IR-8IR-2IR-3 | Incident Handling; Incident Response Plan… | Crosswalk | Same topic: Incident Response4 loosely related (not mappings) |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response9 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RS.MA-02: related, not a mapping §164.308(a)(5)(ii)(B) Protection from Malicious Software Only shares CSF PR.AT-02: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF RS.MA-02: related, not a mapping …and 1 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)1 loosely related (not mappings) |
| NIS2 | 3.13.5 | Incident handling policy; Incident response | Crosswalk | Same topic: Incident Response |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick)2 loosely related (not mappings)ISM-1228 Cyber security events are analysed in a timely manner to identify cyber security incidents Only shares CSF DE.AE-08: 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-08: 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)4 loosely related (not mappings) |
| 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) |
| 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.