LT-3 Enable logging for security investigation
Enable diagnostic logging for all critical Azure resources with sufficient retention to support investigation and forensics.
4
artefacts
2
held by a system
0
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
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