NIST SP 800-171 Rev 3 03.06.05: Incident Response Plan

What else in your programme already covers this

This control maps to 43 controls across 29 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 4 controls

CIS-17.1 Designate Personnel to Manage Incident Handling
CIS-17.4 Establish and Maintain an Incident Response Process
CIS-17.5 Assign Key Roles and Responsibilities
CIS-17.6 Define Mechanisms for Communicating During Incident Response

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

PCI DSS 4.0 · 3 controls

12.10.1 Incident response plan
12.10.2 IRP reviewed and tested annually
12.10.6 IRP refined based on lessons learned

APRA CPS 234 · 2 controls

CPS234-P24 Information Security Response Plans
CPS234-P25 Response Plan Content and Escalation Mechanisms

AWS Well-Architected Security Pillar · 2 controls

SEC10-BP01 Identify key personnel and external resources
SEC10-BP02 Develop incident management plans

Azure Security Benchmark · 2 controls

ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
ASBv3-IR-1 Preparation - update incident response plan and handling process

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-SEF-01 Security Incident Management Policy and Procedures
CCM-SEF-03 Incident Response Plans

FedRAMP High · 2 controls

IR-8 Incident Response Plan
IR-9 Information Spillage Response. Respond to information spills by: a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills; b. Identifying the specific information involved in the system contamination; c. Alerting

FedRAMP Moderate · 2 controls

IR-8 Incident Response Plan
IR-9 Information Spillage Response. Respond to information spills by: a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills; b. Identifying the specific information involved in the system contamination; c. Alerting

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-8 Incident response plan
NIST800-IR-9 Information Spillage Response. Respond to information spills by: Assigning [organization-defined] with responsibility for responding to information spills; Identifying the specific information involved in the system contamination; Alerting [organization-defined] of the information spill using a

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

AEO-12 Crisis Management and Incident Recovery

C5 (Germany) · 1 control

C5-SIM-01 Policy for security incident management

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-16 Security Incident Response Plan and Testing

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

HIPAA Security Rule · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

ISO 27001:2022 · 1 control

5.24 Information security incident management planning and preparation

ISO 27002:2022 · 1 control

5.24 Information security incident management planning and preparation

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-8 Incident Response Plan

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-53 Rev 5 LOW · 1 control

IR-8 Incident Response Plan

NIST SP 800-53 Rev 5 MODERATE · 1 control

IR-8 Incident Response Plan

NIST SP 800-53 Revision 5.1 HIGH · 1 control

IR-8 Incident Response Plan

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

SOC 2 · 1 control

SOC2-CC7.4 Responds to identified security incidents through defined procedures

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.06.05 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

If you hold PCI DSS 4.071.1% covered · 28 gaps If you hold C5 (Germany)68% covered · 31 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gaps If you hold ISO 27001:202262.9% covered · 36 gaps If you hold CIS Controls v853.6% covered · 45 gaps If you hold NIST SP 800-161 Rev 152.6% covered · 46 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

See the released pairs, $299 each Browse the graph free