Skip to content

v2.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 12 Nov 14:24
v2.2.0
7192f99

Straza 2.2.0 lets an AI agent call an MCP server as its own Microsoft Entra agent identity, fixes enrollment and sign-in through Entra, lets the console write rules for MCP servers on people's own machines and for harness tools that Straza does not classify, and closes several security gaps. strazad migrates its database, so back up the store first.

New

  • An AI agent can call an MCP server that trusts Microsoft Entra as its own Entra agent identity, without holding an Entra credential.
  • The console's Settings has an Agent signing keys tab that rotates the client assertion key in the order Entra needs.
  • The console writes rules for MCP servers on people's own machines and for harness tools that Straza does not classify.
  • Entra's SCIM provisioning sets an agent's Entra agent identity, and an agent's SCIM manager becomes its sponsor.
  • The audit record of every harness tool keeps the tool's input.

Security

  • The classifier denies a command substitution that downloads or decodes text and runs it as code.
  • The admin API refuses a field the route does not take, so a misspelled expiresIn no longer mints a token that never expires.
  • Allowing an MCP server on a person's own machine raises a risk, and an approval of a harness tool that Straza does not classify is bound to its arguments.
  • Built with Go 1.26.11, which fixes GO-2026-6859 in net/http.

Fixed

  • Enrollment and sign-in through Microsoft Entra work, also for people whom Entra's SCIM provisioning created.
  • Entra's SCIM updates of a user's manager no longer fail.
  • The console's Audit screen no longer uses a full processor core or raises a false "Audit chain broken" alert.
  • Policy simulate runs the classifier, so it answers what the hook answers.

Before you upgrade

Follow Upgrade from 2.1.0 to 2.2.0 in its order. In short:

  • Back up the store. To go back to 2.1.0, first run strazad migrate --to 41 with the 2.2.0 binary.
  • Upgrade strazad before strazactl, and install the straza client of this version on machines that enroll through Entra.
  • Check your admin API scripts and every policy that uses interpreters or mode: classify.
  • Tool inputs now reach audit sinks unmasked. Read the upgrade notes in the changelog for how to keep them out of a sink, and for key rotation and entraBlueprint.

Which file do I need

Each archive (.tar.gz, .zip) holds all three programs: strazad, the server, also for a standalone install on one host; strazactl, the admin CLI; and straza, the client. Each package holds only the client and installs its background service: .deb or .rpm on Linux, .msi on Windows, .pkg on macOS. On Docker or Kubernetes, run the server from ghcr.io/strazahq/straza:2.2.0 or the Helm chart.

Install and verify

Verify your download with Download a release and verify it: checksums.txt is signed with cosign, and every file below, the packages included, has its line in it. The image is ghcr.io/strazahq/straza:2.2.0, and the Helm chart is 2.2.0.

The changelog lists every change of this release, with the upgrade notes.