nano SIEM
Hunts

Administer hunts

Supported in:Self-hosted

Set up AI for hunts, check the server runner, configure the scheduler and retention, and grant hunt permissions.

Set up hunts for your team. Assign AI models to the hunt agents, check the server runner, decide how long hunt history is kept, and grant permissions.

Set up AI for hunts

The server runner and the reviewer use the AI provider you configure in nano.

  1. Configure a provider in Settings → AI & pivt → Providers. See AI & pivt.
  2. Click Agent Models.
  3. In the Hunt group, assign a model to each hunt agent.
AgentDefault modelWhat it does
Hunt investigator (hunt_investigator)workers-ai/@cf/zai-org/glm-5.3Investigates each run
Hunt reviewer (hunt_reviewer)workers-ai/@cf/zai-org/glm-5.3Checks each lead
Hunt recheck (hunt_recheck)workers-ai/@cf/zai-org/glm-5.3-flashChecks known attackers

The investigator and reviewer models must support tool calling. If you have more than one provider, consider giving the reviewer a model from a different family than the investigator. nano measures the reviewer's accuracy separately for each model.

Reasoning effort

The hunt agents use low reasoning effort by default. At higher effort, a reasoning model can use its whole output allowance on thinking and never run a query. If you changed an agent's effort, nano keeps your setting.

The Agent Models page doesn't show reasoning effort. To change it, call the API. You need settings:agent_models.

curl -X PUT "https://<your-nano-host>/api/settings/agent-models/hunt_reviewer" \
  -H "X-API-Key: $NANO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"reasoning_effort": "low"}'

Check the server runner

  1. Click Hunts, then Runners.
  2. Check that the server runner shows online and lists your investigator model.

The server runner needs:

  • an AI provider, and an investigator model that supports tool calling;
  • a valid license;
  • the jobs service's database administrator credentials, which it uses to create its own read-only user;
  • a free connection slot. There are 6 by default, and fewer on small installations.

It doesn't need the Agent Lane switch, listener, or allow-list that external agents use.

Server runner settings

Set these environment variables on the jobs service (nano-jobs). Each applies to one jobs instance.

VariableDefaultMeaning
NANO_HUNTS_SERVER_RUNNERonSet to off to stop the server runner
NANO_HUNTS_SERVER_CONCURRENCY1Runs at the same time on this instance, 1 or 2
NANO_HUNTS_RUNNER_LABELnano-jobs and the node nameThe runner's name. Give each instance on one node its own name.
NANO_HUNTS_REVIEWER_DESKTOP_GRACE_SECS600Seconds to wait after a Desktop run before the server reviews its leads

Scheduler settings

VariableMeaning
HUNT_SCHEDULER_ENABLEDSet to false to stop all scheduled runs. Hunts then run only with Run now.
HUNT_SCHEDULER_POLL_INTERVAL_SECSHow often, in seconds, nano checks for hunts that are due
HUNT_SCHEDULER_BATCH_SIZEMost hunts queued on each check

Retention

nano cleans up hunt history once an hour. Set these environment variables on the jobs service to change how long it keeps each kind of data.

DataDefaultVariable
Suppressions that stop matchingExpire after 60 daysHUNT_RETENTION_SUPPRESSION_IDLE_DAYS
Expired or revoked suppressionsDeleted 30 days laterHUNT_RETENTION_SUPPRESSION_GRACE_DAYS
Expired baselines and notesDeleted 30 days laterHUNT_RETENTION_KNOWLEDGE_GRACE_DAYS
Revoked baselines and notesKept, so they can't be learned again (0 means never delete)HUNT_RETENTION_REVOKED_KNOWLEDGE_DAYS
Dismissed findingsDeleted after 180 daysHUNT_RETENTION_DISMISSED_LEAD_DAYS
Finished runsDeleted after 90 daysHUNT_RETENTION_SWEEP_DAYS
Rejected rule ideasDeleted after 90 daysHUNT_RETENTION_REJECTED_IDEA_DAYS
Deployment profilesNewest 10 keptHUNT_RETENTION_PROFILES_KEEP
Disabled runnersDeleted after 180 days without contactHUNT_RETENTION_RUNNER_IDLE_DAYS
Dormant campaignsClosed after 90 days (0 means never)HUNT_RETENTION_CAMPAIGN_DORMANT_DAYS

nano never deletes:

  • promoted findings, even after their case is deleted;
  • findings that nobody has triaged yet;
  • findings that support a rule idea that isn't rejected;
  • the newest run of each hunt, or a run that still has findings.

To turn cleanup off, set HUNT_RETENTION_ENABLED=false.

Hunts never delete event data. Events age out with your normal event retention. If a finding's events have aged out, the finding says so.

Grant permissions

Hunt permissions are separate from playbook permissions. Deciding what runs on its own against all your data is a different responsibility from editing response procedures.

PermissionAllowsAdminEditorReadOnly
hunts:viewView hunts, runs, findings, memory, campaigns, rulings, the profile, and runnersYesYesNo
hunts:runRun a hunt now, change its schedule, and enable or disable itYesYesNo
hunts:triagePromote and dismiss findings, record rulings, link findings to campaigns, and acknowledge escalationsYesYesNo
hunts:manageCreate, edit, and archive hunts and campaigns, change escalation settings, request reviews, and act on rule ideasYesNoNo
hunts:reportReport run results. Used by a runner's key.YesNoNo
hunts:profile_writeSave a deployment profile and create draft hunts. Used by a profiling key.YesNoNo

Promoting a finding also needs cases:create. Acknowledging an escalation also needs cases:edit.

The ReadOnly role has no hunt permissions, because every new user gets it through the Everyone group. To give read-only access to hunts, add hunts:view to a custom role. See Access control.

Users must sign in again after you change their roles.

What's next

On this page