asset
Open the asset investigation view for a host, user, IP or MAC: resolved identities, an activity timeline and summary cards.
Use asset to investigate a host, user, IP address, or MAC address. nano resolves its related identities in your search window and shows matching activity across those identities.
Syntax
<filter for one asset> | asset [field=<field>]| Argument | Default | Description |
|---|---|---|
field | auto-detected | The identifier to investigate. If you leave it out, nano takes the first identifier it finds in the matching events (see the table below). |
Identifiers
field= accepts an exact OCSF path, or an identity kind that covers all paths of that kind:
| Kind | OCSF paths |
|---|---|
host | src_endpoint.hostname, device.hostname, dst_endpoint.hostname |
ip | src_endpoint.ip, dst_endpoint.ip |
user | user.name, actor.user.name |
mac | src_endpoint.mac, dst_endpoint.mac |
An exact path reads only that path. A kind such as field=user reads both user.name and actor.user.name.
What the view shows
- Profile: the primary identifier, the related identities resolved in the window, and first and last seen times.
- Activity: event volume over time.
- Timeline: matching events, newest first, each labeled by kind (process, file, authentication success or failure, network, DNS, cloud API, or the event's OCSF class) with a one-line summary.
- Summary cards: network, process, authentication and DNS activity, and rare or first-seen artifacts.
Click a value to drill down. The drilldown search stays scoped to the asset's identities.
Examples
Investigate a workstation:
device.hostname="ws-hr-005.corp.local" | assetInvestigate an internal IP:
src_endpoint.ip="10.1.3.87" | assetInvestigate a user, across both subject and actor fields:
actor.user.name="jsanchez" OR user.name="jsanchez" | asset field=userInvestigate the host behind a suspicious process, naming the identifier explicitly:
class_uid=1007 process.name="rundll32.exe" device.hostname="ws-it-083.corp.local" | asset field=device.hostnameNotes
-
Narrow the search to a single asset before
| asset. The view investigates one identifier. -
Identity resolution uses the search time range. Widen the range to pick up identities seen earlier.
-
The parser also accepts
sections=andmax_age=(from earlier releases). The asset view ignores both. -
The profile shows only what your logs record: IP, MAC, domain, vendor, users and hostnames. It doesn't pull directory attributes such as department, manager, MFA status or group membership.
What's next
- resolve_identity: add identity columns to rows without opening the view
- baseline: what is new for this host, user or IP
- lateral: movement paths from a user or host
- tree: process trees