Skip to main content

Set a hunt's time window

Every query step in a hunt searches a stretch of time. A time window on the hunt sets that stretch for all its steps at once, so a hunt about activity from last week searches last week, not just the last 24 hours.

The window works the same for every source a step can query: your SIEM, a log store such as Axiom, or the Huntbase data lake.

Where a step's window comes from​

When a query step runs, Huntbase picks its window in this order:

  1. The window you choose when you run that step again (see Run a step over another window).
  2. A window the step already has of its own, from an earlier run over a chosen window.
  3. The hunt's time window.
  4. The default: the last 24 hours.

A step keeps the window you last ran it over. When you change the hunt's window later, steps without their own window use the new one from their next run. A step with its own window keeps it.

Set the hunt's window​

The window shows as a chip with a clock in the hunt's header, next to the view switch, for example Window: Last 30 days or Window: 2–9 Nov. Without a window it reads Window: Step default, and its tooltip says each step searches its own window: the last 24 hours unless it says otherwise.

To change it:

  1. Click the chip. The list is headed Search the hunt's steps over.
  2. Pick Last 24 hours, Last 7 days, Last 30 days or Last 90 days, or Custom range… and pick a start and end day.
  3. To go back to no window, pick Step default (last 24 hours).

Steps use the new window from their next run. Nothing re-runs by itself.

The tooltip says who set the window:

NoteWhat it means
Set by youSomeone on your team picked it.
Set by ScoutScout picked it while planning the hunt.
Set from the evidence the hunt started fromThe hunt started from an insight, a look-back or an indicator with timestamps, and the window covers them with a day either side.

You need permission to edit the hunt to change its window. In a concluded hunt, the chip is read-only.

See what a step searched​

After a query step runs, its result header says which window it used, for example Ran over 2–9 Nov, even when the hunt's window is a rolling one such as Last 7 days. Hover it for the exact start and end. This is the window the run really used, so you can read a step's result without guessing what it covered.

Run a step over another window​

If you can edit the hunt, Ran over … is a button.

  1. Click Ran over … on the step.
  2. Under Run this step again over, pick:
    • Hunt window: and the hunt's window, when it has one;
    • Evidence: and the dates of the activity the hunt is about, when Huntbase knows them;
    • a preset, or Custom range….

The step runs at once over that window, and keeps it for its next runs.

When a step finds nothing​

A step that returns no rows may simply have looked in the wrong place in time. When the hunt knows when its evidence happened, and the step's window missed it, the step says so, for example The evidence is from 1–3 Nov; this step ran over 15–16 Nov., with a Re-run over 1–3 Nov button. One click runs the step over the evidence's dates.

When Scout's diagnosis of an empty result proposes a different window, the fix offers Re-run over … too, and runs the step directly.

Scout and the time window​

When Scout plans a hunt from an insight, a threat intel look-back or an indicator with timestamps, it sets the hunt's window from those timestamps. The steps it plans then search that window instead of the last 24 hours.

The same happens when a chat with Scout becomes a hunt, or a chat joins one: the hunt's window covers the times of the rows and findings in the chat. Scout only sets a window when the hunt has none, and you can change it at any time; your choice wins from the next run.

Next steps​