NIST CSF 2.0 · Respond (RS)
RS.MA-03
Incidents are categorized and prioritized
frameworkNIST Cybersecurity Framework 2.0
sectionRespond (RS)
topicsIncident Response
frameworks7 5 1
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| 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 Response |
| 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 Response |
| 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) |
| PCI DSS | 12.10.112.10.212.10.312.10.4 | Incident response plan ready to activate; Incident response plan reviewed and tested annually… | Crosswalk | Same topic: Incident Response |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3 | Incident Handling; Incident Response Testing | Crosswalk | Same topic: Incident Response1 loosely related (not mappings) |
| 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 Response4 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RS.MA-03: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF RS.MA-03: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Only shares CSF RS.MA-03: related, not a mapping |
| 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 Response1 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) |
| 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) |
| 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.