| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| ISO 27001 | A.5.26 | Response to information security incidents | Crosswalk | Same topic: Mitigation |
| CIS v8.1 | — | No requirement | No mapping in our data | No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards). |
| SOC 2 | CC7.4 | Responding to identified security incidents | Editorial | Same topic: Mitigation (editorial pick) |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Crosswalk | Same topic: Mitigation |
| CMMC | IR.L2-3.6.1 | Incident Handling | Crosswalk | Same topic: Mitigation |
| 800-53 | IR-4 | Incident Handling | Crosswalk | Same topic: Mitigation |
| HIPAA | §164.308(a)(6)(ii) | Response and Reporting | Crosswalk | Same topic: Mitigation1 loosely related (not mappings) |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | 3.5 | Incident response | Crosswalk | Same topic: Mitigation1 loosely related (not mappings) |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.11(2)(c)Art.17(3)(f) | Response and recovery; ICT-related incident management process | Editorial | Same topic: Mitigation (editorial pick) |
| 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.