Azure Security Benchmark ASBv3-IR-6: Containment, eradication and recovery - automate the incident handling

What else in your programme already covers this

This control maps to 31 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.

FedRAMP High · 4 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes
IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 4 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes
IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
SI-7(7) Integration of Detection and Response

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

ASD37-28 Continuous incident detection and response (Excellent)
ASD37-30 Endpoint detection and response (Very Good)
ASD37-36 System recovery capabilities (Very Good)

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
NIST-CSF-RS.MI-01 Incidents are contained
NIST-CSF-RS.MI-02 Incidents are eradicated

AWS Well-Architected Security Pillar · 2 controls

SEC04-BP04 Initiate remediation for non-compliant resources
SEC10-BP06 Pre-deploy tools

SOC 2 · 2 controls

SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-CC7.5 CC7.5 Recovering from security incidents

APRA CPS 234 · 1 control

CPS234-30 Detection and Response Mechanisms

C5 (Germany) · 1 control

C5-SIM-02 Processing of security incidents

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-SEF-02 Service Management Policy and Procedures

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

ISO 27001:2022 · 1 control

5.26 Response to information security incidents

ISO 27002:2022 · 1 control

5.26 Response to information security incidents

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-4 Incident Handling

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-4 IR-4 Incident Handling

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 1 control

10.7.3 10.7.3 Respond promptly to critical security control failures

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-6 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