Skip to main content

Upgrading to 1.27.0

Released 2026-11-01. Everything in the release: changelog. How to upgrade: Upgrade.

What's new​

  • Live detection, off until you turn it on. Between scans, the agent watches its machine, its containers and Kubernetes nodes as attacks happen: programs started from temporary folders or memory, shells started by web servers and databases, crypto miners, downloaded scripts piped into a shell, and changes to accounts, sudo rules, SSH keys, scheduled jobs and services. Alerts arrive within seconds on each host's new Runtime tab. See Live detection.
  • Runtime alerts and Live detection stopped notifications, for the channels that tick them.

Before you upgrade​

Back up: database schema 32. Hosts get live detection's settings, status and alerts, so 1.26 and earlier can't open the database afterwards. Back up first.

After you upgrade​

Nothing changes until you turn live detection on: it's off for every host, existing and new, and a host with it off loads nothing into its kernel.

To use it:

  1. Upgrade the agents to 1.27.0. Older agents show Agent too old in the Hosts list's new Live detection column; the Agents page lists the agents to upgrade.
  2. Turn it on: for one host, Turn on live detection on its Runtime tab; for every host, and for new ones as they enroll, under Settings → Live detection (admins).
  3. Check it runs: the dashboard's Live detection card says how many hosts are watched. On a host's Runtime tab, Send a test alert proves the whole chain within about 20 seconds.
  4. To be told about alerts, and when detection stops, tick Runtime alerts and Live detection stopped on a notification channel.

Kubernetes (Helm and Kustomize)​

The node agent needs two more capabilities, BPF and PERFMON, which the 1.27.0 chart and Kustomize base add: upgrade them as on Upgrade, as well as the image. A node agent upgraded without them runs and scans as before; if live detection is turned on for it, it shows Not supported, saying it isn't allowed to load programs into the kernel. If you keep your own copy of the DaemonSet, add BPF and PERFMON to its capabilities.add. The cluster agent doesn't need them: it doesn't watch a machine.

Install script and packages​

Nothing else to do: the agent runs as root.

Docker Compose​

If you run the Compose file's agent (--profile agent), use the 1.27.0 Compose file, whose agent has the BPF and PERFMON capabilities.

Known issues​

  • Alerts name the program but not yet its container or pod.
  • An agent watches the kernel it runs on: two agents on one machine, such as one installed with the install script and one in a container, each report the same events.