Platform · Threat Intelligence
Intelligence matters when it meets your data. Bring your own TAXII and MISP feeds, retro-hunt indicators across your history, and see what is relevant to you.
[ipv4-addr:value = '185.220.101.47'] OR [file:hashes.'SHA-256' = '9f2c…a41e'] OR [domain-name:value = 'cdn-update-check.net']
| Connection | Translated to | Matches | Status |
|---|---|---|---|
| huntbase (lake) | KQL | 2 | Done |
| acme-iceberg | KQL | 5 | Done |
| Sentinel | KQL | 0 | Done |
| Splunk | SPL | 1 | Done |
| Elastic | ES|QL | — | Running |
Write a STIX 2.1 pattern once. Huntbase sweeps every connection in one run and hands back the matches.
Indicators, CVEs, ATT&CK techniques and the groups behind them, joined to your devices, users and hunts.
Connect private TAXII 2.1 and MISP feeds. Look indicators up in bulk and retro-hunt them across what you already store.
02Relationships graph
Public intelligence arrives with its relationships already drawn, and your own entities sit beside it. Open the canvas and ask Scout what it sees.
03Every indicator
TLP and statement (copyright) markings are kept with each indicator and shown on it.
STIX versioning and revocation are followed per indicator, so a revoked indicator stops matching.
Each indicator shows who produced it, from its STIX Identity.
CIDR ranges are matched live against incoming telemetry, as well as in retro-hunts.
Feeds, indicators and lookups are available over the API with API keys, for automation.
Tested against the 24 OASIS STIX 2.1 consumer interoperability test cases, over TAXII 2.1.
04In the loop
A high-confidence indicator match opens a hunt. A sweep becomes a hunt; a hunt becomes a watcher; the watcher fires on the next indicator.
Open by design
STIX 2.1
Write a pattern once; sweep every connection.
CACAO v2
Playbook export for partners, as JSON or YAML.
MITRE ATT&CK
Techniques, groups, software, mitigations and campaigns in the graph.
CVE · CWE · CAPEC · CPE
The vulnerability chain as linked public entities.
Questions
Yes. Connect private TAXII 2.1 and MISP feeds alongside the public intelligence Huntbase provides.
Yes. Look indicators up in bulk, and retro-hunt them across your stored history to see whether they were already in your environment.
Threats are scored for relevance to your environment, and an ATT&CK coverage heatmap shows where your detections and hunts are thin.
TLP and statement (copyright) markings are kept with each indicator and shown on it. Scout's briefings respect TLP, and intelligence marked TLP:RED never leaves Huntbase.
No. Huntbase brings public intelligence and its own tradecraft. Scout doesn't train shared models on your data.
Sweep new intelligence as soon as it lands. Your analysts decide what it means.