800-53 · IR Incident Response
IR-8
Incident Response Plan
frameworkNIST SP 800-53 Rev 5.2
sectionIR Incident Response
csf 2.0DE.AE-03 DE.AE-08 ID.IM-01 ID.IM-02 ID.IM-03 ID.IM-04 RC.RP-01 RC.RP-02 RC.RP-04 RC.RP-06 RS.AN-08 RS.MA-01 RS.MA-05
topicsIncident Response
frameworks7 5 1
Official texta. Develop an incident response plan that:
1. Provides the organization with a roadmap for implementing its incident response capability;
2. Describes the structure and organization of the incident response capability;
3. Provides a high-level approach for how the incident response capability fits into the overall organization;
4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
5. Defines reportable incidents;
6. Provides metrics for measuring the incident response capability within the organization;
7. Defines the resources and management support needed to effectively maintain and mature an incident response capability;
8. Addresses the sharing of incident information;
9. Is reviewed and approved by [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]; and
10. Explicitly designates responsibility for incident response to [Assignment: organization-defined entities, personnel, or roles].
b. Distribute copies of the incident response plan to [Assignment: organization-defined incident response personnel];
c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;
d. Communicate incident response plan changes to [Assignment: organization-defined organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and
e. Protect the incident response plan from unauthorized disclosure and modification.NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Provides the organization with a roadmap for implementing its incident response capability;
2. Describes the structure and organization of the incident response capability;
3. Provides a high-level approach for how the incident response capability fits into the overall organization;
4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
5. Defines reportable incidents;
6. Provides metrics for measuring the incident response capability within the organization;
7. Defines the resources and management support needed to effectively maintain and mature an incident response capability;
8. Addresses the sharing of incident information;
9. Is reviewed and approved by [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]; and
10. Explicitly designates responsibility for incident response to [Assignment: organization-defined entities, personnel, or roles].
b. Distribute copies of the incident response plan to [Assignment: organization-defined incident response personnel];
c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;
d. Communicate incident response plan changes to [Assignment: organization-defined organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and
e. Protect the incident response plan from unauthorized disclosure and modification.NIST SP 800-53 Rev 5.2 control statement (public domain)
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 Response8 loosely related (not mappings)DE.AE-03 Information is correlated from multiple sources Only shares CSF DE.AE-03: related, not a mapping DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria Only shares CSF DE.AE-08: 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 RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed Only shares CSF RC.RP-02: related, not a mapping RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms Only shares CSF RC.RP-04: related, not a mapping RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed Only shares CSF RC.RP-06: related, not a mapping RS.AN-08 An incident's magnitude is estimated and validated Only shares CSF RS.AN-08: related, not a mapping RS.MA-05 The criteria for initiating incident recovery are applied Only shares CSF RS.MA-05: related, not a mapping |
| ISO 27001 | A.5.24A.5.25A.5.26Clause 7.5.1Clause 7.5.2Clause 7.5.3 | Information security incident management planning and preparation; Assessment and decision on information security events… | Crosswalk | Same topic: Incident Response NIST SP 800-53 → ISO 27001 mapping 9 loosely related (not mappings)A.5.27 Learning from information security incidents Only shares CSF ID.IM-03, ID.IM-04, RC.RP-06, RS.MA-01: related, not a mapping Clause 10.1 Continual improvement Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.RP-06: related, not a mapping …and 1 more in the downloads |
| 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 Response14 loosely related (not mappings)CIS 11.1 Establish and Maintain a Data Recovery Process Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02: related, not a mapping CIS 13.1 Centralize Security Event Alerting Only shares CSF DE.AE-03, DE.AE-08: related, not a mapping CIS 13.11 Tune Security Event Alerting Thresholds Only shares CSF DE.AE-03, DE.AE-08: related, not a mapping CIS 8.1 Establish and Maintain an Audit Log Management Process Only shares CSF DE.AE-03: related, not a mapping …and 6 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)6 loosely related (not mappings)CC7.5 Recovering from identified security incidents Only shares CSF ID.IM-03, ID.IM-04, RC.RP-01, RC.RP-02…: related, not a mapping A1.3 Testing recovery plan procedures Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02: related, not a mapping A1.2 Environmental protections, backups and recovery infrastructure Only shares CSF RC.RP-02, RC.RP-04: related, not a mapping A1.1 Capacity management to meet availability commitments Only shares CSF RC.RP-04: related, not a mapping |
| 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 Response9 loosely related (not mappings)12.10.6 Plan updated from lessons learned and industry changes Only shares CSF ID.IM-02, ID.IM-04, RC.RP-02, RC.RP-06…: related, not a mapping 1.2.4 Accurate account-data flow diagram maintained Only shares CSF DE.AE-03, RC.RP-02, RC.RP-04, RS.AN-08: related, not a mapping 1.2.3 Accurate network diagram maintained Only shares CSF RC.RP-02, RC.RP-04, RS.AN-08: related, not a mapping 12.5.1 Inventory of in-scope system components Only shares CSF DE.AE-03, RC.RP-04, RS.AN-08: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF DE.AE-03, RS.AN-08: related, not a mapping 10.5.1 Audit logs retained 12 months, three immediately available Only shares CSF DE.AE-03, RC.RP-06: related, not a mapping …and 1 more in the downloads |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3 | Incident Handling; Incident Response Testing | Crosswalk | Same topic: Incident Response8 loosely related (not mappings)CA.L2-3.12.3 Security Control Monitoring Only shares CSF DE.AE-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping CM.L2-3.4.9 User-Installed Software Only shares CSF DE.AE-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping RA.L2-3.11.1 Risk Assessments Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RS.AN-08: related, not a mapping SI.L2-3.14.6 Monitor Communications for Attacks Only shares CSF DE.AE-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping SI.L2-3.14.7 Identify Unauthorized Use Only shares CSF DE.AE-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response15 loosely related (not mappings)§164.308(a)(7)(ii)(B) Disaster Recovery Plan Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.308(a)(1)(ii)(B) Risk Management Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF DE.AE-03, ID.IM-01, ID.IM-02, ID.IM-03…: related, not a mapping §164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.316(a) Policies and Procedures Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.316(b)(2)(iii) Updates Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.308(a)(1)(ii)(A) Risk Analysis Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RS.AN-08: related, not a mapping …and 7 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)2 loosely related (not mappings)Art.32(1)(c) Security of processing Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02: related, not a mapping |
| NIS2 | 3.13.5 | Incident handling policy; Incident response | Crosswalk | Same topic: Incident Response4 loosely related (not mappings)4.1 Business continuity and disaster recovery plan Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick)10 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-03, 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-03, DE.AE-08: related, not a mapping ISM-0109 Event logs from workstations are analysed in a timely manner to detect cyber security… Only shares CSF DE.AE-03: related, not a mapping ISM-1509 Privileged access events are centrally logged Only shares CSF DE.AE-03: related, not a mapping ISM-1515 Restoration of data, applications and settings from backups to a common point in time… Only shares CSF RC.RP-02: related, not a mapping ISM-1623 PowerShell module logging, script block logging and transcription events are centrally… Only shares CSF DE.AE-03: related, not a mapping ISM-1660 Allowed and blocked application control events are centrally logged Only shares CSF DE.AE-03: related, not a mapping ISM-1683 Successful and unsuccessful multi-factor authentication events are centrally logged Only shares CSF DE.AE-03: related, not a mapping …and 2 more in the downloads |
| 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)10 loosely related (not mappings)Art.11(3) Response and recovery Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02: related, not a mapping Art.12(6) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02: related, not a mapping …and 2 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) |
| 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.