← Controls / IR

IR-01 Policy and Procedures

Incident Response

Low Moderate High Privacy

Description

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] incident response policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the incident response policy and the associated incident response controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the incident response policy and procedures; and c. Review and update the current incident response: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

Supplemental Guidance

Incident response policy and procedures address the controls in the IR family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of incident response policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to incident response policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

Changes from Rev 4

Title changed from 'Incident Response Policy and Procedures' Requires the selection (one or more) of organization-level; mission/business process-level; system-level incident response policies Adds text requiring consistency with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines Requires the designation of a specific official to manage the development, documentation, and dissemination of the incident response policy and procedures New parameters require update to policy and procedures as a result of specified events in addition to specified frequency Discussion amplifies the need for policy and procedures for risk management, and to help provide security and privacy assurance

Compliance Mappings

ISO 27001:2022

5.25.37.5A.5.1A.5.2A.5.4A.5.24A.5.31A.5.36A.5.37

ISO 27002:2022

5.15.246.8

COBIT 2019

DSS02

CIS Controls v8

CIS 17CIS 17.1CIS 17.4CIS 17.5

NIST CSF 2.0

GV.OC-03GV.OV-01GV.PO-01GV.PO-02GV.SC-03GV.SC-08ID.IM-01ID.IM-02ID.IM-03RC.RP-04

SOC 2 TSC

CC1.2-POF1CC1.4-POF1CC2.2-POF1CC2.2-POF3CC2.2-POF7CC2.2-POF10CC5.3CC5.3-POF1CC5.3-POF6CC7.2-POF1CC7.3CC7.3-POF1CC7.4CC7.4-POF1CC7.4-POF2CC7.4-POF3CC7.4-POF4CC7.4-POF5CC7.4-POF6CC7.4-POF10CC7.4-POF11CC7.4-POF12CC7.4-POF13P1.1-POF5

PCI DSS v4.0.1

12.112.10

CSA CCM v4

BCR-09CEK-19SEF-01SEF-02SEF-08

CSA AICM v1

BCR-09CEK-19SEF-01SEF-02SEF-08SEF-09

FINOS CCC

CCC-C15

ISO 42001:2023

A.8.4

NIS2 Directive

Art. 21(2)(b)

PRA Operational Resilience

SS1/21-8.1

BSI IT-Grundschutz

DER.2.1

ANSSI

Hygiene.2Hygiene.35Hygiene.40SecNumCloud.6.1SecNumCloud.17.1

FINMA Circular 2023/1

IV.A(23)IV.A(41)IV.C(70)

OSFI B-13

B-13.2.5B-13.3.4

EU GDPR

Art.33(1)Art.33(2)Art.34(1)Art.34(2)

EU DORA

Art.17(1)Art.17(2)Art.17(3)

BIO2

5.15.246.8

RBI CSF

Annex1.19ITGRCA.27

FISC Security Guidelines

FISC.O4

LGPD + BCB 4893

BCB.Art.2BCB.Art.5LGPD.Art.48

HKMA TM-E-1

TME1.2.5TME1.5.4TME1.7.5

MLPS 2.0

8.1.10.108.1.10.11

DNB Good Practice

DNB.1.2DNB.15.1DNB.15.2

EU CRA

CRA.Art14CRA.II.6CRA.Info.2

SWIFT CSCF

SWIFT.7.1

SAMA CSF

1.23.6

NCA ECC

1-32-13

UAE IA

T3T11

CBB TM

TM-13

Qatar NIA

IM

CBUAE

CR-9

CBE CSF

CD-2

SA JS2

JS2-7.4

CBN CSF

Part1.3Part3.6

BoG CISD

CISD-VII

POPIA

s19s22

BoM CTRM

5.1

IOSCO Cyber Resilience

GOV-1PFMI-17RR-1

CPMI-IOSCO PFMI

CG.RRPFMI.P17

FFIEC IS

II.C.1III.CIII.D

NYDFS 500

500.3500.16

HIPAA Security Rule

§164.308(a)(6)(i)§164.316(a)

ECB CROE

CROE.2.5.1

EBA ICT Guidelines

3.4.13.5(d)3.7.3

SEBI CSCRF

CCMPRS.MA

BOT Cyber Resilience

Ch4.1

CMMC 2.0

IR

NERC CIP

CIP-008-6

10 CFR 73.54

RG5.71-B-CP

TSA Pipeline SD

SD-1 Sec 2

FERC CIP Orders

Order 888

DOE C2M2 v2.1

RESPONSE

API 1164

Sec 10

AWIA

AWWA Sec 6Sec 2013(b)

IAEA NSS 17-T

Sec 7

TIBER-EU

TIBER.BT

PCI HSM

10

Solvency II

Art.41(3)DR.266EIOPA-ICT-4.9

Lloyd's Minimum Standards

CRM.3MS8.2MS8.5

NAIC Insurance Data Security

4F-a

PRA SS1/23

P5.3

HITRUST CSF v11

04.a11.a

FDA Cybersecurity Guidance

INC-1

ISO 27799

5.116.1

NHS DSPT

NDG-6.1

CCSS v9.0

1.06.1

MiCA

Art.62(7)Art.62(8)Art.64(1)

Basel SCO60

SCO60.23SCO60.50SCO60.53SCO60.73

BSSC Standards

GSP-05TIS-06

SEC Custody (Digital Assets)

SEC-CD-11

ISO 17799 (legacy)

10.4.113.113.2.115.1.1

COBIT 4.1 (legacy)

PO9.5PO9.6DS5.6DS8.2PC5