Hunt results
Every hunt Scout runs on its own ends with a result: Found, Nothing found or Inconclusive. A hunt never just stops. The result says what Scout concluded and what happens next: respond and propose a detection, record what was searched, or hand the hunt to a person.
The result is Scout's. It sits next to the two verdicts every hunt has, and doesn't replace either: the checks' verdict, worked out by rule from what the hunt ran, and your verdict, the outcome of record you set when you conclude. See Conclude a hunt.
The three results
| Result | When Scout may record it | What happens next |
|---|---|---|
| Found | The checks' verdict is Affected, or it is Can't confirm and the hunt has at least one finding. Scout can't record Found on its own say-so. | Scout responds (collects, then contains where a policy allows), re-hunts to confirm, and proposes a detection. |
| Nothing found | The checks' verdict is Not affected or No evidence in what we can see, and nothing in the hunt counts as a finding. | Scout records what was searched, so "nothing" is a statement you can check. |
| Inconclusive | Scout couldn't settle it, for example because a source failed or the evidence is weak. Scout can always record this. | A message in Needs you asks a person to look at the hunt. |
On the hunt, the result is on the details pane's Brief, under Result, with the re-hunt and, for Nothing found, what was searched. A hunt Scout started also says where it came from, for example Started by Scout from new intel: and the idea's title, and lists the actions Scout ran under a policy, with Undo. The result is also in Scout activity and the morning summary.
Nothing found: what was searched
A Nothing found result carries a summary of what the hunt searched: how many hosts, over how many days, which queries ran and which sources answered. Huntbase works it out from the queries that actually ran; Scout doesn't write it. It reads, for example, Searched 12 hosts over 7 days, 9 queries.
If a source didn't answer, or the period was shorter than asked, the checks' verdict says so (No evidence in what we can see), so a gap is never presented as proof of absence.
The confirming re-hunt
After Scout contains a threat, it hunts again to check the threat is gone. Once the actions have run and been checked, it re-runs each query that hit as a new cell in the notebook, scoped to the hosts and accounts involved.
| Re-hunt | Meaning |
|---|---|
| Re-hunt running | Waiting for the actions to finish and be checked, or running. |
| Re-hunt clean | The queries that hit now find nothing on the affected hosts and accounts. |
| Still present after re-hunt | They still find the activity. The hunt and Scout activity show it, and Scout takes it into account before it records a result. |
| Re-hunt skipped | None of the queries that hit could run again. |
You can also ask Scout to re-hunt in the hunt's chat.
Detection proposed
When a hunt is Found, Scout proposes turning what it found into a standing detection, so the same activity is caught next time without a hunt. The proposal goes through the same path as any other watcher proposal, and the watcher starts in Shadow: its matches go to the daily digest and it notifies nobody until a person turns it On. See Watchers.
Scout activity records Detection proposed with a link to the watcher.
Findings Scout makes
When a hunt has found something, Scout can record a finding with Scout as its author. It cites the rows in the hunt's evidence it rests on, and Scout can only record one when the checks' verdict supports it. A finding Scout made reads as Scout's, not yours, so it's clear who said what.
Your verdict still decides
The result is how Scout ended its work, not the outcome of record. When you open an autonomous hunt, read the result and the evidence, then conclude it with your verdict. Scout's draft is offered as Start from Scout's draft.
Next steps
- Scout activity and the morning summary — results across all of Scout's hunts
- Conclude a hunt — the checks' verdict and yours
- Autonomous hunting — where these hunts come from