800-53 · IR Incident Response
IR-4
Incident Handling
frameworkNIST SP 800-53 Rev 5.2
sectionIR Incident Response
csf 2.0DE.AE-02 DE.AE-03 DE.AE-06 DE.AE-08 ID.IM-01 ID.IM-02 ID.IM-03 RC.CO-03 RC.CO-04 RC.RP-01 RC.RP-02 RC.RP-06 RS.AN-03 RS.AN-06 RS.AN-07 RS.AN-08 RS.CO-02 RS.CO-03 RS.MA-02 RS.MA-03 RS.MA-04 RS.MA-05 RS.MI-01 RS.MI-02
topicsIncident Response, Mitigation, Lessons Learned
frameworks7 5 1
Official texta. Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery;
b. Coordinate incident handling activities with contingency planning activities;
c. Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and
d. Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.NIST SP 800-53 Rev 5.2 control statement (public domain)
b. Coordinate incident handling activities with contingency planning activities;
c. Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and
d. Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.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-03ID.IM-04RC.RP-06RS.MA-01RS.MA-02RS.MA-03RS.MA-04RS.MI-01RS.MI-02 | Improvements are identified from execution of operational processes, procedures, and activities; Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved… | Crosswalk | Same topic: Lessons Learned, Incident Response, Mitigation15 loosely related (not mappings)DE.AE-02 Potentially adverse events are analyzed to better understand associated activities Only shares CSF DE.AE-02: related, not a mapping DE.AE-03 Information is correlated from multiple sources Only shares CSF DE.AE-03: related, not a mapping DE.AE-06 Information on adverse events is provided to authorized staff and tools Only shares CSF DE.AE-06: 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.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders Only shares CSF RC.CO-03: related, not a mapping RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Only shares CSF RC.CO-04: 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 …and 7 more in the downloads |
| ISO 27001 | A.5.24A.5.25A.5.26A.5.27Clause 10.1A.8.16 | Information security incident management planning and preparation; Assessment and decision on information security events… | Crosswalk | Same topic: Incident Response, Mitigation, Lessons Learned NIST SP 800-53 → ISO 27001 mapping 8 loosely related (not mappings)A.5.28 Collection of evidence Only shares CSF RC.CO-03, RS.AN-06, RS.AN-07, RS.MA-02: related, not a mapping Clause 7.4 Communication Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping |
| CIS v8.1 | CIS 17.4CIS 17.1CIS 17.5CIS 17.7CIS 17.8CIS 17.9 | Establish and Maintain an Incident Response Process; Designate Personnel to Manage Incident Handling… | Crosswalk | Same topic: Incident Response, Lessons Learned21 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping CIS 17.6 Define Mechanisms for Communicating During Incident Response Only shares CSF RC.CO-04, RS.CO-03: related, not a mapping CIS 13.1 Centralize Security Event Alerting Only shares CSF DE.AE-03, DE.AE-06, DE.AE-08: related, not a mapping CIS 13.11 Tune Security Event Alerting Thresholds Only shares CSF DE.AE-03, DE.AE-06, DE.AE-08: related, not a mapping CIS 11.1 Establish and Maintain a Data Recovery Process Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping …and 13 more in the downloads |
| SOC 2 | CC7.3CC7.4CC7.5 | Evaluating security events to determine if they are incidents; Responding to identified security incidents… | Editorial | Same topic: Incident Response, Mitigation, Lessons Learned (editorial pick)4 loosely related (not mappings)CC2.3 Communication with external parties Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping CC7.2 Monitoring system components for anomalies Only shares CSF DE.AE-02, DE.AE-03: related, not a mapping A1.2 Environmental protections, backups and recovery infrastructure Only shares CSF RC.RP-02: related, not a mapping |
| PCI DSS | 12.10.112.10.212.10.312.10.412.10.6 | Incident response plan ready to activate; Incident response plan reviewed and tested annually… | Crosswalk | Same topic: Incident Response, Mitigation, Lessons Learned25 loosely related (not mappings)10.4.1 Security event and critical logs reviewed daily Only shares CSF DE.AE-02, DE.AE-03, RS.AN-03, RS.AN-08…: related, not a mapping 10.2.1 Audit logs enabled and active Only shares CSF DE.AE-02, DE.AE-03, RS.AN-03, RS.AN-07…: related, not a mapping 10.3.3 Logs promptly backed up to a central server Only shares CSF DE.AE-02, DE.AE-03, DE.AE-06, RS.AN-06…: related, not a mapping 1.2.4 Accurate account-data flow diagram maintained Only shares CSF DE.AE-03, RC.RP-02, 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, RS.AN-06: related, not a mapping 12.8.2 Written agreements with service providers Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping 12.8.4 Service provider compliance monitored annually Only shares CSF ID.IM-02, RC.CO-03, RS.CO-03: related, not a mapping 1.2.3 Accurate network diagram maintained Only shares CSF RC.RP-02, RS.AN-08: related, not a mapping …and 17 more in the downloads |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3IR.L2-3.6.2 | Incident Handling; Incident Response Testing… | Crosswalk | Same topic: Incident Response, Mitigation, Lessons Learned NIST SP 800-171r2 Appendix D 8 loosely related (not mappings)CA.L2-3.12.3 Security Control Monitoring Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: related, not a mapping CM.L2-3.4.9 User-Installed Software Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: related, not a mapping SI.L2-3.14.6 Monitor Communications for Attacks Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: related, not a mapping SI.L2-3.14.7 Identify Unauthorized Use Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: 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 AU.L2-3.3.6 Reduction & Reporting Only shares CSF RS.AN-03, RS.AN-06, RS.AN-07: related, not a mapping |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response, Mitigation17 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: related, not a mapping §164.314(a)(2)(i) Business Associate Contracts Only shares CSF ID.IM-03, RC.CO-03, RS.AN-06, RS.AN-07…: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF ID.IM-03, RC.CO-03, RS.AN-06, RS.AN-07…: related, not a mapping §164.312(b) Audit Controls Only shares CSF DE.AE-02, DE.AE-03, ID.IM-01, ID.IM-02…: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Only shares CSF RC.CO-03, RS.AN-06, RS.AN-07, RS.CO-02…: related, not a mapping §164.308(a)(7)(ii)(B) Disaster Recovery Plan Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-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, RC.CO-04…: 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, RC.CO-04…: related, not a mapping …and 9 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.34(1) Communication of a personal data breach to the data subject Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02: related, not a mapping |
| NIS2 | 3.13.53.6 | Incident handling policy; Incident response… | Crosswalk | Same topic: Incident Response, Mitigation, Lessons Learned6 loosely related (not mappings)4.3 Crisis management Only shares CSF DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08…: related, not a mapping 3.4 Event assessment and classification Only shares CSF RS.MA-02, RS.MA-03, RS.MA-04: related, not a mapping 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)12 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-02, DE.AE-03, DE.AE-06, 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-02, DE.AE-03, DE.AE-06, 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-02, DE.AE-03: related, not a mapping ISM-1907 Event logs from non-internet-facing servers are analysed in a timely manner to detect… Only shares CSF DE.AE-02, DE.AE-03: related, not a mapping ISM-0123 Cyber security incidents are reported to the chief information security officer, or one… Only shares CSF RS.CO-02: related, not a mapping ISM-0140 Cyber security incidents are reported to ASD as soon as possible after they occur or… Only shares CSF RS.CO-02: 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 …and 4 more in the downloads |
| DORA | Art.11(2)(b)Art.11(2)(c)Art.13(2)Art.13(3)Art.17(1)Art.17(3)Art.17(3)(f)Art.18(1) | Response and recovery; Response and recovery… | Editorial | Same topic: Incident Response, Mitigation, Lessons Learned (editorial pick)16 loosely related (not mappings)Art.17(2) ICT-related incident management process Only shares CSF RS.AN-03, RS.AN-06, RS.AN-07: related, not a mapping Art.12(6) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping …and 8 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, Lessons Learned (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.