Hunts
A hunt keeps an investigation together: the question you are testing, the steps you and Scout run, the entities and evidence they turn up, and the verdict and report you hand off at the end. A hunt is one document with three views: Notebook, Flow and Evidence. It also has a Report and its own chats with Scout.
A hunt opens on its Notebook: a Plan block at the top, then the steps as an ordered list of cells you read top to bottom, each with what it found. The Flow view draws the same cells as a graph, and Evidence shows what they turned up as a table, a timeline or a graph. Nothing in a hunt is linear by design: you can plan, run, review, plan again, and conclude at any point.
Work through a hunt
These pages follow a hunt from start to finish:
- Start a hunt: pick a starting point, write the question, choose how much Scout does, and add work from elsewhere.
- Work in the notebook: the Plan block, adding, running and editing cells, and reviewing what Scout changed.
- Set a hunt's time window: choose the stretch of time every query step searches, and re-run a step over another window.
- Endpoint and telemetry cells: bring one endpoint, or a view of your shipped telemetry, into the hunt as evidence.
- Approvals and Needs you: approve the plan and the steps Scout proposes, and clear what the hunt is waiting on.
- Hunt views and the details pane: the Flow graph, the Evidence view, and the Flow minimap, Outline, Brief and Provenance beside the notebook.
- Conclude a hunt: record the verdict, settle open issues, and write the report and the customer copy.
Parts of a hunt
| Term | What it is |
|---|---|
| Plan | The first cell: the hunt's question (its hypothesis), where it came from, and the list of steps. Scout plans from it. |
| Cell | One step in the notebook: a query, a note, a task, a checkpoint, an endpoint or telemetry cell. The Flow view calls the same step a node. |
| Section | A heading that groups the cells beneath it. |
| Checkpoint | A step that stops the plan until a person decides. |
| Needs you | The list of what the hunt is waiting on: failures, approvals, checkpoints and the verdict. |
| Checks | The record of every search the hunt and its Scout chats ran, what came back and what wasn't searched. The checks give their own verdict: Affected, Not affected, No evidence in what we can see, Can't tell yet or Can't confirm. See The checks box. |
| Verdict | The outcome you record when you conclude: Confirmed, Benign, False positive, Clear or Inconclusive. It leads over the checks' verdict, which stays shown beneath it. |
| Report | The write-up Scout drafts from the hunt, in its own tab, and a customer report you can save as a PDF. |
A hunt's lifecycle
| Status | What it means |
|---|---|
| Draft | Every new hunt starts here. Until it has any steps, the owner can remove it with ⋯ › Delete draft…. |
| Active | The hunt is being worked: cells run, Scout plans, approvals wait under Needs you. A hunt you recorded as Confirmed but kept open reads Confirmed · open, in the verdict's colour. |
| Concluded | A verdict has been recorded and the hunt is closed and read-only. The chip names the verdict, for example Concluded · Confirmed, and adds any open issues you acknowledged (Concluded · Confirmed · 3 open issues). Anyone who can edit the hunt can reopen it. See Conclude a hunt. |
| Archived | Shelved. Restore to active brings it back. |
The status chip in the header is read-only. You conclude a hunt with Conclude, and reopen, archive or restore it from the header's ⋯ menu.
The hunt header
The header carries, in order:
- the title (click to edit), the status chip, the severity, the Scout mode chip (Scout: Guide, Scout: Collaborator or Scout: Operator), and the organization the hunt investigates as plain text, for example in Example Corp;
- the view switch: Notebook · Flow · Evidence (⌘\ or Ctrl+\ cycles through them);
- Run ▾, Conclude (Edit conclusion once the hunt is concluded), the ⋯ menu (More actions for hunt), and the Scout icon, which opens or hides the hunt's Scout panel (Ask Scout / Hide Scout, ⌘J or Ctrl+J).
When the hunt has open issues, the header shows N open issues. Click it to open Conclude at its Open issues section. See Conclude a hunt.
When the header is short of space, chips that don't fit fold into a +N button, and you can still see and change them there.
Under the header, one quiet line says where the hunt came from, for example From report: with the report's title, Started from a detection, Watcher: or Playbook:, each a link, followed by progress such as 8 cells · 3 done · 1 failed · 12 entities.
Run ▾
Run ▾ is the hunt's one run control. Its menu offers:
| Item | What it runs |
|---|---|
| Run cell [n] | The cell you have focused in the notebook, or the node selected in the Flow view. It runs a cell that hasn't run, and re-runs one that has. |
| Run from [n] | That cell and every cell below it, top to bottom, as in a notebook. The item lists the cells it will run (Runs [13], [14], top to bottom). It leaves alone cells waiting for your approval, steps you declined and checkpoints you already answered, and says where it will pause for approval. |
| Run all (n) | Every cell that hasn't run yet. When everything has run, it reads Re-run all (n). When no cell has a query, it is disabled: No cells have a query yet. If some steps will stop for approval, the item says how many, for example 2 need approval. |
| Run stale (n) | Cells whose inputs changed since they ran, and what depends on them. |
When something is stale the button reads, for example, Run · 2 stale, and Run stale leads the menu. A disabled item always says why, for example Select a cell first. While a run is going, the button becomes Cancel with its progress and the step it's on, for example Cancel (3/8 · Failed logins by host), or Cancel paused run while it waits on you. A step that can't start, such as a query with a parameter that has no value, waits for you, and the run carries on with the other steps.
The run control in each cell's gutter, and Run in the Flow side panel, are the per-cell shortcuts.
The ⋯ menu
| Item | What it does |
|---|---|
| Share… | Who owns the hunt, who is on it and who can see it. See Collaborators and visibility. |
| Save to Library ▸ | Save as playbook… and Relaunch when a watcher fires…. See Save, export and reuse a hunt. |
| Export ▸ | Customer report… (once a verdict is recorded), Hunt as YAML… and Results spreadsheet… (the tracker spreadsheet, .xlsx). |
| Import cells from YAML… | Adds cells from a YAML export to this hunt. |
| Pause Scout / Resume Scout | Stops Scout changing cells or recording verdicts in this hunt until you resume. See Pause Scout. |
| Reopen hunt | On a concluded hunt. |
| Archive hunt / Restore to active | Shelves an active hunt, or brings an archived one back. |
| Delete draft… | Last and in red, on a draft, owner only. |
An item that can't be used yet stays in the menu, disabled, and says why, for example Nothing to export yet — add a cell first. The exports stay available on a concluded hunt.
Pause Scout
When you want Scout to stop changing the hunt while you look, choose ⋯ › Pause Scout, or click Pause Scout above the input in the hunt's Scout panel. The notebook's banner then reads Scout is paused — it won't change cells or record verdicts until you resume, with Resume. You can still chat with Scout. If you ask it to change something while it's paused, a short note under its answer says it didn't, and how to resume. Stopping Scout in the middle of an answer pauses it the same way until you next write to it.
Pause and resume are offered to the owner and anyone with Can edit, on an active hunt. A concluded or archived hunt is always idle: Scout never shows as working on it.
The answer box
Once a hunt has a verdict, an answer box at the top of the hunt says it before anything else:
- With no analyst verdict yet, it shows the checks' verdict line, for example Can't tell yet, with No analyst verdict yet.
- Once someone has concluded, it shows Analyst: and their verdict, their reason, and who recorded it and when. The checks' verdict follows in muted text, starting From the checks:.
Open it to see the checks box (what was checked, what wasn't, and the findings), open issues and follow-ups. Customer report (or Shareable report) opens the report you can send outside the team. See Customer or shareable report.
The Brief beside the notebook shows the same verdict and checks under Scout's summary of the hunt.
Collaborators and visibility
Every hunt has an Owner and a Scope. On an organization's hunt, the person shown as the owner is the person who created it. The owner and anyone with Can edit can add and run cells, edit the title, description, question and scope, and conclude, reopen or archive the hunt. Only the owner can delete a draft, add or remove people, and change who can see it. Someone with Can view reads the hunt but cannot change it.
Open ⋯ › Share… to see who owns the hunt, who created it if that was someone else (Scout, say), everyone on it with their role, and who can see it. The owner adds or removes people there and picks Only people on this hunt or Everyone in the organisation. Hunts are private to the people on them by default. Where the new sharing screens are on, the owner continues in the Share dialog: View is Can view, Edit is Can edit, and Restricted to the people below is Only people on this hunt. Hunts are shared with people, not teams. Sample hunts can't be shared.
Read-only hunts
When you cannot edit, the notebook says why in place of Add cell. A concluded hunt says This hunt is closed. Its cells are read-only. and offers Reopen hunt to its owner and anyone with Can edit. It asks for nothing: checkpoints and proposed steps can't be approved, and steps can't be run again. Someone else's hunt is read-only unless you are a contributor on it; the strip names the owner.
The hunts that come with sample data are owned by Example Corp (sample) and are read-only for everyone.
A hunt opens in its own scope
A hunt belongs to one organization, or to you personally, and it opens only while the Scope selector is set to that scope. If you open a hunt that belongs to another scope, from a link or after switching scope, Explorer shows This hunt belongs to Cyberdyne Systems (or Personal) in place of the hunt, with two buttons:
- Switch to Cyberdyne Systems changes your scope to the hunt's and opens it.
- Back to hunts takes you to the hunts list.
The same applies to the hunt's report. If you are not on the hunt's organization at all, you see Hunt not available instead.
Where hunts appear
The new navigation is rolling out and may not be enabled for your organization yet.
In the new navigation, Investigate › Hunts opens the Hunts page: Every investigation: running, waiting on you, and concluded with a verdict. It lists hunts only, in the list, campaign, card or board layout, with the filters that apply to hunts. Each hunt opens at its own link, and the breadcrumb reads Explorer › Investigate › Hunts › and the hunt's title. There is no Explorer tab bar: the hunts, chats and queries you have open are listed under Recent in the open navigation.
In the classic layout, hunts are listed under Activity › Hunts in Activity, each open hunt is a tab in Explorer, and every hunt you can see is a folder in the dock's Workspace tree with its needs-you count beside it.
Hunts waiting on you, and their approvals, also appear in the Inbox, and outcomes roll up in Pulse.
Next steps
- Start a hunt — the ways in, and the empty notebook
- Work in the notebook — the Plan block, cells, runs and results
- Conclude a hunt — verdicts, open issues and reports
- Hunt playbooks — save a hunt as a reusable definition and launch it later