# IR-04 Incident Handling

NIST SP 800-53 control. Family: IR Incident Response. Function: corrective. Baselines: low, moderate, high, privacy. Mapping licence: CC BY-SA 4.0.

Statement: a. 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.
Guidance: Organizations recognize that incident response capabilities are dependent on the capabilities of organizational systems and the mission and business processes being supported by those systems. Organizations consider incident response as part of the definition, design, and development of mission and business processes and systems. Incident-related information can be obtained from a variety of sources, including audit monitoring, physical access monitoring, and network monitoring; user or administrator reports; and reported supply chain events. An effective incident handling capability includes coordination among many organizational entities (e.g., mission or business owners, system owners, authorizing officials, human resources offices, physical security offices, personnel security offices, legal departments, risk executive [function], operations personnel, procurement offices). Suspected security incidents include the receipt of suspicious email communications that can contain malicious code. Suspected supply chain incidents include the insertion of counterfeit hardware or malicious code into organizational systems or system components. For federal agencies, an incident that involves personally identifiable information is considered a breach. A breach results in unauthorized disclosure, the loss of control, unauthorized acquisition, compromise, or a similar occurrence where a person other than an authorized user accesses or potentially accesses personally identifiable information or an authorized user accesses or potentially accesses such information for other than authorized purposes.

## Enhancements (15)
- IR-04(01) Automated Incident Handling Processes. Baselines: moderate, high
- IR-04(02) Dynamic Reconfiguration
- IR-04(03) Continuity of Operations
- IR-04(04) Information Correlation. Baselines: high
- IR-04(05) Automatic Disabling of System
- IR-04(06) Insider Threats
- IR-04(07) Insider Threats — Intra-organization Coordination
- IR-04(08) Correlation with External Organizations
- IR-04(09) Dynamic Response Capability
- IR-04(10) Supply Chain Coordination
- IR-04(11) Integrated Incident Response Team. Baselines: high
- IR-04(12) Malicious Code and Forensic Analysis
- IR-04(13) Behavior Analysis
- IR-04(14) Security Operations Center
- IR-04(15) Public Relations and Reputation Repair
Each enhancement's statement: /api/v1/controls/IR-04?fields=enhancements

## Patterns that use it (27)
- Critical (6): SP-031 Security Monitoring and Response; SP-036 Incident Response; SP-047 Secure Agentic AI Frameworks; SP-049 AI in Security Operations (draft); SP-051 Tokenised Asset Security Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (19): SP-001 Client Module; SP-002 Server Module; SP-006 Wireless- Private Network Pattern; SP-007 Wireless- Public Hotspot Pattern; SP-008 Public Web Server Pattern; SP-017 Secure Network Zone Module; SP-021 Realtime Collaboration Pattern; SP-023 Industrial Control Systems; SP-027 Secure LLM Usage; SP-029 Zero Trust Architecture; SP-030 API Security; SP-034 Cyber Resilience; SP-035 Offensive Security Testing; SP-037 Privileged User Management; SP-043 Security Metrics and Measurement; SP-046 External Attack Surface Management; SP-048 Offensive AI and Deepfake Defence (draft); SP-052 Decentralised Identity & Verifiable Credentials (draft); SP-053 Zero-Knowledge Proof Architecture (draft)
- Standard (2): SP-019 Secure Ad-Hoc File Exchange Pattern; SP-039 Client-Side Encryption and Data Privacy

## Clauses by framework (77 frameworks)
- iso_27001_2022: A.5.25, A.5.26, A.5.27, A.5.28, A.8.16. OSA's own, not in NIST's crosswalk: A.5.28, A.8.16
- iso_27002_2022: 5.24, 5.25, 5.26, 5.27, 5.28, 8.16
- cobit_2019: DSS02, DSS03
- pci_dss_v4: 10.7, 11.5, 12.10
- nist_csf_2: DE.AE-02, DE.AE-03, DE.AE-04, DE.AE-06, DE.AE-08, GV.SC-08, ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-03, RC.CO-04, RC.RP-01, RC.RP-02, RC.RP-04, RC.RP-06, RS.AN-03, RS.AN-06, RS.AN-07, RS.AN-08, RS.CO-02, RS.CO-03, RS.MA-01, RS.MA-02, RS.MA-03, RS.MA-04, RS.MA-05, RS.MI-01, RS.MI-02. OSA's own, not in NIST's crosswalk: DE.AE-04, GV.SC-08, RC.RP-04, RS.MA-01
- cis_controls_v8: CIS 13, CIS 17, CIS 17.6, CIS 17.8, CIS 17.9
- soc2_tsc: CC2.2-POF3, CC2.2-POF10, CC7.3, CC7.3-POF1, CC7.4, CC7.4-POF1, CC7.4-POF2, CC7.4-POF3, CC7.4-POF4, CC7.4-POF5, CC7.4-POF6, CC7.4-POF10, CC7.4-POF11, CC7.4-POF12, CC7.4-POF13
- finos_ccc: CCC-C15
- iso_42001_2023: A.3.3, A.8.4
- iec_62443: 3-3 SR 7.4
- nis2: Art. 21(2)(b), Art. 21(2)(j)
- mas_trm: 7, 12
- pra_op_resilience: SS1/21-8.1
- bsi_grundschutz: DER.2.1
- anssi: Hygiene.35, Hygiene.39, Hygiene.40, SecNumCloud.17.1, SecNumCloud.17.2
- osfi_b13: B-13.2.5, B-13.3.4
- finma_circular: IV.A(41), IV.A(42), IV.A(43), IV.C(70), IV.D(71), IV.D(72)
- gdpr: Art.33(1), Art.33(3), Art.33(4), Art.34(1)
- dora: Art.17(1), Art.17(3), Art.18(1), Art.18(2)
- bio2: 5.24, 5.25, 5.26, 5.27, 5.28, 8.16
- rbi_csf: Annex1.19, Annex1.22, ITGRCA.27
- fisc: FISC.O4
- lgpd_bcb: BCB.Art.5, BCB.Art.5-Supp, BCB.Art.6, BCB.Art.7, LGPD.Art.48, LGPD.Art.49
- hkma_tme1: TME1.5.4, TME1.7.5, TME1.11.3
- mlps_2: 8.1.5.4, 8.1.10.10
- dnb_good_practice: DNB.15.2
- cra: CRA.I.2k
- swift_cscf: SWIFT.7.1
- cbb_tm: TM-5, TM-12, TM-13
- cbuae: CR-3, CR-9
- nca_ecc: 2-13, 3-2, 5-1
- qatar_nia: IM
- sama_csf: 3.6
- uae_ia: T11
- bog_cisd: CISD-VII
- bom_ctrm: 4.2, 5.1
- cbe_csf: CD-2
- cbn_csf: Part3.5, Part3.6
- popia: s19, s22
- sa_js2: JS2-7.3, JS2-7.4
- bcbs_239: Principle 6
- bot_cyber: Ch4.1
- cpmi_pfmi: CG.DE, CG.LE, CG.RR, PFMI.P17
- eba_ict: 3.5(d), 3.7.3
- ecb_croe: CROE.2.4, CROE.2.5.1, CROE.2.8.1
- ffiec_is: III.B, III.C, III.D
- hipaa_sr: §164.308(a)(6)(i), §164.308(a)(6)(ii)
- iosco_cyber: DET-4, LE-1, PFMI-17, RR-1
- nydfs_500: 500.2, 500.14, 500.16
- sebi_cscrf: DE.CM, RS.AN, RS.IM, RS.MA, SOC
- cmmc_2: IR
- nerc_cip: CIP-008-6, CIP-009-6, CIP-015-1
- nrc_73_54: RG5.71-B-CP
- tsa_psd: SD-2 Sec C
- ferc_cip: Order 881, Order 888
- doe_c2m2: RESPONSE
- api_1164: Sec 10
- awia: AWWA Sec 6, Sec 2013(b)
- iaea_nss: Sec 7
- cbest: CBEST.5
- tiber_eu: TIBER.BT, TIBER.CLOSE
- pci_hsm: 10
- fda_cyber: INC-1, INC-2, VR-1
- hitrust_csf: 11.a, 11.b, 11.c
- iso_27799: 16.1, 16.2
- lloyds_ms: CRM.3, MS8.5
- naic_ds: 4, 4F-a, 4F-b, 5
- nhs_dspt: NDG-6.1, NDG-6.3, NDG-6.4
- pra_ss1_23: P5.3
- solvency_ii: DR.266, EIOPA-ICT-4.9
- csa_ccm_v4: LOG-05, SEF-02, SEF-03, SEF-05, SEF-06
- csa_aicm: LOG-05, SEF-02, SEF-03, SEF-05, SEF-06, SEF-09
- mica: Art.62(8), Art.64(1), Art.92(1)
- basel_sco60: SCO60.23, SCO60.50, SCO60.53, SCO60.55, SCO60.63, SCO60.73, SCO60.82
- bssc: GSP-05, TIS-04
- sec_custody_digital: SEC-CD-11
- dpdpa: Act.8(5), Rules.6(1)(c), Rules.7(1), Rules.7(2), Rules.Sch1.B.7
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/IR-04
- Clauses only: /api/v1/controls/IR-04?fields=mappings
- Page for people: /controls/ir-04/