LT-5 Centralize security log management and analysis
Aggregate security logs in Microsoft Sentinel or equivalent SIEM with documented detection rules and analyst workflows.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), LT-5. 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
- Sentinel workspace configuration · SIEM / log platform
- Coverage metrics (MITRE mapping) · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Detection rule library · Policy repository / GRC workspace
- Analyst playbooks · Policy repository / GRC workspace
First move
Common gaps auditors find
- Logs ingested but no detections
- Custom rules absent
- No MITRE coverage tracking
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-4 Enable network logging for security investigation · LT-6 Configure log storage retention