Azure Security Benchmark ASBv3-IR-5: Detection and analysis - prioritize incidents

What else in your programme already covers this

This control maps to 32 controls across 21 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 SP 800-53 Rev 5 · 4 controls

NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-8 IR-8 Incident Response Plan
NIST800-RA-2 RA-2 Security Categorization
NIST800-RA-9 RA-9 Criticality Analysis

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
NIST-CSF-RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed
NIST-CSF-RS.MA-03 Incidents are categorized and prioritized

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

CCM-DSP-04 Data Classification
CCM-SEF-06 Event Triage Processes

FedRAMP High · 2 controls

IR-4 Incident Handling
RA-9 Criticality Analysis (RA-9)

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
RA-9 Criticality Analysis (RA-9)

HIPAA Security Rule · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis (Addressable)

NIST SP 800-171 Rev 3 · 2 controls

03.04.11 Information Location
03.06.01 Incident Handling

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis (Addressable)

APRA CPS 234 · 1 control

CPS234-20 Information Asset Classification

AWS Well-Architected Security Pillar · 1 control

SEC04-BP03 Correlate and enrich security alerts

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

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

C5 (Germany) · 1 control

C5-SIM-02 Processing of security incidents

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

CFTC-SS-16 Security Incident Response Plan and Testing

CIS Controls v8 · 1 control

CIS-17.9 Establish and Maintain Security Incident Thresholds

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

ISO 27001:2022 · 1 control

5.25 Assessment and decision on information security events

ISO 27002:2022 · 1 control

5.25 Assessment and decision on information security events

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-5 Incident Monitoring

NIST SP 800-172 · 1 control

3.6.1e Establish Security Operations Center (SOC)

SOC 2 · 1 control

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

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