nano SIEM
Enrichments

Enrichment architecture

Supported in:Self-hosted

How nano fetches feed data, loads it into ClickHouse dictionaries and stamps it onto events at ingest.

Use this architecture guide to trace how feed data becomes event context. Enrichment runs once, at ingest, inside ClickHouse. Vector parses a log into an OCSF event and inserts it; the materialized view that builds ocsf_logs rows looks each IP, domain and hash up in in-memory ClickHouse dictionaries and writes the results into the row.

Where values land

nano never adds top-level fields of its own to an OCSF event. Enrichment fills:

  • the standard OCSF endpoint attributes (*.location.country, *.location.continent, *.autonomous_system.number, *.autonomous_system.name), only when the parser left them empty, so values from the source win;
  • nano-derived columns named under enrichments. (enrichments.ioc_*_threat_type, enrichments.custom_*_ip_tags). A parser that already emits an enrichments[] entry with the same name wins;
  • the prevalence_* columns, computed from the prevalence dictionaries.

See Enrichment field reference.

Platform feeds

nano publishes IPinfo Lite, ThreatFox and the Tor exit list as one signed bundle:

  1. The jobs leader asks nano's feed endpoint for the current bundle (open core: the open feed; Self-run with a license: the licensed feed; or your own mirror set with PLATFORM_FEEDS_URL).
  2. It verifies the bundle's signature against keys compiled into the release before downloading it, then checks its digest, length and sequence. Older or substituted bundles are refused.
  3. Each feed is written into ClickHouse under its own generation key: IPinfo rows into ip_enrichments, ThreatFox and Tor rows into custom_enrichment_results.
  4. One commit row makes the whole generation visible at once. A load that fails part-way is never visible, and the last good generation keeps stamping.
  5. The dictionaries (ip_enrichment_dict with its geo trie and attributes, and ioc_enrichment_dict) refresh from those tables, and new events are stamped from them.

Air-gapped installs skip steps 1–2's download and import the same signed .nanfeed file with POST /api/enrichment/platform-feeds/import.

Your own data (Self-run)

  • Custom enrichments run in nano's embedded WebAssembly sandbox on their schedule. Their records are written to custom_enrichment_results and served by custom_enrichment_dict (tags on IPs) and custom_ioc_enrichment_dict (indicators).
  • IOC lists publish versioned rows into the same store and reload the custom IOC dictionary.
  • Prevalence counts are rolled up from ingested events into aggregate tables and served by the prevalence dictionaries.

Memory

Dictionaries live in ClickHouse memory. With the platform feeds on, ClickHouse needs at least 6 GB. If the IP dictionary can't load, events keep flowing without geo/ASN context and SIEM Health reports the dictionary as degraded.

Security

  • Signed feeds. A platform bundle is accepted only with a valid signature from a key compiled into your release, and never rolled back to an older sequence.
  • Sandboxed code. Custom enrichment code runs in an embedded WebAssembly sandbox with no file system, environment or shell, and can reach only the domains you list, over https. Every request is checked against private, loopback and metadata addresses, and credentials are added only to request headers, so the code never holds them.
  • Secrets. Feed upstream credentials are held by nano. Keys for Marketplace agent lookups are stored encrypted.

Troubleshoot

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

A feed stops adding values

Check the feed's state in Marketplace or GET /api/enrichment/platform-feeds. A stale feed still stamps; an expired feed no longer does. Then follow the troubleshooting guide.

What's next

On this page