Azure Security Benchmark
Logging and Threat Detection

Azure Security Benchmark ASBv3-LT-6: Configure log storage retention

Plan and configure log retention at each logging service according to compliance, regulatory and business requirements so logs are archived for the required period.

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

What else in your programme already covers this

This control maps to 50 controls across 22 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 · 4 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • AU-9 Protection of Audit Information
  • SI-12 Information Management and Retention

FedRAMP Moderate · 4 controls

  • AU-11 Audit Record Retention
  • AU-4 Audit Log Storage Capacity
  • AU-9 Protection of Audit Information
  • SI-12 Information Management and Retention

ISO 27002:2022 · 4 controls

  • 5.28 Collection of evidence
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.33 Protection of records
  • 8.15 Logging

C5 (Germany) · 3 controls

  • C5-COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements
  • C5-OPS-11 Logging and Monitoring - Metadata Management Concept
  • C5-OPS-14 Logging and Monitoring - Storage of the Logging Data

CIS Controls v8 · 3 controls

ISO 27001:2022 · 3 controls

  • 5.28 Collection of evidence
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 8.15 Logging

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations
  • SEC07-BP04 Define scalable data lifecycle management

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

PCI DSS 4.0 · 2 controls

  • 10.3.2 10.3.2 Audit log files protected from modification
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online
  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • ASD37-33 Capture network traffic (Limited)
  • CFTC-SS-20 Production of System Safeguards Books and Records

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

SOC 2 · 1 control

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information

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