> 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/configuration/response/soar/palo-alto-xsoar-integration-rux.md).

# Palo Alto XSOAR integration (RUX)

Configure Palo Alto XSOAR for RUX deployments, including content pack details and UX-specific implementation notes.

{% hint style="info" %}
**Please Note:**

This article is ONLY for customers using Vectra's Respond UX (RUX) with XSOAR. While similar, there are some differences in the implementation for customers using the Quadrant UX. If you are unsure which UX you are using, please see: [Analyst UX options (RUX vs QUX)](https://docs.vectra.ai/deployment/getting-started/analyst-ux-options-rux-vs-qux.md) **.**

If you are configuring XSOAR for the Quadrant UX, please see [Palo Alto XSOAR integration (QUX)](https://docs.vectra.ai/configuration/response/soar/palo-alto-xsoar-integration-qux.md) instead.
{% endhint %}

## New Version Available

**November 2025 - Content Pack version 1.2.0**

The following documentation pertains to the Vectra integration for Palo Alto XSOAR content pack version 1.2.0.

## Contains

* Introduction\
  \- Document and Release Information
* Terminology
* Architecture
* Implementation\
  \- Vectra Pre-requisites\
  \- XSOAR Pre-requisites\
  \- Downloading and Installing the App\
  \- Implementation Checklist\
  \- Initial Configuration of New Asset
* Operational Components\
  \- Incidents\
  \- Incident Template\
  \- Incident Info\
  \- Entity Detections\
  \- War Room\
  \- Work Plan\
  \- Remaining Tabs\
  \- Context Data\
  \- Indicators\
  \- Actions\
  \- Playbooks
* Operations\
  \- Incident Creation Philosophy\
  \- Incident Priority\
  \- Investigate\
  \- Detections\
  \- War Room\
  \- Work Plan\
  \- Sync Assignment\
  \- Basic Workflow\
  \- Intermediate Workflow\
  \- Running Actions - General\
  \- Running Actions - Resolve Assignment
* Working with Playbooks
* Known Limitations
* Troubleshooting
* Worldwide Support Contact Information

### Attachments

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


---

# 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/configuration/response/soar/palo-alto-xsoar-integration-rux.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.
