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.
4
artefacts
1
held by a system
1
at each review
moderate
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
- 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
- Analytics and filtering rules in use · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
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