nano SIEM
Search Commands

resolve_identity

Supported in:Self-hosted

Resolve an IP, hostname or user in each row to the host, user and IP your other events tie it to at that time.

Use resolve_identity to identify the host or user associated with an IP address, hostname, or user name at the event's time. nano uses observations from your events to fill empty OCSF fields.

resolve-identity is an alias.

Syntax

... | resolve_identity [field=<field> | <field>] [max_age=<duration>]
ArgumentDefaultDescription
fieldsrc_endpoint.ipThe field to resolve. Only the first field is used if you list several.
max_age24hThe newest identity observation must be at most this far from the event's time. Older observations are ignored.

Fields you can resolve:

KindFields
IP addresssrc_endpoint.ip, dst_endpoint.ip, device.ip
Hostnamesrc_endpoint.hostname, dst_endpoint.hostname, device.hostname
Useruser.name, actor.user.name

Output

resolve_identity fills the row's own OCSF paths that are empty, for example src_endpoint.hostname and user.name when you resolve src_endpoint.ip. Values the event already carries are never overwritten. Later commands use the filled paths like any other field.

Identities come from your own events: endpoint, authentication and DHCP logs that name a host or user together with an IP. A value that no event ties to an identity stays empty.

If no row carries the field, or nothing resolves, the search returns the rows unchanged with a warning explaining why. A failure in the resolution itself fails the search rather than returning unresolved rows.

Resolved rows also include identity_ip, identity_hostname, identity_fqdn, identity_user, identity_mac, identity_source, and identity_observed_at. Use these columns to inspect the resolution result even when the event already has an OCSF value.

Examples

Who was behind the source IPs of proxy requests:

metadata.log_source=conduit_proxy | resolve_identity field=src_endpoint.ip | table time, src_endpoint.ip, src_endpoint.hostname, user.name, http_request.url.hostname

Top users and hosts behind proxy traffic, by resolved identity:

metadata.log_source=conduit_proxy | head 1000 | resolve_identity field=src_endpoint.ip | stats count by src_endpoint.hostname, user.name | sort -count | head 10

Resolve endpoint events by host name, allowing week-old observations:

class_uid=1007 process.name="powershell.exe" | resolve_identity field=device.hostname max_age=7d | table time, device.hostname, device.ip, actor.user.name, process.cmd_line

Run commands after enrichment

resolve_identity is not compiled into the ClickHouse query. The search splits at the first lookup, prevalence, inputlookup, resolve_identity, ai or lateral stage, and every command after it runs in post-processing on the returned rows. Only these commands work there: where, head, tail, sort, table, stats, dedup, rename, fields, top, rare, fillnull, eval, timechart, rex, risk, reverse, tree.

Only the returned rows are resolved, so filter first. resolve_identity inside a subsearch (append, join, IN [ ... ]) is refused.

What's next

  • asset: everything nano knows about one host
  • lookup: add context from your own tables
  • tree: process and web activity trees

On this page