Azure Security Benchmark
Logging and Threat Detection

Azure Security Benchmark ASBv3-LT-1: Enable threat detection capabilities

Monitor all known resource types for expected threats and anomalies, and configure alert filtering and analytics rules so high quality alerts are extracted from log data and false positives are reduced.

What else in your programme already covers this

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

PCI DSS 4.0 · 5 controls

  • 10.4.1 Daily log review for critical systems
  • 10.4.1.1 Automated mechanisms for log review
  • 10.4.2 Periodic review of other system component logs
  • 11.5.1 IDS/IPS in place
  • 11.5.2 Change detection mechanism (FIM)
  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-29 Host-based IDS/IPS (Very Good)
  • ASD37-30 Endpoint detection and response (Very Good)
  • ASD37-32 Network-based IDS/IPS (Limited)

FedRAMP High · 4 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-7(1) Automatic Processing
  • SI-4 System Monitoring
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis

FedRAMP Moderate · 4 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-7(1) Automatic Processing
  • SI-4 System Monitoring
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis

NIST SP 800-53 Rev 5 · 4 controls

  • SEC01-BP04 Stay up to date with security threats and recommendations
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations
  • SEC04-BP03 Correlate and enrich security alerts

CIS Controls v8 · 3 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-8.11 Conduct Audit Log Reviews

CMMC 2.0 · 3 controls

NIST SP 800-172 · 3 controls

  • 3.11.3e Advanced Automation and Analytics Capabilities
  • 3.14.2e Monitor Organizational Systems with Specialized Capabilities
  • 3.14.6e Use Threat Indicator Information for Detection
  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-7(1) Automatic Processing
  • SI-4 System Monitoring
  • AU-6 Audit Record Review, Analysis, and Reporting
  • AU-7(1) Automatic Processing
  • SI-4 System Monitoring

C5 (Germany) · 2 controls

ISO 27002:2022 · 2 controls

  • 5.7 Threat intelligence
  • 8.16 Monitoring activities
  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

NIST SP 800-171 Rev 3 · 2 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • SI-4 System Monitoring
  • CBPR-PR-32 Detection, prevention and response measures

APRA CPS 234 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.16 Monitoring activities

SOC 2 · 1 control

  • SOC2-CC7.2 Monitors system components for anomalies indicating malicious acts

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 Logging and Threat Detection

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

Azure Security Benchmark ASBv3-LT-1 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 61 it maps to, and the evidence behind each claim, over MCP and REST.