Azure Security Benchmark
Logging and Threat Detection

Azure Security Benchmark LT-3: Enable logging for security investigation

Enable diagnostic logging for all critical Azure resources with sufficient retention to support investigation and forensics.

What else in your programme already covers this

This control maps to 79 controls across 29 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 · 7 controls

  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions

FedRAMP Moderate · 7 controls

  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions
  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions
  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records

CIS Controls v8 · 5 controls

PCI DSS 4.0 · 5 controls

  • 10.2.1 Audit logs enabled on system components
  • 10.2.1.1 Log all user access to CHD
  • 10.2.1.2 Log all admin actions
  • 10.2.2 Audit log content
  • 5.3.4 Audit logs for anti-malware enabled

NIST SP 800-171 Rev 3 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records

ACSC Essential Eight · 3 controls

CMMC 2.0 · 3 controls

  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

C5 (Germany) · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • CBPR-PR-30 Specific proportional safeguards in place

APPI · 1 control

  • ASD37-33 Capture network traffic (Limited)
  • SEC04-BP01 Configure service and application logging
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

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