> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/release-notes/quadrant-ux-qux/archived-qux-release-notes/vectra-cognito-62-release-notes.md).

# v6.2 Release Notes (QUX)

Cognito^(®) Version 6.2 includes the following features and enhancements as well as a few bug fixes:

* Link Network & O365 Accounts into a Unified View
* SAML 2.0-based Single Sign-On to Detect UI
* Executive Report: What’s on my Network?
  * Device Inventory by Mac Vendor
  * Endpoint Coverage
  * High Privilege Entities
* New Info detections:
  * New Host Role
  * Novel Admin Protocol Usage
* Six new alerts for Detect for O365
* Download the O365 logs that fired the detection
* Disable Anonymization in Detect for O365
* CrowdStrike EU Cloud and US Commercial Cloud 2 support
* New Cognito Recall Saved Searches
* User configured static hosts
* Additional syslog format support for Windows event log ingestion
* Share link maximum duration increased to 30 days

Click below to download the release notes for Cognito^(®) Version 6.2.

### Attachments

{% file src="/files/alEXUmwILfJDMtXFppQu" %}


---

# 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.vectra.ai/release-notes/quadrant-ux-qux/archived-qux-release-notes/vectra-cognito-62-release-notes.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.