Auto Retro-Hunt
Automatically match newly-landed threat-intel indicators against your historical logs with retro-hunt rules.
Create a retro-hunt rule to match newly arrived threat-intelligence indicators against historical logs. You can find activity that occurred before the feed identified the indicator.
Hits are first-class detections — they flow through the normal alert and case pipeline like any other detection match.
Creating a retro-hunt rule
Create the rule in the rules area, like any other detection rule. A retro-hunt rule is configured with:
| Setting | Meaning |
|---|---|
| Feeds | Which threat-intel feeds to hunt indicators from — specific feeds, or all |
| Artifact types | Which indicator types to match: ip, domain, hash, url |
| Lookback window | How far back in your logs each indicator is hunted (default 90 days, max 365) |
| Schedule | Cron expression controlling how often the rule runs |
| Max indicators per run | Cap on indicators hunted in a single run |
How it works
Each run:
- Computes the delta of indicators newly landed since the last run, tracked by a watermark.
- Hunts only those indicators across your logs over the lookback window.
- Emits hits through the standard signal processor — the same path as every other detection.
Re-running never re-alerts on already-hunted indicators: an indicator is hunted once, when it lands. If a run exceeds the per-run cap, the overflow carries over to the next run and is recorded on the run — nothing is silently truncated.
Run history
Each run records the number of indicators processed, the hits it produced, and any truncation (overflow carried to the next run). Use it to confirm the rule is keeping up with feed volume.
Lifecycle
See detection rule modes for how Staging / Live / Alerting behave in general.
Relationship to the | retro command
The interactive | retro search command is the manual, one-off version of the same engine: you bring an indicator and sweep history on demand. A retro-hunt rule automates that sweep for every new indicator your feeds deliver.
Troubleshoot
Need help with these checks? Contact support with the affected deployment, request ID and time with timezone.
The rule processes no indicators
Check that the selected threat-intelligence feeds are syncing. A rule without feed data has no indicators to hunt.
Promoting to Alerting does not alert on old indicators
The rule advances its watermark while hunting in Live mode. Create the rule in Alerting if you need alerts for the current backlog.
Indicators carry over between runs
Compare the run history with the per-run cap. Overflow carries to the next run; use the history to check whether the rule is keeping up.
What's next
Detection Rules & Threat Hunting
Write, test and promote nPL detection rules over OCSF events — lifecycle, scheduling, real-time rules, alert modes and findings.
Alerts & Incident Response
Triage nano alerts from detection rules: alert states, acknowledging and closing with a disposition, bulk actions, filters, metrics and troubleshooting.