LT-3 Enable logging for security investigation
Enable diagnostic logging for all critical Azure resources with sufficient retention to support investigation and forensics.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), LT-3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Log Analytics workspace configuration · SIEM / log platform
- Activity log archive · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Diagnostic settings inventory · Policy repository / GRC workspace
- Retention policy · Policy repository / GRC workspace
First move
Common gaps auditors find
- Diagnostic logs disabled by default
- Retention under regulatory minimums
- Logs not sent to immutable storage
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetLT-2 Enable threat detection for identity and access management · LT-4 Enable network logging for security investigation