Azure Security Benchmark ASBv3-IR-2: Preparation - setup incident notification

What else in your programme already covers this

This control maps to 49 controls across 25 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-6 Incident Reporting
IR-6(1) Automated Reporting
SI-4(5) System-Generated Alerts
SI-5 Security Alerts, Advisories, and Directives

FedRAMP Moderate · 4 controls

IR-6 Incident Reporting
IR-6(1) Automated Reporting
SI-4(5) System-Generated Alerts
SI-5 Security Alerts, Advisories, and Directives

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
NIST-CSF-RS.MA-04 Incidents are escalated or elevated as needed

CIS Controls v8 · 3 controls

CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
CIS-17.6 Define Mechanisms for Communicating During Incident Response

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

CCM-BCR-07 Communication
CCM-SEF-07 Security Breach Notification
CCM-SEF-08 Points of Contact Maintenance

ISO 27002:2022 · 3 controls

5.24 Information security incident management planning and preparation
5.25 Assessment and decision on information security events
6.8 Information security event reporting

C5 (Germany) · 2 controls

C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents
C5-SIM-04 Duty of the users to report security incidents to a central body

CMMC 2.0 · 2 controls

IR.L2-3.6.2 Incident Reporting
SI.L2-3.14.3 Security Alerts & Advisories

ISO 27001:2022 · 2 controls

5.24 Information security incident management planning and preparation
6.8 Information security event reporting

NIST SP 800-161 Rev 1 · 2 controls

161R1-IR-6 Incident Reporting
161R1-SR-8 Notification Agreements

NIST SP 800-171 Rev 3 · 2 controls

03.06.02 Incident Monitoring, Reporting, and Response Assistance
03.14.03 Security Alerts, Advisories, and Directives

NIST SP 800-172 · 2 controls

3.6.1e Establish Security Operations Center (SOC)
3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-6 IR-6 Incident Reporting
NIST800-SI-5 SI-5 Security Alerts, Advisories, and Directives

PCI DSS 4.0 · 2 controls

12.10.3 12.10.3 Incident response personnel available 24/7
12.10.5 12.10.5 Plan covers alerts from security monitoring systems

SOC 2 · 2 controls

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

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 234 · 1 control

CPS234-P25 Response Plan Content and Escalation Mechanisms

AWS Well-Architected Security Pillar · 1 control

SEC10-BP01 Identify key personnel and external resources

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

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

CFTC-SS-19 Prompt Notification to the Commission

HIPAA Security Rule · 1 control

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

NIST SP 800-66 Rev 2 · 1 control

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

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