nano SIEM
Hunts

Hunts

Supported in:Self-hosted

Run scheduled threat hunts that test a hypothesis against your data, rule out benign explanations, and send analysts only the findings that hold up.

Use hunts to look for attacks that your detection rules don't catch. A hunt tests a hypothesis against your data on a schedule. Two AI agents then sort what it finds, so your analysts see only the findings that hold up.

The Hunts page, with the funnel and the hunt library

How a hunt differs from a detection rule

A detection rule asks whether a known pattern happened. A hunt asks whether a hypothesis is true anywhere in your data, and it looks at the benign explanations before it asks for a person.

Detection ruleHunt
QuestionDid this known pattern happen?Is this hypothesis true anywhere in my data?
LogicOne query with a match conditionA hypothesis, several queries, and AI review
OutputAn alert for every matchFindings, each labeled lead, benign, duplicate, or escalated
Benign activityYou add exclusionsThe hunt tests each candidate against a benign explanation and remembers what it learns
What reaches an analystEvery alertOnly escalated findings
CostQuery costQuery cost plus AI tokens on every run

Hunts and detection rules work together. A hunt reads the detections that already fired, including quiet ones from rules in Live mode. If a detection already covers what a hunt finds, the hunt labels its finding a duplicate. If a hunt keeps finding the same real pattern, you can turn it into a detection rule.

How a hunt runs

Each run of a hunt is called a sweep. A sweep runs these steps in order:

  1. Schedule. nano picks the hunts that are due, highest priority first.
  2. Discover sources. nano checks which log sources have data in the time window. If none of the hunt's sources have data, the sweep stops here at no AI cost.
  3. Run queries. nano runs the hunt's queries and flags unusual rows. This step doesn't use AI.
  4. Recheck known actors. If the hunt tracks known attackers, a small AI model checks whether their warning signs appeared.
  5. Investigator. An AI agent reads the results and your team's notes, runs more queries if it needs to, and labels each candidate. The investigator can't escalate.
  6. Reviewer. A second AI agent checks each lead on its own, from the evidence. The reviewer is the only step that can escalate a finding.
  7. Analyst. A person acknowledges the escalation, opens a case, or dismisses the finding. Later runs learn from that decision.

Each layer decides one thing:

LayerDecided byWhat it decides
Query rulesnanoQueries are read-only and limited. The investigator can't escalate.
RecheckSmall AI modelWhether a known attacker's warning signs appeared
InvestigatorAI agentWhether each candidate is a lead, benign, or a duplicate
ReviewerAI agentWhether each lead is escalated or benign
AnalystPersonThe final decision, which later runs learn from

Find hunts in nano

Click Hunts in the left navigation. The section has these pages:

PageUse it to
HuntsSee the funnel and your hunts. Open a hunt to see its playbook, escalation settings, and runs.
FindingsTriage findings by label, state, and hunt.
EscalationsAcknowledge findings the reviewer escalated.
CampaignsTrack known attackers and their warning signs.
Rule ideasReview detection rules suggested by repeated findings.
MemoryReview what hunts have learned about your environment.
RulingsSee your analysts' decisions on findings.
ProfileSee which telemetry you have and which techniques it can cover.
RunnersCheck the runners that run your hunts.

Read the funnel

The funnel on the Hunts page, and on each hunt, counts runs, then findings by label, then escalations, over 7 or 30 days. A healthy hunt files many findings and escalates very few. In a production deployment of the same design at about 23 TB per day, one week of 1,248 runs escalated 86 findings. That is well under 1% of the findings filed.

The funnel for one hunt

What's next

On this page