Azure Security Benchmark
Incident Response

Azure Security Benchmark ASBv3-IR-4: Detection and analysis - investigate an incident

Ensure the security operations team can query and use diverse data sources when investigating potential incidents, collecting logs broadly enough to track activity across the attack chain without blind spots.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-6(3) Correlate Audit Record Repositories
  • AU-7 Audit Record Reduction and Report Generation
  • IR-4 Incident Handling
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))

FedRAMP Moderate · 5 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-6(3) Correlate Audit Record Repositories
  • AU-7 Audit Record Reduction and Report Generation
  • IR-4 Incident Handling
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))

CMMC 2.0 · 4 controls

NIST SP 800-171 Rev 3 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

CIS Controls v8 · 3 controls

  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.AE-03 Information is correlated from multiple sources
  • NIST-CSF-RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident

NIST SP 800-172 · 3 controls

  • 3.11.2e Threat Hunting
  • 3.11.3e Advanced Automation and Analytics Capabilities
  • 3.6.1e Establish Security Operations Center (SOC)
  • ASD37-31 Hunt to discover incidents (Very Good)
  • ASD37-33 Capture network traffic (Limited)

ISO 27001:2022 · 2 controls

  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence

ISO 27002:2022 · 2 controls

  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence

SOC 2 · 2 controls

  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

APRA CPS 234 · 1 control

  • CPS234-30 Detection and Response Mechanisms

C5 (Germany) · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

PCI DSS 4.0 · 1 control

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed

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.

Other controls in Incident Response

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-IR-4 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.

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.

Query this from an agent

The graph holds this control, the 55 it maps to, and the evidence behind each claim, over MCP and REST.