NIST SP 800-172 3.6.2e: Establish and Maintain a Cyber Incident Response Team

What else in your programme already covers this

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

NIST Cybersecurity Framework 2.0 · 5 controls

NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
NIST-CSF-RS.MA-04 Incidents are escalated or elevated as needed
NIST-CSF-RS.MI-01 Incidents are contained

Azure Security Benchmark · 3 controls

ASBv3-IR-1 Preparation - update incident response plan and handling process
ASBv3-IR-2 Preparation - setup incident notification
ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

CIS Controls v8 · 3 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

HIPAA Security Rule · 3 controls

164.308(a)(1)(i) Security Management Process (Standard)
164.308(a)(6)(i) Security Incident Procedures (Standard)
164.308(a)(6)(ii) Response and Reporting (Required)

NIST SP 800-161 Rev 1 · 3 controls

161R1-IR-4 Incident Handling
161R1-IR-7 Incident Response Assistance
161R1-IR-8 Incident Response Plan

NIST SP 800-66 Rev 2 · 3 controls

164.308(a)(1)(i) Security Management Process (Standard)
164.308(a)(6)(i) Security Incident Procedures (Standard)
164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 3 controls

12.10.1 12.10.1 Incident response plan ready for activation
12.10.3 12.10.3 Incident response personnel available 24/7
12.10.4 12.10.4 Periodic training for incident response personnel

C5 (Germany) · 2 controls

C5-SIM-01 Policy for security incident management
C5-SIM-02 Processing of security incidents

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

CCM-SEF-02 Service Management Policy and Procedures
CCM-SEF-03 Incident Response Plans

FedRAMP High · 2 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes

ISO 27001:2022 · 2 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents

ISO 27002:2022 · 2 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents

NIST SP 800-171 Rev 3 · 2 controls

03.06.01 Incident Handling
03.06.05 Incident Response Plan

SOC 2 · 2 controls

SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-4 IR-4 Incident Handling

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-172 have you already done?

NIST SP 800-172 3.6.2e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

If you hold NIST SP 800-53 Rev 568.6% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.165.7% covered · 12 gaps If you hold NIST SP 800-161 Rev 162.9% covered · 13 gaps If you hold FedRAMP Moderate60% covered · 14 gaps If you hold NIST Cybersecurity Framework 2.048.6% covered · 18 gaps If you hold C5 (Germany)45.7% covered · 19 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. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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