nano SIEM
Case Management

Entities & Entity Graph

Supported in:Self-hosted

Which entities nano extracts from an alert's OCSF events, and how to work them in the case workspace.

Inspect a case’s entities to identify the users, hosts, IPs, domains, and hashes involved in the investigation. When an alert joins a case, nano extracts these entities from its matched events and attaches them to the case.

Entity types

TypeDescriptionExamples
UserAccounts and identitiesadmin, jsmith@corp.com
HostHostnames and computer namesSRV-PROD-01, LAPTOP-ABC123
IPIPv4 addresses203.0.113.42, 10.0.0.1
DomainDomain namesevil.example, api.example.org
HashFile hashes (MD5, SHA-1, SHA-256)a1b2c3…
URLFull URLshttps://evil.example/malware.exe
FileFile paths and names/tmp/payload.sh
ProcessProcess names and command linespowershell.exe
EmailEmail addressesattacker@evil.example

Entity extraction

Extraction runs in two passes over each matched event:

  1. Named fields. nano walks the event's OCSF 1.9 object tree and checks each field's full dotted path.
  2. Value sweep. Every string value in the event, including message and raw_data, is scanned for public IPv4 addresses, URLs, MD5/SHA-1/SHA-256 hashes and email addresses.

Fields read by type

EntityOCSF 1.9 fields
Useruser.name, actor.user.name, user.uid
Hostsrc_endpoint.hostname, dst_endpoint.hostname, device.hostname
IPsrc_endpoint.ip, dst_endpoint.ip (plus IPs found by the value sweep)
Domainhttp_request.url.hostname, url.hostname, query.hostname
Hashfile.hashes.value, process.file.hashes.value, actor.process.file.hashes.value (plus hashes found by the value sweep)
URLhttp_request.url.url_string, url.url_string (plus URLs found by the value sweep)
Filefile.path, file.name, process.file.path, actor.process.file.path
Processprocess.name, actor.process.name, process.cmd_line, actor.process.cmd_line
EmailFound by the value sweep in any string, for example email.from or actor.user.email_addr

On Detection Finding events, the affected-resource fields (resources.hostname, resources.device.hostname, resources.ip, resources.user.name, resources.user.uid) are also read as hosts, IPs and users.

For the full path list by entity, see the OCSF field reference.

Value checks

  • A user value that looks like an IP or a hash is skipped.
  • A host value that is an IP, a single character, all digits, or a placeholder (localhost, unknown, none, n/a) is skipped.
  • Domains are stored lowercased. A domain under an internal suffix (a built-in one, or one you set with PUT /api/settings/internal-domains) is recorded as a host, not a domain.
  • Hashes and email addresses are stored lowercased. When the same string matches several hash lengths, the longest wins.

Entities tab

The Entities tab in the case's evidence drawer lists the case's entities grouped by type. For each entity you can:

  • See how often it occurs in the case and whether it is the case's primary entity.
  • See its risk score (0–100) from risk-based alerting and open a Risk breakdown. Users, hosts, IPs, domains, hashes and email addresses carry risk; processes, files and URLs don't.
  • Pivot in search. This opens Search filtered to the entity, with the time range set to the case's alert window (first to last alert, padded by one hour).

Entity graph

The entity graph shows the case's entities as nodes, colored by type.

  • Views: switch between the graph and a table. Cases with more than 15 entities open in the table view.
  • Filter: show or hide entity types.
  • Navigate: drag nodes, drag the background to pan, and scroll or use the zoom buttons to zoom. The fit button resets zoom and position.
  • Export: save the graph as entity-graph.png.

Edges

Edges connect entities whose types commonly relate:

Type group
User, Host, IP
Host, IP, Domain
IP, Domain, URL
Process, File, Hash
User, Email

Primary entity

Each case has one primary entity. nano picks it by type, in this order: host, user, IP, domain, hash. The primary entity is marked in the Entities tab.

API reference

Entities are returned grouped by type as part of the case:

GET /api/cases/{id}

The entities field holds one summary per type, each with a count and the entities:

{
  "entities": [
    {
      "entity_type": "user",
      "count": 1,
      "entities": [
        {
          "entity_value": "admin@corp.com",
          "occurrence_count": 15,
          "is_primary": true,
          "risk_score": null,
          "enrichment_data": null
        }
      ]
    }
  ]
}

Finding events for an entity

To see the events behind an entity, search the entity's OCSF paths directly. For example, everything involving one IP or one user:

src_endpoint.ip="203.0.113.42" OR dst_endpoint.ip="203.0.113.42"
| stats count by class_name, metadata.log_source
actor.user.name="jsmith" OR user.name="jsmith"
| stats count by class_name, device.hostname

Best practices

  1. Check the primary entity. Make sure it represents the case's focus.
  2. Pivot freely. Pivoting from entities into Search is how investigations expand.
  3. Watch for hub entities. An entity that recurs across many cases can point to a compromised account, an infected host or C2 infrastructure. See related cases.
  4. Export the graph to include the case's entity set in reports and tickets.

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

An internal IP is missing

The value sweep skips private and loopback addresses. Check whether the event provides the address in src_endpoint.ip or dst_endpoint.ip.

A graph edge does not match the evidence

Edges connect related entity types, not proven co-occurrence. Search the events to confirm the relationship before treating it as evidence.

What's next

On this page