LT-1 Enable threat detection capabilities
Monitor all known resource types for expected threats and anomalies, and configure alert filtering and analytics rules so high quality alerts are extracted from log data and false positives are reduced.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), LT-1. 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
- Analytics and filtering rules in use · Cloud console / configuration management
- False positive rate and alert volume trend · SIEM / log platform
periodic reviewEvidence produced at each review
- Review records for detection rule tuning · Document repository
governing documentDocuments that govern the control
- Detection coverage matrix across resource types · Policy repository / GRC workspace
First move
Common gaps auditors find
- detection enabled on compute only
- every rule left at default so analysts drown in noise
- no measurement of alert quality so tuning never happens
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 sheetIR-7 Post-incident activity - conduct lesson learned and retain evidence · LT-2 Enable threat detection for identity and access management