Huntbase Hub · Vertex Synapse
Use these hunts in Vertex Synapse.
A Storm package, huntbase-hub, reads this hub and writes each of its 445 hunts into your Cortex as a procedure you can pivot from: its steps, its queries, the ATT&CK techniques and CVEs it covers, and the research it came from.
Install
Run this in Storm as a user who can add packages. Your Cortex needs to reach hub.huntbase.io over HTTPS.
pkg.load https://hub.huntbase.io/synapse/huntbase-hub.jsonRun the same line again to update the package. The package is not code-signed, so leave out --verify.
Sync
huntbase.hub.syncThe first run pulls every hunt. Each run after that pulls only the hunts published or changed since the last one: the package keeps its place in the :ingest:latest property of the hub's meta:source node. Running it twice does no harm. Every node has a fixed identity derived from the hunt and step, so a changed hunt is updated in place rather than copied.
| Option | What it does |
|---|---|
--size 10 | Stop after ten hunts, oldest first. The next run carries on from there. |
--all | Ignore where the last run stopped and pull every hunt again. |
--url | Read a different copy of the hub. Defaults to https://hub.huntbase.io. |
To take one hunt, give its slug, the last part of its address on this site:
huntbase.hub.import activemq-lateral-movement-lockbitKeep it up to date
New hunts are published once a day. A daily cron job keeps your Cortex in step:
cron.add --name "Huntbase Hub sync" daily@10:30 { huntbase.hub.sync }Cron jobs run in UTC. Use cron.list to check it and cron.del to remove it.
What lands in the graph
Each hunt becomes a plan:procedure written to the current view. The hunt.md source is kept in full on :body.
| On the hub | In Synapse |
|---|---|
| Hunt | plan:procedure with :id set to the slug, :desc to the hypothesis, :url to its page here and :system to the hunt.md format |
| Each step | plan:procedure:step, tagged #rep.huntbase.step.<type>. The hypothesis is :firststep |
| Order of steps and decision branches | plan:procedure:link. A branch taken when the evidence supports the hypothesis has :condition=true, the other false |
| Query step | meta:rule holding the query text, with :type huntbase.query.<language>. The step -(uses)> the rule |
| Parameters | plan:procedure:variable nodes in the procedure's :inputs |
| ATT&CK techniques | meta:technique, linked from the procedure with -(refs)> |
| CVEs | risk:vuln, linked with -(refs)> |
| The research it came from | doc:report, linked with -(refs)> |
| Severity, TLP, tactics, products, series | Tags under #rep.huntbase on the procedure |
| This hub | meta:source named "huntbase hub", -(seen)> every procedure |
The hub's index entry and the native hunt definition are also stored as node data on each procedure, under huntbase:hub:entry and huntbase:hub:definition.
A few places to start:
// critical hunts
plan:procedure#rep.huntbase.severity.critical
// hunts that cover a technique
meta:technique:id=T1566 <(refs)- plan:procedure
// the queries in one hunt
plan:procedure:id=activemq-lateral-movement-lockbit -> plan:procedure:step -(uses)> meta:ruleRun them, not just read them
The hunts run in Huntbase.
In Synapse the hunts are knowledge you can link to your own intelligence. In Huntbase, Scout runs them against your data sources and records what it finds.