precision
The share of a rule's alerts that were true positives: true positives divided by all alerts the rule raised.
In more detail
A rule that fires 100 times with 2 true positives has 2 % precision and is mostly noise. Precision per rule, computed from recorded dispositions, shows which rules to tune first. It says nothing about attacks the rule missed.
Related terms
- disposition — The recorded outcome of an alert after triage, such as true positive, benign true positive or false positive.
- tuning — Adjusting a detection rule so it raises fewer false alerts without missing real attacks.
- false positive — A check result that claims something is true when it is not, such as a test passing on broken code or a tool flagging correct code.
Taught in
- Alert Triage, False Positive Reduction & Fatigue Mitigation — Security Operations & Threat Hunting (SOC)
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Log Parsing, Schema Normalization (OCSF/ECS) & Extraction — Security Operations & Threat Hunting (SOC)
- YARA Rule Authoring & File Signature Matching — Security Operations & Threat Hunting (SOC)
- Cyber Kill Chain vs MITRE ATT&CK Framework — Security Operations & Threat Hunting (SOC)
- Disk Forensics: MFT, UsnJrnl & Prefetch — Security Operations & Threat Hunting (SOC)