nano SIEM
Enrichments

Enrichment field reference

Supported in:Self-hosted

Every field nano's enrichments write: endpoint location and autonomous system attributes, threat-intel match fields, custom tags and prevalence counts.

Use these fields to search and inspect enrichment data on your events. ClickHouse writes them at ingest into the ocsf_logs row:

  1. Standard OCSF endpoint attributes, filled by IP geolocation.
  2. nano-derived enrichments.* columns for threat-intel matches and custom tags.
  3. prevalence_* columns with host counts.

All the fields below are searchable. For the rest of the schema, see OCSF field reference.

Endpoint attributes

Written by IPinfo Lite for public IPs, only when the parser left them empty.

PathTypeExample
src_endpoint.location.countrystring, ISO 3166-1 alpha-2DE
src_endpoint.location.continentstringEurope
src_endpoint.autonomous_system.numberinteger24940
src_endpoint.autonomous_system.namestringHetzner Online GmbH
dst_endpoint.location.country, dst_endpoint.location.continentas above
dst_endpoint.autonomous_system.number, dst_endpoint.autonomous_system.nameas above

Threat-intel match fields

Written from the platform IOC dictionary (ThreatFox and Tor exit nodes). Each holds the matching indicator's threat type, or is empty.

FieldChecked againstExample
enrichments.ioc_src_ip_threat_typesrc_endpoint.iptor_exit
enrichments.ioc_dest_ip_threat_typedst_endpoint.ipbotnet_cc
enrichments.ioc_domain_threat_typeurl.hostname, http_request.url.hostname, query.hostname (first match wins)payload_delivery
enrichments.ioc_hash_threat_typefile.hashes.sha256, process.file.hashes.sha256 (first match wins)payload

Custom tags

Written from custom enrichments that aren't IOC feeds. Each holds the matching record's tags, comma-separated.

FieldChecked against
enrichments.custom_src_ip_tagssrc_endpoint.ip
enrichments.custom_dest_ip_tagsdst_endpoint.ip

Producer-supplied enrichments[]

A parser or sender can emit OCSF's own enrichments[] list. Its name and value leaves are stored as the array columns enrichments.name and enrichments.value, and the rest of each element stays in the event. If an element's name is one of the derived fields above (for example ioc_dest_ip_threat_type), its value wins over the dictionary lookup.

enrichments.value="203.0.113.7" | table time, metadata.log_source, enrichments.name, enrichments.value

Prevalence

FieldCounts hosts that have seen
prevalence_file_hashfile.hashes.sha256
prevalence_process_hashprocess.file.hashes.sha256
prevalence_dest_domaindst_endpoint.hostname (not an IP literal)
prevalence_dest_ipdst_endpoint.ip (public addresses only)

The value is the host count known at ingest. An artifact not yet in the prevalence summary reads as 1. 65535 means the event has no such artifact (for example no hash, or a private destination IP).

For prevalence at search time (current counts, not the counts at ingest), use the prevalence command.

Examples

Every threat-intel match on a destination, by threat type:

enrichments.ioc_dest_ip_threat_type=* | stats count by enrichments.ioc_dest_ip_threat_type, dst_endpoint.ip

Rare file hashes seen on fewer than three hosts:

prevalence_file_hash<3 | stats count by file.hashes.sha256, device.hostname

Top destination networks:

dst_endpoint.autonomous_system.name=* | top limit=10 dst_endpoint.autonomous_system.name

When a field is missing

  • The IP is private or reserved. IPinfo and prevalence skip non-public addresses.
  • The event has no field to enrich. The parser didn't map an IP, domain or hash to the fields above.
  • No match. ThreatFox, Tor and custom enrichments write a value only for a match.
  • The event predates the feed. Enrichment happens at ingest. Older events keep what they were stamped with.
  • The feed is expired, or ClickHouse is short of memory. See Troubleshooting.

What's next

On this page