Azure Security Benchmark
Incident Response

Azure Security Benchmark ASBv3-IR-3: Detection and analysis - create incidents based on high-quality alerts

Establish a process to create high quality alerts and measure their quality, so analysts prioritise real incidents rather than spending time on false positives.

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

What else in your programme already covers this

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

C5 (Germany) · 4 controls

  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-OPS-16 Logging and Monitoring - Configuration
  • C5-OPS-20 Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures
  • C5-SIM-05 Evaluation and learning process
  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
  • NIST-CSF-RS.MA-02 Incident reports are triaged and validated

NIST SP 800-53 Rev 5 · 3 controls

  • NIST800-AU-6 AU-6 Audit Record Review, Analysis, and Reporting
  • NIST800-IR-5 IR-5 Incident Monitoring
  • NIST800-SI-4 SI-4 System Monitoring

PCI DSS 4.0 · 3 controls

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed
  • 10.7.2 10.7.2 Detect and alert on critical security control failures
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems

CIS Controls v8 · 2 controls

  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • IR-5 Incident Monitoring
  • SI-4(5) System-Generated Alerts

FedRAMP Moderate · 2 controls

  • IR-5 Incident Monitoring
  • SI-4(5) System-Generated Alerts

ISO 27002:2022 · 2 controls

  • 5.25 Assessment and decision on information security events
  • 8.16 Monitoring activities

NIST SP 800-171 Rev 3 · 2 controls

  • 03.03.05 Audit Record Review, Analysis, and Reporting
  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-172 · 2 controls

  • 3.11.3e Advanced Automation and Analytics Capabilities
  • 3.6.1e Establish Security Operations Center (SOC)
  • CBPR-PR-33 Testing the effectiveness of safeguards
  • CPS230-27 Identification and Escalation of Incidents and Near Misses

APRA CPS 234 · 1 control

  • CPS234-30 Detection and Response Mechanisms
  • ASD37-28 Continuous incident detection and response (Excellent)
  • CFTC-SS-16 Security Incident Response Plan and Testing

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.25 Assessment and decision on information security events

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.

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-3 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 42 it maps to, and the evidence behind each claim, over MCP and REST.