log replay
Running recorded logs from a past incident or test set through a detection rule to show exactly what it would have caught.
In more detail
Replay proves a new rule would have fired during the real incident and still stays quiet on normal logs. It also protects old true positives when a rule is tuned.
Related terms
- corrective action — A change agreed in a post-incident review to fix a cause, with an owner, a due date and a way to prove it worked.
- detection as code — Treating detection rules like software: stored in version control, reviewed, and tested automatically on every change.
- tuning — Adjusting a detection rule so it raises fewer false alerts without missing real attacks.
Taught in
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Recovery & System Validation Testing — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)