retro
Sweep an indicator, a list of indicators, a feed or a lookup table across your whole history, and open a hunt summary.
Use retro to check whether an indicator has appeared in your retained history, where it appeared, and how rare it is. nano reads the indicators from an ioc search term and opens a hunt summary.
The ioc search term
ioc is a search term, not a command. It matches an indicator in every OCSF field that can hold one, so you don't have to know where it appears. You can use it in any search, with or without retro:
ioc=185.220.101.45 | stats count by metadata.log_source, src_endpoint.ip, dst_endpoint.ipThe fields searched depend on the kind of value:
| Value | Fields searched |
|---|---|
| IP address | src_endpoint.ip, dst_endpoint.ip |
| Domain | http_request.url.hostname, url.hostname, query.hostname, dst_endpoint.hostname |
| URL | http_request.url.url_string, url.url_string |
| File hash | file.hashes.value, process.file.hashes.value, actor.process.file.hashes.value |
| Email address | email.from, email.to, user.name, user.uid, actor.user.name, actor.user.uid |
| CVE | vulnerabilities.cve.uid |
Domain, URL, email and CVE matches are case-insensitive.
Forms
| Form | Matches |
|---|---|
ioc=<value> | One indicator. Quote it only if it contains spaces or special characters. |
ioc in [v1, v2, ...] | Any indicator in the list |
ioc in [inputlookup <table>] | Any value in one of your lookup tables |
ioc in lookup("<table>") | Any value in a lookup table; lookup("<table>", "<column>") reads one column |
ioc in threatfox("<query>") | Indicators from a threat feed. Feeds: threatfox, misp, otx, feodo, abuse |
The feed and lookup(...) forms work only in the base search, not inside a subsearch.
Syntax
<ioc term> | retro [by indicator | asset | user]retro must be the last command.
by | View |
|---|---|
(none) or indicator | Per indicator: a summary for one ioc= value, or a list ranked rarest first for a list, feed or table |
asset | Matches rolled up to hosts. host, ip, entity and account are aliases. |
user | Matches rolled up to users |
An unknown by value falls back to indicator.
Examples
One IP across all history:
ioc=185.220.101.45 | retroA file hash, whether it appeared as a written file or a running process:
ioc=44d88612fea8a8f36de82e1278abb02f | retroA campaign's indicators, rarest first:
ioc in [185.220.101.45, evil-c2.example, 44d88612fea8a8f36de82e1278abb02f] | retroThe hosts that touched any of them, for containment:
ioc in [185.220.101.45, evil-c2.example] | retro by assetEvery indicator in a lookup table, rolled up by user:
ioc in lookup("threat_iocs") | retro by userNotes
retrosearches full retention, up to 365 days; you don't need to widen the time picker.- Each indicator gets a rarity verdict from your prevalence data. See prevalence.
What's next
- prevalence: rarity of artifacts in ordinary searches
- lookup: your lookup tables, the source of
ioc in lookup(...) - asset: everything about one host