detection rule
A saved query or pattern that watches incoming events and raises an alert when they match something suspicious.
In more detail
Detection rules can match a single known-bad event (signature), count events over a time window (threshold), link events in order (correlation) or flag departures from normal (anomaly). Each rule is only as good as the log fields it reads. Rules need owners, tests and regular tuning.
Related terms
- alert — An automatic notification sent when a monitored condition, such as a high error rate, stays true.
- Sigma — An open, vendor-neutral format for writing SIEM detection rules in YAML, which tools convert into each SIEM's own query language.
- threshold — A chosen limit that a value is compared against to decide whether something should happen, such as an alert firing.
- correlation rule — A detection rule that links several events, often from different sources, that together suggest an attack.
- anomaly detection — Learning what normal behaviour looks like for a workload or identity and flagging what is new.
Taught in
- SOC Operating Models, Tiers & Key Performance Metrics — Security Operations & Threat Hunting (SOC)
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Event Correlation Rules, Thresholds & Anomaly Pipelines — Security Operations & Threat Hunting (SOC)
- Detection as Code: Authoring & Testing Sigma Rules — Security Operations & Threat Hunting (SOC)
- Cyber Kill Chain vs MITRE ATT&CK Framework — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)