detection as code
Treating detection rules like software: stored in version control, reviewed, and tested automatically on every change.
In more detail
Each rule lives in a Git repository beside test events that must match (true positives) and must not (true negatives). A pipeline runs the tests before a rule is deployed, so a tuning change that breaks a detection is caught. Every missed attack or false positive becomes a new named test case.
Related terms
- Sigma — An open, vendor-neutral format for writing SIEM detection rules in YAML, which tools convert into each SIEM's own query language.
- detection engineering — The job of designing, writing, testing and maintaining the rules that turn logs into alerts.
- true negative — Harmless activity that a rule correctly left alone.
- Git — A free, open-source distributed version control system that records the history of a project as a chain of snapshots.
Taught in
- Detection as Code: Authoring & Testing Sigma Rules — Security Operations & Threat Hunting (SOC)