Run watchers as Axiom monitors
A watcher deployment on Axiom normally means Huntbase searches your dataset on a schedule. You can also push a Sigma watcher into Axiom, where it runs as one of Axiom's own monitors. Axiom then runs the rule on its schedule, and what the monitor fires comes back to Huntbase as detections.
Pushing works the same way as for Splunk, Microsoft Sentinel and Google SecOps. This page covers what is specific to Axiom. For modes, statuses, drift and removing a rule, see Push rules into Splunk, Sentinel or Axiom.
What Huntbase creates in Axiom
| Watcher | Axiom monitor |
|---|---|
| A single-event Sigma rule | A match monitor: Axiom sends each matching event. |
A Sigma rule with a count condition, such as selection | count() by TargetUserName > 10 | A threshold monitor: Axiom counts per group and fires when a group crosses the threshold. Only Axiom can take these: on other SIEMs the deployment shows Can't run here. |
Correlation rules, which join events across a window, run as scheduled searches that Huntbase runs on your dataset. They can't be pushed as monitors.
The monitor is named Huntbase - <watcher> [<id>], and its description ends with a Huntbase marker. Leave the marker in place: Huntbase uses it to recognise its monitors.
Axiom limits match monitors: it refuses one whose query matched more than 500 events in the last 24 hours. The deployment then shows Push failing with Axiom's reason. Tune the rule, or deploy it as a scheduled search instead.
Allow the connection to write monitors
Your Axiom connection is read-only by default. To push monitors, a connection admin adds a rule-write credential: a second Axiom API token used only to create, update and delete monitors.
In Axiom, under Settings › API tokens, create an advanced API token with:
- permission to create, read, update and delete monitors and notifiers;
- query permission on the datasets the rules read.
Axiom doesn't let you change a token's permissions after you create it. If the token is missing a permission, create a new one. Without these permissions the push fails with a message that names what to grant.
Then add the token to the connection as its rule-write credential. See Allow a connection to write rules.
Get alerts back into Huntbase
Huntbase collects monitor alerts in two ways. Both give the same detection, so nothing is raised twice.
- Webhook. Huntbase adds a notifier to each monitor that posts to the connection's Huntbase webhook. The webhook must use Basic Auth or Custom Header: Axiom sends fixed headers, so it can't sign requests for HMAC Signature or JWT (Bearer Token). Without a suitable webhook the push still works, and the deployment says alerts can't come back by webhook.
- Polling. Every 5 minutes Huntbase reads each monitor's history from Axiom and picks up anything the webhook didn't deliver. This also covers Huntbase environments that Axiom can't reach.
Polling reads the monitor's notification history, and Axiom only keeps history for a monitor that has a notifier. Some Axiom plans don't include webhook notifiers. On those plans the push still works, the monitor runs in Axiom, and Huntbase tells you that alerts can't come back. Keep a Search on the store deployment of the same watcher so its detections still reach Huntbase, or ask Axiom to enable webhook notifiers for your organization.
A match monitor's events become rows on the detection. A threshold monitor raises one detection per group that crossed the threshold, for example one per user name.
The detection lists Axiom under Seen in, and Where alerts are handled works as for other pushed rules: In Huntbase or In Axiom only.
Modes
| Mode | In Axiom |
|---|---|
| Off or Paused | The monitor stays in Axiom, disabled. |
| Shadow | The monitor runs and notifies Huntbase. Detections are recorded, but nothing reaches Needs you. |
| On | The monitor runs, and its detections reach Needs you. |
The monitor runs at the deployment's frequency, at least every 5 minutes.
Drift
Huntbase reads each monitor back and compares the parts it manages: name, description, type, query, schedule, time range, threshold, whether it is disabled, how it groups alerts, and whether the Huntbase notifier is still attached. Someone who edits the monitor in Axiom sees Edited in Axiom, with what changed. Re-push puts the Huntbase version back.
Compute
Monitors run in Axiom, so they use your Axiom query compute, not your Huntbase query budget. Each run counts. A monitor that runs every 5 minutes runs 12 times as often as an hourly deployment. See Keep query compute low.