๐๏ธ Hunt playbooks
A hunt playbook is a reusable hunt definition: the hypotheses, queries, checkpoints, analytics and tasks that make up a hunt, saved as a versioned document you can launch again and again. Playbooks live in the Content library (the Library), which opens on the Hunt playbooks facet by default.
๐๏ธ Watchers
Content library โบ Watchers (in the Content library) is the catalog of watcher templates your organization can use. A template is a watcher you can switch on for your organization as it is, or copy and change into a watcher of your own. The catalog holds:
๐๏ธ Test data
Content library โบ Test data is the Huntbase test lake: a catalog of public attack recordings and real-world baseline telemetry, loaded and parsed into the same tables as your own data. Use it to see what a technique really looks like in the logs, to test a watcher before it goes near your estate, and to check a hunt query finds something before you run it on your telemetry.
๐๏ธ Add your team's knowledge
Content library โบ Knowledge is where your organization keeps its own reference documents for Scout: incident response runbooks, security policies, escalation paths, and notes about your environment (which subnets hold what, who owns which systems, which alerts are known to be noisy). Upload a document once and Scout uses it whenever it answers, next to Huntbase's curated guidance, and cites the exact section it relied on.
๐๏ธ Scripts
Content library โบ Scripts holds the scripts Scout can run on your endpoints. A script is reviewed and signed before any endpoint will run it. Each run is tied to the exact bytes and arguments that were approved, so a changed script, or a script someone swapped on the way, is refused.
๐๏ธ Actions
An Action is a saved, versioned response, such as Isolate endpoint or Initiate patch. People run it without seeing or choosing the script underneath. Each Action sets:
๐๏ธ Query templates
Query templates are saved, reusable queries โ from Huntbase's built-in catalogue, from content packs that ship with your connections, or saved by your team from the query workspace. You browse them in the Content library, open them straight into a query in Explorer, and schedule them to run on their own.
๐๏ธ Evidence collections
An evidence collection is a template that gathers files and artefacts from endpoints: an osquery query whose results you keep, or a file collection (carve) that copies a file into your storage destination. You keep them in the Content library under Evidence collections (/library?type=collection) and run them against your endpoint fleets.
๐๏ธ Schedules
A schedule runs a query template automatically โ once at a set time, or on a recurring cadence โ so recurring checks keep producing results without anyone pressing run. Schedules are created from a template in the Content library (or from a query you've run) and managed from the template's Schedules tab or the Schedules page.
๐๏ธ Content packs
A content pack is a named, versioned set of Huntbase content that belongs together: the products it needs, query templates and scheduled inventories, watchers, hunt playbooks, report templates, evidence collections, compliance checks and the knowledge Scout cites. Instead of switching on dozens of items one by one, you enable a pack, choose how much of it runs, and Huntbase sets it up for your organisation. When the pack gets a new version, Huntbase updates it for you and keeps your changes.
๐๏ธ AI Security pack
The AI Security pack finds the AI tools, models, agents and MCP servers in use in your organisation, and helps you hunt for AI misuse. It takes stock of the AI on your endpoints, adds the queries for your AI platforms, and brings hunts for AI-related attacks. It's an optional content pack: Huntbase makes it available to your organisation, and it runs only once an organisation admin enables it.
๐๏ธ Identity Threats pack
The Identity Threats pack detects and hunts account takeover across Okta, Microsoft Entra ID and Google Workspace. It schedules queries for MFA fatigue, risky and impossible-travel sign-ins, OAuth consent grants, admin role grants, new application credentials, legacy authentication, suspicious Google logins and domain-wide delegation. It checks for admins without MFA, switches on identity correlation watchers, and brings hunts for token theft, session hijacking, consent phishing and password spraying.