nano SIEM
Releases

nano v2.0.6

Supported in:Self-hosted

nano v2.0.6: security fixes, a CrowdStrike FDR pull source, scheduled automatic backups and an ingest durability fix. All Self-run installs should upgrade.

v2.0.6 includes everything in v2.0.5.

To upgrade, follow Upgrade a self-hosted deployment.

Security

nano now refuses the published default Vector install token, the value nano once shipped as a default or example (for example nanosiem-default-token). nano's ingest and Vector config delivery no longer accept it. This can break insecure setups: see Upgrade notes. We don't publish exploit details. To report a vulnerability, see Support.

Highlights

  • CrowdStrike FDR. Pull CrowdStrike Falcon Data Replicator events into nano as a pull source. See CrowdStrike FDR.
  • Scheduled backups. The installer can set up automatic backups once, to a mounted path or an S3-compatible bucket (AWS S3, Wasabi, RustFS and others). Backups run daily by default and keep the last 7. See Back up.
  • Durable ingest acknowledgements. Vector now acknowledges events only after they are written to its disk buffer, so an acknowledged event survives the loss of an ingest node.
  • SOAR license. Self-run installs now use their installed license automatically for the SOAR catalog and licensed content. When no license is available, the SOAR page says why. See Playbooks.
  • PostgreSQL over TLS. Services no longer fail to start when PostgreSQL requires TLS with sslmode=verify-ca or verify-full, for example managed PostgreSQL on AWS RDS, Cloud SQL or Azure. verify-ca no longer rejects a certificate that doesn't name the connection host.

Upgrade notes

  • The default install token is refused. Upgrading replaces a publicly known VECTOR_AUTH_TOKEN in .env with a generated value before the services start. Senders using ingest tokens keep working. Any sender still sending the public default token gets HTTP 401: give it its own ingest token. A private install token is not changed.
  • Several servers. On a cluster of several servers, nano upgrade stops before changing anything while .env still holds the public default token. On nano-1, replace the VECTOR_AUTH_TOKEN line in .env with a generated value (openssl rand -hex 32), or run NANO_PREPARE_ONLY=1 ./install.sh from the v2.0.6 bundle. Copy .env to every server, then upgrade. See High availability.
  • Strict config delivery on clusters. On an upgraded cluster, the upgrade sets NANO_VECTOR_CONFIG_DELIVERY_STRICT=false in .env if it isn't set, so an ingest server whose .env predates NANO_VECTOR_CONFIG_DELIVERY_TOKEN keeps receiving its configuration. Once every server has the current .env, set it to true on nano-1 and restart. Strict delivery refuses the install token for configuration delivery. New installs and the Helm chart use strict delivery already.
  • Migrations are forward-only and run before the new services start.
  • Upgrade with install.sh, as described in Upgrade a self-hosted deployment.

On this page