baseline
Show what is new for a host, user or IP in the search window compared with its own recent history.
Use baseline to find activity that is new for a host, user, or IP compared with its recent history. Each row includes history coverage so you can assess the result.
Syntax
... | baseline [host="<value>" | user="<value>" | ip="<value>"] [window=<duration>] [dims=<field>[,<field>...]]| Argument | Default | Description |
|---|---|---|
host= / user= / ip= | inferred | The entity to baseline. If you leave it out, nano takes the entity from the search filter, for example device.hostname="ws-1" | baseline. |
window | 7d | How far back before the search range to look for prior activity. 1 to 90 days. A longer window is rejected. |
dims | all for the entity type | Limit the check to some dimensions. Name them by OCSF field (see Dimensions). |
The search time range is the window under examination. It is capped at the last 7 days of the range you pick. The lookback ends where the search range starts, so a noisy window can never become its own baseline.
Dimensions
Each dimension is checked on the side of the event where the entity is the actor, so a remote host's activity is not credited to the machine it connected to.
| Entity | Dimension | OCSF fields (use in dims=) |
|---|---|---|
host | users | user.name, actor.user.name |
host | processes | process.name |
host | destination IPs | dst_endpoint.ip |
user | hosts | src_endpoint.hostname, device.hostname |
user | source IPs | src_endpoint.ip |
user | processes | process.name |
ip | hosts | src_endpoint.hostname, device.hostname |
ip | ports | dst_endpoint.port |
ip | users | user.name, actor.user.name |
A field that doesn't belong to the entity type is rejected with the list of supported fields.
Coverage
"Never done before" only means something if the entity has enough history. Every row carries coverage:
coverage | Meaning | New values |
|---|---|---|
sufficient | At least 3 active days and 50 events in the lookback | Reported |
thin | Some history, but less than that | Reported. Treat them as leads. |
no_history | No activity in the lookback | Suppressed. Nothing is called new. |
unknown | History could not be read in time | The row is marked partial with a reason. |
baseline_unknown is true when a dimension's result filled with new values, so the baseline couldn't be established (a never-watched entity, or a scan). incomplete is true when a dimension was capped or not read; rerun with dims= to scan it on its own.
Output fields
One row per new value:
| Field | Description |
|---|---|
entity, entity_type | The entity and its type (host, user, ip) |
dimension | What is new: processes, destination IPs, users, hosts, source IPs, ports |
value | The new value |
count | Occurrences in the search window |
first_seen | When the value first appeared for the entity |
coverage, baseline_unknown, incomplete | See Coverage |
When nothing is new, you get one summary row with coverage and a note, so an empty result is never ambiguous.
Examples
What is new on a workstation (entity taken from the filter):
device.hostname="ws-hr-005.corp.local" | baselineOnly new processes, against 14 days of history:
device.hostname="ws-hr-005.corp.local" | baseline window=14d dims=process.nameHosts and source IPs a user has never logged on from:
* | baseline user="jsanchez" dims=src_endpoint.hostname,src_endpoint.ipNew destination ports for an internal IP:
* | baseline ip="10.1.3.87" dims=dst_endpoint.portNotes
- Keep the search range short. The view reads the search window plus the lookback.
- For rarity of an artifact across the whole environment (a hash or domain), use prevalence.
What's next
- asset: the full investigation view for the same entity
- prevalence: how rare an artifact is across all hosts
- lateral: movement paths for a user or host
- retro: sweep an indicator across history