NIST CSF 2.0 · Respond (RS)
RS.MA-05
The criteria for initiating incident recovery are applied
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| ISO 27001 | A.5.25 | Assessment and decision on information security events | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| CIS v8.1 | CIS 17.9 | Establish and Maintain Security Incident Thresholds | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| SOC 2 | — | No requirement | No mapping in our data | No mapping in our data (SOC 2 links are editorial only). |
| PCI DSS | 12.10.112.10.212.10.6 | Incident response plan ready to activate; Incident response plan reviewed and tested annually… | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| CMMC | IR.L2-3.6.1 | Incident Handling | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| 800-53 | IR-4IR-8 | Incident Handling; Incident Response Plan | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | 3.1 | Incident handling policy | No mapping. Only shares CSF RS.MA-05: related, not a mapping | |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | — | No requirement | No mapping in our data | No mapping in our data (DORA links are editorial, and its technical standards are not mapped). |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| 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.