nano SIEM
Releases

nano v2.0.13

Supported in:Self-hosted

nano v2.0.13 makes detections, entities, prevalence and AI prompts correct on OCSF, makes OCSF the default for new installs and adds SCIM 2.0 provisioning.

v2.0.13 includes everything in v2.0.12. It includes no security fixes.

To upgrade, follow Upgrade a self-hosted deployment. On Docker Compose, scripts/nano upgrade upgrades v2.0.10, v2.0.11 and v2.0.12 to v2.0.13 directly. Before you upgrade a single-server install, read the upgrade notes about .env sizing overrides.

New

  • SCIM 2.0 provisioning. Okta and Microsoft Entra ID can create, update, deactivate and delete nano users and sync their groups over SCIM. See SCIM provisioning.
  • OCSF is the default schema for new installs. A fresh Docker Compose install or a bare docker compose up with no NANO_SCHEMA_PROFILE uses OCSF. Existing installs keep their schema: the installer and scripts/nano upgrade write NANO_SCHEMA_PROFILE=udm into an .env that has no value, and the ClickHouse migrator refuses to start, naming the fix, if it finds a UDM install with the value unset. Helm already defaulted to OCSF.

Fixes and improvements

  • OCSF correctness.
    • Prevalence counts hosts from the host field that's correct for each OCSF class, so rarity is right on OCSF events.
    • SOAR playbooks, real-time rules and cases resolve entities by OCSF class, for example user.name on authentication events and actor.user.name on endpoint events.
    • Concept searches such as action=blocked, logons and authentication results match OCSF events.
    • pivt, the investigator and every AI prompt and built-in query use OCSF field paths.
    • The search Rarity view and POST /api/prevalence/query-artifacts read every OCSF artifact column. Known issue: on OCSF they return artifacts only for *. Any filtered query (a field such as class_uid=1007, or a keyword) returns nothing, because the filter is built for UDM fields and the error is answered as an empty result. Fixed in v2.0.15.
    • Hunt reconnaissance, the case audit mirror, cloud enrichment and playbook paths work on OCSF.
    • IOC and geo field buckets, the process tree and the result source label are correct on OCSF in the web app.
  • Rule editor. The validator checks fields against the rule's dataset. On OCSF it accepts OCSF fields and their aliases and suggests only OCSF fields, and the risk rule's score_24h query no longer reports an unknown field.
  • Risk rule renamed. The default risk rule is now accumulated_risk_threshold_exceeded. It's renamed only if it still has its original name. Everything that refers to it uses its ID, so nothing else changes.
  • Search commands.
    • | asset and | baseline accept OCSF entity fields such as device.hostname and user.name.
    • timechart … by <field> with more than 10 series no longer fails.
    • isnull() and isnotnull() treat an empty OCSF field as null.
    • | ai is bounded: a 90-second timeout (SEARCH_AI_PIPE_TIMEOUT_SECS), one call per user at a time, and four per search service. Rows always come back, marked SKIPPED or ERROR if the call doesn't finish. A search with | ai is no longer moved to a background job.
  • Web app. A page that fails to load shows an error panel with a Reload button and keeps the navigation, instead of a blank screen. After an upgrade, a tab running the old build reloads once by itself.
  • Docker Compose: scripts/nano upgrade. These fix the v2.0.12 known issues.
    • It renders each server's configuration again from the new bundle and your inventory, shows the difference in the dry run, and recreates every service whose configuration changed, including the ingest proxy. Rollback restores the earlier configuration.
    • The nginx edges look up container addresses at request time, so an app server reboot no longer leaves the ingest servers marking it DOWN. scripts/nano cluster-health has an edge:internal row.
    • The SIEM Health check waits for a report made after the upgrade (NANO_UPGRADE_SIEM_HEALTH_WAIT_SECONDS, default 600).
    • The drain and rejoin hooks use the new nano-lb-haproxy forced-command wrapper and confirm HAProxy's state. The dry run runs a real drain and rejoin on every server the upgrade drains, one at a time.
    • It prints each step as it happens, also over ssh without a terminal.
    • A log source deploy that's still installing reports pending, not a failure.
  • Docker Compose: installer. install.sh no longer moves or drops .env overrides you set below its sizing block. See Upgrade notes.
  • Helm. helm upgrade with --reuse-values or --reset-then-reuse-values now gets the new release's images: the chart pins its own images and the ClickHouse operator digest. --reuse-values still ignores new defaults, so pass your -f files. See Kubernetes: Upgrades.
  • Removed: Sigma conversion. POST /api/sigma/convert and Sigma-format rule repositories are gone; converted rules targeted UDM fields and never matched on OCSF. An existing Sigma repository stays listed and can be deleted, but its sync and import return 400.
  • Open edition. The public nano-rs/nano repository no longer contains source for modules that aren't in the open-source edition.
  • Documentation. Updated SCIM, Kubernetes on AWS, high-availability and upgrade guides.

Upgrade notes

  • Docker Compose: check your .env sizing overrides. If you set sizing overrides below the installer's sizing block in .env, v2.0.11 or v2.0.12 may have moved them into the block. Check your .env overrides before rerunning install.sh.

    • On a single-server install, rerunning install.sh on v2.0.11 or v2.0.12 could drop an override placed below the block.
    • scripts/nano upgrade to v2.0.11 or v2.0.12 moved such an override into the block, where the next installer run overwrote it.
    • Role-split clusters (several servers) are not affected.

    Open .env, compare the values in the # BEGIN NANO block with the ones you meant to pin, and put any you want to keep below the block again, as Sizing details and overrides describes. From v2.0.13 the installer and scripts/nano upgrade leave overrides below the block alone.

  • Sigma repositories. If you imported rules from a Sigma-format repository, its sync stops with Sigma-format repositories are no longer supported. Rules already imported stay as they are.

  • Risk rule name. If a search, dashboard or script refers to the default risk rule by its old name, Accumulated risk threshold exceeded, change it to accumulated_risk_threshold_exceeded.

On this page