Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

8.4.0 — 29 April 2026

What changed in Dispel in the release of 29 April 2026.

Dispel Zero Trust Engine 8.4.0, including Orchestrator 1.11.0.

Customer Impact Score: 2 — visible changes and new features, without a substantial change to the workflows most people use.

New features and improvements

  • Compliance is a section of its own. Dispel holds the framework as a catalog of controls, evaluates each one against what the system records, and shows the result per control. NIS2 (Implementing Regulation EU 2024/2690) is included. (DIS-18653, DIS-19930)

  • Billing has a page of its own, showing your plan and what you are using against it. (DIS-19438, DIS-19439)

  • The Browser Connect utilization report filters by facility and by date range, and lists the recordings for the period. (DIS-19658)

  • Users and virtual desktop users can upload and download files on a device they have access to, and a facility can set how long a transferred file is kept. (DIS-19752, DIS-19755)

  • File transfers in progress moved from a floating widget into stacked picture-in-picture panels that sit alongside a session. (DIS-19835, DIS-19995)

  • Hovering the Participants column on the Active Connections table shows who is actually in the session. (DIS-19843)

  • The session timer reads in a clearer format, and the maximum session age can be configured. (DIS-19638)

  • A third-party system can call the Dispel API with OIDC client credentials, which is how the ServiceNow integration authenticates. (DIS-19006)

Bug fixes

  • Administrators and custodians at the destination facility could not see or approve a file transfer addressed to them. (DIS-17741)

  • Downloading a file transfer from the logs could fail. (DIS-19654)

  • A permissions report could be truncated when the dataset was large. (DIS-19031)

  • New stacks using on-demand virtual desktops could intermittently fail to build. (DIS-17802)

  • A popped-out Browser Connect session could stay on "Reconnecting…". (DIS-19285)

  • An integration that failed to sync or connect did not say why. (DIS-19632)

  • Accepting the terms during OIDC onboarding could loop. (DIS-20021)

  • General bug and security fixes across permission handling, session termination and notifications, the Active Connections table, Topology's list view and side panels, integration site mapping, Session Forensics scoring, the devices tab, and file transfer scanning.

Last updated

Was this helpful?