# IR-02 Incident Response Training

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

Statement: a. Provide incident response training to system users consistent with assigned roles and responsibilities: 1. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility or acquiring system access; 2. When required by system changes; and 3. [Assignment: organization-defined frequency] thereafter; and b. Review and update incident response training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
Guidance: Incident response training is associated with the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail are included in such training. For example, users may only need to know who to call or how to recognize an incident; system administrators may require additional training on how to handle incidents; and incident responders may receive more specific training on forensics, data collection techniques, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of AT-02 or AT-03. Events that may precipitate an update to incident response training content include, but are not limited to, incident response plan testing or response to an actual incident (lessons learned), assessment or audit findings, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.

## Enhancements (3)
- IR-02(01) Simulated Events. Baselines: high
- IR-02(02) Automated Training Environments. Baselines: high
- IR-02(03) Breach. Baselines: privacy
Each enhancement's statement: /api/v1/controls/IR-02?fields=enhancements

## Patterns that use it (9)
- Critical (1): SP-036 Incident Response
- Important (2): SP-014 Awareness and Training Pattern; SP-031 Security Monitoring and Response
- Standard (6): 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-023 Industrial Control Systems

## Clauses by framework (59 frameworks)
- iso_27001_2022: A.5.24, A.6.3. OSA's own, not in NIST's crosswalk: A.5.24
- iso_27002_2022: 5.24
- cobit_2019: DSS02
- pci_dss_v4: 12.10
- nist_csf_2: PR.AT-02. OSA's own, not in NIST's crosswalk: PR.AT-02
- cis_controls_v8: CIS 14.6, CIS 17, CIS 17.1, CIS 17.5
- iso_42001_2023: A.8.4
- nis2: Art. 21(2)(b)
- anssi: Hygiene.4, Hygiene.35, SecNumCloud.17.1
- osfi_b13: B-13.2.5, B-13.3.4
- finma_circular: IV.A(41), IV.A(42), IV.C(70), IV.D(71)
- gdpr: Art.33(2), Art.39(1)(b)
- dora: Art.13(6), Art.17(3)(d)
- bio2: 5.24
- rbi_csf: Annex1.19, Annex1.23, ITGRCA.27
- fisc: FISC.O4
- lgpd_bcb: BCB.Art.5
- hkma_tme1: TME1.7.5
- dnb_good_practice: DNB.15.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
- bot_cyber: Ch4.1
- cpmi_pfmi: CG.RR, PFMI.P17
- eba_ict: 3.5(d)
- ecb_croe: CROE.2.5.1
- ffiec_is: III.D
- hipaa_sr: §164.308(a)(6)(i)
- iosco_cyber: RR-1
- nydfs_500: 500.16
- sebi_cscrf: RS.MA
- cmmc_2: IR
- nerc_cip: CIP-008-6
- nrc_73_54: RG5.71-B-CP
- 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: DCS-11, SEF-03
- csa_aicm: DCS-11, SEF-03
- bssc: GSP-05
- sec_custody_digital: SEC-CD-11
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-02
- Clauses only: /api/v1/controls/IR-02?fields=mappings
- Page for people: /controls/ir-02/