> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/changelog/releases/2026-07-09.md).

# 8.9.0 — 9 July 2026

What changed in Dispel in the release of 9 July 2026.

**Dispel Zero Trust Engine 8.9.0**, including Orchestrator 1.17.0.

{% hint style="info" %}
[**Customer Impact Score: 2**](https://legal.dispel.com/support/maintenance-windows#customer-impact-scores) — visible changes and new features, without a substantial change to the workflows most people use.
{% endhint %}

## New features and improvements

* An organization can upload its own trusted CA bundle for [Browser Connect](https://docs.dispel.com/integrate-and-administer/settings/browser-connect). The certificates are validated when you add them and are injected into the session, so an HTTPS device signed by your own authority opens cleanly. (DIS-21926, DIS-21855)
* Dispel reads asset inventory from [Claroty xDome](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/claroty-xdome). (DIS-21945)
* Dispel reads asset inventory from [Tenable OT Security](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/tenable) and [Darktrace](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/darktrace), with the vendor's own device detail carried onto the device. (DIS-21614, DIS-21623)
* A device set up for Browser Connect can be given its own screen resolution. (DIS-21557)
* A recording you cannot open now says which facility permission it needs. (DIS-20565)
* Session Forensics reads the authentication factors your identity provider reports and scores the session on what actually happened, rather than assuming. (DIS-20766)
* Adding devices to a facility has a search box in place of the dropdown. (DIS-20904)
* [Topology](https://docs.dispel.com/monitor-and-investigate/topology)'s tree view draws large trees faster: only what is on screen is rendered, and the animation eases off once the tree is big. (DIS-21591)

## Bug fixes

* Signing in through SSO could hang on **Authenticating SSO**. (DIS-21711)
* Session Forensics could report a sign-in that used MFA as having used none, could show the wrong provider for an SSO session, and might not attach a session to an organization the user switched into. (DIS-21807, DIS-21725, DIS-21716, DIS-21752)
* The access request page could fail to render, or fail silently after a request was submitted. (DIS-21592, DIS-21693, DIS-22116)
* Scrubbing a recording past its end left it unable to play again, and the timeline could break at the end of the recording. (DIS-21428, DIS-20264, DIS-20020)
* Playback speed and full screen did not affect the recording playing. (DIS-21805)
* A device could refuse to be deleted while sessions still referenced it. (DIS-19180)
* Opening a session or a recording in an external window could break the layout, and the recording could show a placeholder instead of the player. (DIS-21333)
* **General bug and security fixes** across access rule propagation, the members and device pages, the organization message banner, virtual desktop reservations, recording windows and indicators, and Topology's tree.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/changelog/releases/2026-07-09.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.