Operations → Security Operations
Threat Hunting
A proactive search for hidden adversary activity that automated alerts and known signatures may have missed.
Motivation
Threat Hunting helps security teams reduce operational risk by making detection, investigation, and response more systematic.
Mental model
Threat hunting starts with a hypothesis and searches across evidence for weak signals that may not have triggered an alert.
Where it fits
Threat Hunting belongs to the Operations track, inside Security Operations. It complements preventive controls by helping teams observe and act on what happens in running environments.
Practical considerations
- Define ownership, escalation paths, and expected response times.
- Prefer high-quality, contextual signals over large volumes of unactionable alerts.
- Test procedures and automation before relying on them during an incident.
- Review outcomes and tune detections, tooling, and playbooks continuously.
Common mistakes
- Treating tooling as a substitute for clear processes and accountable owners.
- Collecting telemetry without retention, access, and investigation plans.
- Measuring alert volume instead of detection quality and response effectiveness.
Related concepts
Use the metadata panel or return to the graph to explore prerequisites and neighboring security operations concepts.