Tuning
Adjusting detection logic to cut noise without losing real catches.
What it is
Tuning is the iterative adjustment of a detection's logic, thresholds, or exclusions to reduce false positives while preserving its ability to catch real threats. It is the ongoing maintenance that keeps detections useful.
Why it matters
Untuned detections either drown analysts in noise or get switched off entirely, so disciplined tuning is what keeps the alert stream trustworthy and combats alert fatigue.
In practice
Refining a noisy rule to exclude a known administrative tool's legitimate usage while still alerting on its abuse.
What to look for
- Exceptions scoped to one host, user or path rather than broad allows.
- A record of why each exception exists.
- Alert volume and true positive rate tracked before and after.
Common mistake
Excluding a whole process name. Attackers can use the same name, so scope by path, signer and parent.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Sigma Open source
A vendor neutral rule format that converts into queries for most SIEMs. Our notes.
-
YARA Open source
Matches byte and string patterns in files or memory, the standard for malware rules. Our notes.
-
Suricata Open source
Runs network rules against live traffic or captures and logs every match. Our notes.
-
Splunk Enterprise Security Commercial
Where many teams run, tune and schedule detection searches in production.
Read next
- False Positive: An alert that flags benign activity as malicious.
- Alert Fatigue: Desensitization to alerts caused by overwhelming volume and noise.
- Precision and Recall: Metrics for how accurate and how complete a detection is.