> For the complete documentation index, see [llms.txt](https://docs.octoxlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octoxlabs.com/release-notes/previous-releases/octoxlabs-5.x/release-notes-v5.6.7.md).

# Release Notes - v5.6.7

We are pleased to announce release of **version 5.6.7.** This update introduces several new integration,
 update on several integrations and several resolved issues. Below is a structured summary of the key
 improvements delivered in this version.

### New Adapters

* BlackBerry Unified Endpoin Management
* Microsoft Enterprise Applications

### Minor Features

* Update on following adapters:
  * **Symantec Cloud Secure Web Gateway**
  * **MYQ**
  * **Azure Entra** - Sign In Activity
* Update on Service Inventory for more data fetch

### Resolved Issues

* Fix **empty description field** issue on **Palo Alto Pan-OS**
* Fix 401 issue on **Openstack** adapter
* Fix **host\_start key** issue on **Nessus** adapter
* Fix **host\_idendtity\_detail is Null** issue on **VMware vCenter** adapter


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.octoxlabs.com/release-notes/previous-releases/octoxlabs-5.x/release-notes-v5.6.7.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.