GS-7 Define and implement logging, threat detection and incident response strategy
Define and implement a logging, threat detection and incident response strategy so threats are detected and remediated rapidly and compliance requirements for logging are met.
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
- Combined logging, detection and response strategy · SIEM / log platform
- Log source and retention requirements derived from it · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Detection coverage objectives and how they are measured · Policy repository / GRC workspace
- Incident response responsibilities defined in the strategy · 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
- logging strategy written for compliance only with no detection objective
- detection and response owned separately with no shared strategy
- no measurable coverage objective so gaps are invisible
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 sheetGS-6 Define and implement identity and privileged access strategy · GS-8 Define and implement backup and recovery strategy