Azure Security Benchmark ASBv3-IR-1: Preparation - update incident response plan and handling process

What else in your programme already covers this

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

AWS Well-Architected Security Pillar · 3 controls

SEC10-BP02 Develop incident management plans
SEC10-BP04 Develop and test security incident response playbooks
SEC10-BP06 Pre-deploy tools

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

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

CCM-BCR-09 Disaster Response Plan
CCM-SEF-01 Security Incident Management Policy and Procedures
CCM-SEF-03 Incident Response Plans

NIST SP 800-161 Rev 1 · 3 controls

161R1-IR-1 Policy and Procedures
161R1-IR-4 Incident Handling
161R1-IR-8 Incident Response Plan

NIST SP 800-53 Rev 5 · 3 controls

NIST800-IR-1 IR-1 Policy and Procedures
NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-8 IR-8 Incident Response Plan

ACSC Essential Eight · 2 controls

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
E8-APP-ML2 Application Control (ML2)

APRA CPS 234 · 2 controls

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

C5 (Germany) · 2 controls

C5-OIS-03 Interfaces and Dependencies
C5-SIM-01 Policy for security incident management

FedRAMP High · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

NIST Cybersecurity Framework 2.0 · 2 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.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

NIST SP 800-171 Rev 3 · 2 controls

03.06.01 Incident Handling
03.06.05 Incident Response Plan

PCI DSS 4.0 · 2 controls

12.10.1 12.10.1 Incident response plan ready for activation
12.10.2 12.10.2 Annual review and testing of the incident response plan

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

CBPR-PR-32 Detection, prevention and response measures

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

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

Australia My Health Records Act 2012 · 1 control

MYHR-ENF-1 Mandatory data breach notification

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

AEO-12 Crisis Management and Incident Recovery

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

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-218 · 1 control

SP800-218-RV.1.3 Vulnerability Disclosure Policy

NIST SP 800-66 Rev 2 · 1 control

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

SOC 2 · 1 control

SOC2-CC7.4 CC7.4 Responding to security incidents

UK Cyber Essentials · 1 control

CE-SC.8 Process for Compromised Passwords

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 Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-IR-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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 NIST SP 800-53 Rev 5 pair alone.

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