lateral
Trace where a user or host moved: logons, lateral-movement connections and remote execution, hop by hop.
Use lateral to trace where a user, host, or IP moved during your search window. nano follows authentication, connections on lateral-movement ports, and remote-execution tools to return movement edges and a graph.
Use it to answer "where did this account go?" or "what did this compromised host reach?" without pivoting by hand.
Syntax
<seed filter> | lateral [seed=auto|user|host] [entity=<field>] [maxhops=<1-10>] [methods=auth,network,process]| Argument | Default | Description |
|---|---|---|
seed | auto | Which kind of entity to start from. auto tries users first, then hosts and IPs. |
entity | auto-detected | The field that holds the seed: user.name, actor.user.name, device.hostname, src_endpoint.hostname, dst_endpoint.hostname, src_endpoint.ip or dst_endpoint.ip. |
maxhops | 4 | How many hops to follow from the seed (1–10). |
methods | all three | Which evidence to follow: auth, network, process. |
The trace covers the search time range. Set it with the time picker or earliest=.
Seeding the trace
Put an exact match for the seed in the base search. lateral reads the seed from it:
user.name="mtaylor" | lateralstarts from that account.device.hostname="ws-it-083.corp.local" | lateral seed=hoststarts from that host.src_endpoint.ip="10.1.4.63" | lateral entity=src_endpoint.ipstarts from that IP.
Without an exact match, lateral takes the seed from the first matching events, so a broad base search can seed on an unexpected entity. The seed it used is shown in the result header.
Evidence it follows
| Method | What it looks for | Technique shown |
|---|---|---|
auth | Authentication events (class_uid=3002), events with activity_name="Logon", and events with an auth_protocol | The authentication protocol (kerberos, ntlm, negotiate), else rdp/ssh by destination port, else logon |
network | Connections to dst_endpoint.port 22, 135, 139, 445, 3389, 5985 or 5986 | ssh, dcom, smb, rdp, winrm |
process | Processes whose process.name contains psexe, wmic, winrs, powershell, pwsh, mstsc, ssh, schtasks or sc.exe | The tool, for example psexec or wmic |
A host seed also matches events that name the host only by an IP it held during the window.
Output
- Graph. The result view draws the movement graph: hosts and users as nodes, edges labeled by method with counts and first-seen times.
- Rows. One row per movement edge, with the time, user, source and destination host, IP and port, the method and technique (see the table above), the hop number (0 is the seed's own movement), the authentication type and result, the process name for process-based edges, and the log source.
- Header. The seed field and value, hops and methods used, total edges and unique hosts, and whether the trace stopped early at a hop because of its time budget.
Limits
Examples
Where did this account log on or connect in the last hour?
user.name="mtaylor" | lateralTwo hops from a suspected compromised workstation, logons and connections only:
device.hostname="ws-it-083.corp.local" | lateral seed=host maxhops=2 methods=auth,networkStart from an IP address:
src_endpoint.ip="10.1.4.63" | lateral entity=src_endpoint.ip maxhops=1Only logon evidence, one hop, first 50 edges:
user.name="lallen" | lateral entity=user.name methods=auth maxhops=1 | head 50Notes
- Narrow the time range and lower
maxhopsormethodswhen a trace takes long; each hop and method adds work. - Edges for the same source, destination and method within the same minute are collapsed into one.
- For a single host's activity and identity history, use asset.
What's next
- asset: investigation view for one host
- resolve_identity: resolve IPs to hosts and users
- sequence: ordered patterns for one entity
- tree: process and web trees