Azure Security Benchmark ASBv3-GS-7: Define and implement logging, threat detection and incident response strategy

What else in your programme already covers this

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

APRA CPS 234 · 3 controls

CPS234-15 Information Security Capability
CPS234-30 Detection and Response Mechanisms
CPS234-P24 Information Security Response Plans

C5 (Germany) · 2 controls

C5-OPS-10 Logging and Monitoring - Concept
C5-SIM-01 Policy for security incident management

CIS Controls v8 · 2 controls

CIS-17.4 Establish and Maintain an Incident Response Process
CIS-8.1 Establish and Maintain an Audit Log Management Process

CMMC 2.0 · 2 controls

AU.L2-3.3.1 System Auditing
IR.L2-3.6.1 Incident Handling

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

CCM-LOG-01 Logging and Monitoring Policy and Procedures
CCM-SEF-01 Security Incident Management Policy and Procedures

FedRAMP High · 2 controls

AU-1 Policy and Procedures
IR-1 Policy and Procedures

FedRAMP Moderate · 2 controls

AU-1 Policy and Procedures
IR-1 Policy and Procedures

ISO 27001:2022 · 2 controls

5.24 Information security incident management planning and preparation
8.15 Logging

ISO 27002:2022 · 2 controls

5.24 Information security incident management planning and preparation
8.15 Logging

NIST SP 800-171 Rev 3 · 2 controls

03.03.01 Event Logging
03.06.05 Incident Response Plan

NIST SP 800-172 · 2 controls

3.11.1e Threat-Aware Risk Assessment
3.6.1e Establish Security Operations Center (SOC)

NIST SP 800-53 Rev 5 · 2 controls

NIST800-AU-1 AU-1 Policy and Procedures
NIST800-IR-1 IR-1 Policy and Procedures

PCI DSS 4.0 · 2 controls

10.1.1 10.1.1 Requirement 10 policies and procedures maintained and in use
12.10.1 12.10.1 Incident response plan ready for activation

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

ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components

AWS Well-Architected Security Pillar · 1 control

SEC04-BP02 Capture logs, findings, and metrics in standardized locations

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-SEC-1 Written security and access policy

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

CFTC-SS-16 Security Incident Response Plan and Testing

HIPAA Security Rule · 1 control

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

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-8 Incident Response Plan

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

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