nano SIEM
Releases

nano v2.0.15

Supported in:Self-hosted

nano v2.0.15 runs custom enrichments and collectors in a WebAssembly sandbox, makes an ingest 2xx mean synced to disk and speeds up PostgreSQL HA failover.

v2.0.15 includes everything in v2.0.13. It is not flagged as a security release.

v2.0.14 was not released. Its build was tagged, but the release step stopped before the bundle was published. v2.0.15 is the same code plus a fix to the release tooling. Upgrade from v2.0.13 straight to v2.0.15.

To upgrade, follow Upgrade a self-hosted deployment. On Docker Compose, scripts/nano upgrade upgrades v2.0.13 to v2.0.15 directly. v2.0.10, v2.0.11 and v2.0.12 also upgrade directly; there are no required stops. Before you upgrade, read the upgrade notes about enrichments and collectors.

New

  • Custom enrichments and collectors run in a WebAssembly sandbox. Deno is removed from the images. Code runs in nano's built-in wasm sandbox instead.
    • Secrets stay outside the code. nano puts a credential only into a request header sent to an allowed domain.
    • Network access goes through an allowlisted broker: https on port 443, to the allowed domains only.
    • nano checks each enrichment and collector when it's saved and after the upgrade. Code that can't run in the sandbox is marked needs attention and doesn't run. Settings → SIEM health lists it, and the Marketplace drawer shows the reason. See Needs attention.
    • The official Shodan lookup now installs as a built-in threat-intel provider, not as code. It resolves IP addresses only.
    • AI code generation and the editor target the sandbox.
  • OCSF sample gate for log sources. On OCSF, publishing a changed parser, or the first deploy of a new source, needs sample events that pass the OCSF 1.9 contract.
    • The samples can come with the request, from a passing test-lab run of that exact parser, or from a first-party parser's bundled samples.
    • Going back to an earlier published version needs no samples.
    • Existing sources aren't affected until their parser changes.
    • A first go-live can be acknowledged as untested. nano audits it, and the next parser change needs a passing sample.
    • The test lab shows OCSF errors by field path, and the source shows whether its parser is attested.
  • Log-source deploys run as background jobs. Deploy, undeploy, publish and deploy-all run as jobs. The web app shows their progress and final state. A deploy no longer stops halfway when the browser or a proxy times out.

Fixes and improvements

  • Ingest durability. A 2xx from HEC, HTTP or OTLP now means the event is synced to disk on the ingest server. It survives a power loss or a hard reset of that server. Before, the disk buffer synced every 500 ms, so an event answered just before a crash could be lost. This ships in Vector 0.61.0-nano.10. See High availability.
  • Stable fan-in. Adding a log source no longer rebuilds the shared fan-ins or the OCSF sink. A deploy rewrites only the parser files that changed, so the Vector reload is shorter.
  • Log-source deploys on several hosts. Ingest servers reload one at a time. Each one leaves the load balancer, reloads and rejoins before the next starts. Ingest no longer stalls on every server at once.
  • PostgreSQL HA (Docker Compose). Failover after losing the primary's server is faster: about 19 s instead of 23 s in our drills.
    • etcd leadership stays off the primary's server.
    • The router marks a promoted primary up after one 500 ms check.
    • Each Patroni member lists its own etcd first.
    • With three Keeper servers that aren't the postgres servers, etcd and Sentinel run on the Keeper servers. See High availability.
  • Valkey 9.1.3. Every Compose file and the Helm chart pin Valkey 9.1.3, an upstream security release. A check stops a Dragonfly image from coming back.
  • Helm.
    • Ingest rollouts no longer drop requests. New ingest.rollout values set minReadySeconds, preStop delays and Vector maxUnavailable: 0. They also apply with --reuse-values. See Kubernetes: Upgrades.
    • On GKE, gateway.gke.healthCheck sets the health-check timing. The chart refuses an edge preStop shorter than the load balancer's detection time.
    • Online license mode: GET /api/license returns mode: online for a license checked in online. It used to return hosted, which read as a nano-hosted install.
  • Upgrade fixes (Docker Compose).
    • The dry run has a backup-output row on every postgres and ClickHouse server and on the first app server. It fails, with the command to fix it, where the backup folder can't be created.
    • The dry run prints each phase as it runs.
    • .env keys are set on the line where they already are, so NANO_VERSION stays on line 1.
    • Each drain and rejoin hook call is journaled as an lb_hook event.
  • Rarity on OCSF. The search Rarity view and POST /api/prevalence/query-artifacts filter the way search does on OCSF. A field filter such as class_uid=1007 or a keyword now returns artifacts. A query that can't run answers 400 with the reason, and a failed read answers 500 or 504, never an empty result. This fixes the v2.0.13 known issue.
  • Rarity warming. On a fresh install, the Rarity label says when the 30-day window will be fully covered. A kind with no events, such as no DNS or proxy logs, stays unknown.
  • New ingest tokens. A new token can get 401 for a few seconds. The create response says so (active_within_secs), and the ingest edge adds a retry hint to the 401.
  • OCSF search. A piped | search "keyword" on OCSF works. Showing action adds a note: on OCSF it's the activity; use disposition for blocked or allowed.
  • Install token. Disabling the install token also stops Vector config delivery to forwarders that still use it.

Upgrade notes

  • Enrichments and collectors that need attention. After the upgrade, nano checks every custom enrichment and collector. One that used Deno-only features is marked needs attention and doesn't run. Settings → SIEM health lists it with the reason. Common reasons are a plain http:// URL, a port other than 443, or a credential in a URL or body. Update the code, and it runs again. See Needs attention.
  • An incompatible collector stays enabled. It isn't turned off. Each run fails with its reason until you fix the code. Fix it, or disable it to stop the failed runs.
  • Shodan. An installed Shodan enrichment that ran on Deno needs attention. Uninstall it and install Shodan again from the Marketplace. It then runs as the built-in threat-intel provider. It resolves IP addresses only, not domains.
  • License mode. If a script reads mode from GET /api/license, accept online as well as hosted.

On this page