> 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/respond-ux-rux-1/archived-rux-release-notes/2025-release-notes-rux/march-2025-release-notes.md).

# Mar 2025 Release Notes (RUX)

### The Respond UX March release (2025.03) includes:

**Enriching AI Prioritization Context**

Vectra now surfaces tailored attack profiles when detections span multiple attack surfaces, helping to identify complex threats with greater clarity. Two new profile types have been introduced:

* Hybrid Network Adversary: Indicates an attacker active in both network identity and cloud identity environments, suggesting coordinated activity across on-premises and cloud infrastructure.
* Multi-Cloud Service Adversary: Represents an attacker operating across multiple cloud-based services—such as identity providers, SaaS platforms, or public cloud environments—without direct engagement with network identity systems.

These profiles are designed to reflect the nature of hybrid threats and enhance threat context in the UI.

**Support AI Triage for Azure Detections**

Vectra is enhancing support for Azure detections by enabling AI Triage for Azure CDR (Cloud Detection and Response) alerts. For each existing Azure detection type, we are evaluating and applying appropriate AI distillation algorithms, defining relevant context fields, and addressing any specific handling requirements. This will help surface high-fidelity insights more efficiently and improve detection clarity within the platform.


---

# 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.vectra.ai/release-notes/respond-ux-rux-1/archived-rux-release-notes/2025-release-notes-rux/march-2025-release-notes.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.