nano SIEM
Settings

Rarity thresholds

Supported in:Self-hosted

Configure prevalence tracking: the host-count rarity threshold, which artifact types are tracked, and how long prevalence data is kept.

Use Settings → Rarity Thresholds (/settings/prevalence) to configure how nano tracks artifact prevalence. nano counts distinct hosts for each file hash, domain, and IP address and marks an artifact as rare when its host count is below the threshold.

Detections, the prevalence search command, and investigations use these counts.

Changing these settings requires prevalence:configure.

Settings

SettingFieldDefaultRangeEffect
Host count thresholdrarity_threshold31–1,000An artifact seen on fewer hosts than this is rare. Raise it for larger fleets.
Hash trackingenable_hash_trackingOnTrack MD5 and SHA-256 file hashes.
Domain trackingenable_domain_trackingOnTrack domains and subdomains.
IP address trackingenable_ip_trackingOnTrack source and destination IP addresses.
Data retention periodretention_days90 days1–365Prevalence aggregates older than this are dropped.
Cache TTLcache_ttl_seconds60 s0–3,600How long prevalence lookups are cached. 0 turns caching off.

Turning off a tracking type stops new aggregation for that type.

Choosing a threshold:

  • Fewer than 100 hosts: 2–3
  • 100–1,000 hosts: 3–5
  • More than 1,000 hosts: 5–10

If too many common artifacts are flagged as rare, raise the threshold. If a rare-binary detection never fires, check that hash tracking is on and that your endpoint sources populate file hashes (file.hashes.value).

API

curl -X PUT https://<host>/api/settings/prevalence \
  -H "X-API-Key: $NANO_API_KEY" -H "Content-Type: application/json" \
  -d '{"rarity_threshold": 5, "enable_hash_tracking": true, "enable_domain_tracking": true,
       "enable_ip_tracking": true, "retention_days": 60, "cache_ttl_seconds": 120}'

GET /api/settings/prevalence returns the current values.

Troubleshoot

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

A rare-binary detection does not match

Check that hash tracking is enabled and that the endpoint source populates file.hashes.value.

What's next

On this page