nano SIEM
Enrichments

Enrichments

Supported in:Self-hosted

Context nano adds to events at ingest: geolocation, threat intel matches, Tor exit nodes, prevalence and your own indicators.

Use enrichments to add geolocation, threat intelligence, and other context to your events. nano writes this context at ingest, as ClickHouse stores each event, by looking values up in in-memory ClickHouse dictionaries. You can search, alert on, and chart enrichment fields like any other field.

Find enrichment fields

ContextFields
IP geolocation and network ownersrc_endpoint.location.country, src_endpoint.location.continent, src_endpoint.autonomous_system.number, src_endpoint.autonomous_system.name, and the same under dst_endpoint
Threat-intel matches (ThreatFox, Tor exits)enrichments.ioc_src_ip_threat_type, enrichments.ioc_dest_ip_threat_type, enrichments.ioc_domain_threat_type, enrichments.ioc_hash_threat_type
Custom enrichment tagsenrichments.custom_src_ip_tags, enrichments.custom_dest_ip_tags
Prevalenceprevalence_file_hash, prevalence_process_hash, prevalence_dest_domain, prevalence_dest_ip

See Enrichment field reference for every path and what fills it.

Sources

SourceWhat it addsOpen coreSelf-run
IPinfo LiteCountry, continent and autonomous system for public IPsIncluded (platform feed)Included (platform feed)
ThreatFoxMatches against abuse.ch malware IOCs (IPs, domains, URLs, hashes)Included (platform feed)Included (platform feed)
Tor exit nodesFlags IPs on the Tor Project's exit listIncluded (platform feed)Included (platform feed)
IOC listsYour own indicators (IP, CIDR, domain, hash, URL, email)Not availableYes
PrevalenceHow many hosts have seen an artifactYesYes
Custom enrichmentsYour own feed, written in TypeScript and run in a sandboxNot availableYes
Agent lookupsVirusTotal, AbuseIPDB, Shodan and others, on demand during AI investigationsNot availableYes, from Marketplace

Platform feeds

nano publishes one signed feed bundle that carries IPinfo Lite, ThreatFox and the Tor exit list. Every install fetches it from nano, verifies its signature, and loads it into ClickHouse; you don't need an IPinfo token or an abuse.ch key.

  • The jobs leader checks for a new bundle every hour (PLATFORM_FEEDS_POLL_SECS, minimum 300). Open core uses the open feed; a Self-run install with a license uses the licensed feed.
  • A bundle is installed all at once. A failed or refused check never removes the last good bundle; it keeps stamping.
  • A bundle older than 7 days is shown as stale but keeps stamping until it expires.
  • Air-gapped installs import the same .nanfeed file through the API. See Air-gapped.
Method and pathPermissionPurpose
GET /api/enrichment/platform-feedsenrichments:viewInstalled bundle, each feed's state, last check and error
POST /api/enrichment/platform-feeds/checkenrichments:configureCheck for a new bundle now
POST /api/enrichment/platform-feeds/importenrichments:configureImport a bundle file (air-gapped installs)
VariableDefaultMeaning
PLATFORM_FEEDS_AUTO_UPDATEtrueTurn the scheduled check off
PLATFORM_FEEDS_POLL_SECS3600Seconds between checks (minimum 300)
PLATFORM_FEEDS_URLAn HTTPS mirror of the feed metadata route, for installs that can't reach nano directly
PLATFORM_FEEDS_LICENSE_FILESelf-run: the signed license file used to fetch the licensed feed

The Marketplace page shows the bundle's state and each feed's last update.

IOC lists

Detections → IOC Lists (not in the open-source edition) holds your own indicators. Paste or upload indicators (CSV, JSON or text), review the per-type counts, then append to or replace a list and publish it.

LimitValue
Lists50
Indicators per list50,000
Indicators across all lists250,000
Upload file size8 MiB
Indicator typesIP, CIDR (up to 256 addresses), domain, hash, URL, email
Indicator length2,048 bytes
Tags per indicator16, each up to 64 bytes
Default risk score75

To view IOC lists you need enrichments:view; to create, edit or publish one you need enrichments:configure. Every change is audited (ioc_list_created, ioc_list_updated, ioc_list_deleted, ioc_list_published).

Publishing writes the list into ClickHouse's IOC store and reloads the custom IOC dictionary. Published indicators are then:

  • matched by ioc searches and retro hunts;
  • feed candidates for automatic retro-hunt rules, like any other IOC feed. A republish only surfaces indicators that weren't live before.

Indicators with an expiry stop matching once it passes.

Search enrichment data

src_endpoint.location.country=* | stats count by src_endpoint.location.country | sort -count | head 10
enrichments.ioc_dest_ip_threat_type=* | stats count by enrichments.ioc_dest_ip_threat_type, dst_endpoint.ip
prevalence_file_hash<3 | stats count by file.hashes.sha256, device.hostname
  • Detections can filter on enrichment fields like any other field.
  • Investigations: the event detail view shows the enrichment fields on each event.

Troubleshoot

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

If an expected enrichment is missing, check the platform feed state in Marketplace, then confirm that the event contains the field the feed reads and that ClickHouse has enough memory for the dictionaries. A match-based feed writes a value only when it finds a matching indicator.

What's next

On this page