# IR-08 Incident Response Plan

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. 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 (identified by name and/or by role) and organizational elements]; 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 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.
Guidance: It is important that organizations develop and implement a coordinated approach to incident response. Organizational mission and business functions determine the structure of incident response capabilities. As part of the incident response capabilities, organizations consider the coordination and sharing of information with external organizations, including external service providers and other organizations involved in the supply chain. For incidents involving personally identifiable information (i.e., breaches), include a process to determine whether notice to oversight organizations or affected individuals is appropriate and provide that notice accordingly.

## Enhancements (1)
- IR-08(01) Breaches. Baselines: privacy
Each enhancement's statement: /api/v1/controls/IR-08?fields=enhancements

## Patterns that use it (6)
- Critical (1): SP-036 Incident Response
- Important (4): SP-031 Security Monitoring and Response; SP-034 Cyber Resilience; SP-042 Third Party Risk Management; SP-054 CBDC and Digital Currency Infrastructure (draft)
- Standard (1): SP-029 Zero Trust Architecture

## Clauses by framework (63 frameworks)
- iso_27001_2022: 7.5, A.5.24
- iso_27002_2022: 5.24
- cobit_2019: DSS02
- pci_dss_v4: 12.10
- nist_csf_2: DE.AE-03, DE.AE-08, GV.SC-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. OSA's own, not in NIST's crosswalk: GV.SC-08
- cis_controls_v8: CIS 17, CIS 17.3, CIS 17.4, CIS 17.9
- finos_ccc: CCC-C15
- nis2: Art. 21(2)(b)
- bsi_grundschutz: DER.2.1
- dora: Art.17(1)
- bio2: 5.24
- rbi_csf: Annex1.19, ITGRCA.27
- fisc: FISC.O4
- lgpd_bcb: BCB.Art.5, BCB.Art.5-Supp, BCB.Art.8, LGPD.Art.48
- hkma_tme1: TME1.5.4, TME1.7.5
- mlps_2: 8.1.10.10, 8.1.10.11
- dnb_good_practice: DNB.15.1
- cra: CRA.Art14
- swift_cscf: SWIFT.7.1
- cbb_tm: TM-13
- cbuae: CR-9
- nca_ecc: 2-13
- qatar_nia: IM
- sama_csf: 3.6
- uae_ia: T11
- bog_cisd: CISD-VII
- bom_ctrm: 5.1
- cbe_csf: CD-2
- cbn_csf: Part3.6
- popia: s22
- sa_js2: JS2-7.4
- bcbs_239: Principle 13
- bot_cyber: Ch4.1
- cpmi_pfmi: CG.RR, PFMI.P17
- eba_ict: 3.5(d), 3.7.3
- ecb_croe: CROE.2.5.1
- ffiec_is: III.D
- hipaa_sr: §164.308(a)(6)(i)
- iosco_cyber: PFMI-17, RR-1, RR-5
- nydfs_500: 500.16
- sebi_cscrf: CCMP, RS.IM, RS.MA
- cmmc_2: IR
- nerc_cip: CIP-008-6
- doe_c2m2: RESPONSE
- api_1164: Sec 10
- awia: AWWA Sec 6, Sec 2013(b)
- iaea_nss: Sec 7
- tiber_eu: TIBER.BT
- fda_cyber: INC-1
- hitrust_csf: 11.a
- iso_27799: 16.1
- lloyds_ms: CRM.3, MS8.5
- naic_ds: 4F-a
- nhs_dspt: NDG-6.1
- solvency_ii: EIOPA-ICT-4.9
- csa_ccm_v4: SEF-01, SEF-03
- csa_aicm: SEF-01, SEF-03
- ccss_v9: 1.06.1, 1.06.3, 1.06.4
- mica: Art.62(8), Art.64(1)
- basel_sco60: SCO60.50, SCO60.73
- bssc: GSP-05
- sec_custody_digital: SEC-CD-11
- dpdpa: Act.8(6), Rules.7(1), Rules.7(2)
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-08
- Clauses only: /api/v1/controls/IR-08?fields=mappings
- Page for people: /controls/ir-08/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.