Hunt Hypothesis
Also called Hunt Loop.
A testable assumption about adversary activity that guides a hunt.
What it is
A hunt hypothesis is a specific, testable assumption about how an adversary might be operating in the environment, used to focus a threat hunt and define what evidence to look for. The hunt loop iterates: form a hypothesis, gather data, test it, and refine.
Why it matters
A clear hypothesis turns hunting from aimless data browsing into a directed, repeatable search. Confirmed or refuted, the result often becomes a new detection or a coverage gap to close.
In practice
Hypothesizing that an attacker abused a scheduling mechanism for persistence, then hunting every scheduled task created in the last month.
What to look for
- A clear statement tied to a technique, data source and expected result.
- Data available to test it before the hunt starts.
- A plan for turning findings into detections.
Common mistake
Hunting without a question. Browsing data feels busy but rarely finds anything.
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.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Crown Jewel Analysis: Identifying an org's most critical assets to focus defense on them.
- Anomaly Detection: Flagging activity that deviates from an established normal baseline.
- Detection Coverage: How much of relevant adversary behavior your detections actually catch.