> 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/google-secops-soar-integration-qux.md).

# Google SecOps SOAR integration (QUX)

This integration implements the investigative and generic actions, connector and job for the Vectra QUX app on the Chronicle SOAR Platform. It will allow end-users to implement any use cases on the Vectra Cloud Platform that are possible using a combination of the below-mentioned actions.

**Actions:**

* Test Connectivity(ping): Tests the connectivity of the Chronicle SOAR server to Vectra.
* Search Hosts: List hosts based on query parameters.
* Search Accounts: List accounts based on query parameters.
* Search Detections: List detections based on query parameters.
* Mark Entity Fixed: Mark the given detections as fixed.
* Mark Detection Fixed: Mark detections as fixed for provided IDs
* Unmark Detection Fixed: Unmark the given detections as fixed.
* Describe Entity: Show all the details of an entity for the given ID.
* Describe Detection: Show all the details of a detection for the given ID.
* Add Tags: Add tags to the given entity IDs
* Remove Tags: Remove tags from the given entity ID.
* Add Note: Add a note to the given entity ID
* Remove Note: Remove a note from the given entity ID.
* List Entity Detections: List all the detections for the given entity ID
* Assign Entity: Assign an entity to the given user ID.
* Update Assignment: Updates the assigned user in the assignment for the given entity.
* Remove Assignment: Remove the assignment for the given entity ID.
* Download PCAP: Download the PCAP file for the given detection ID.
* List Assignments: List all the assignments based on the query see parameters.
* Describe Assignment: Show all the details of an assignment for the given ID.
* Resolve Assignment: Resolve assignment based on the given assignment ID and outcome ID.
* List Outcomes : List all the assignment outcomes.
* Add Outcome : Add outcome with title and category.
* List Users: List users based on the query parameters.
* List Groups: List groups based on the query parameters.
* Assign Group: Add members to the given group ID.
* Remove Group: Remove members from the given group ID.

**Connector**

* Vectra QUX - Entities Connector: Pull entities and their detections from the Vectra QUX platform and create a case in Chronicle SOAR.

**Job**

* Vectra QUX - Clear Empty Cases Job: Close the Chronicle case if the detection is attached to a different entity or no detections remain.

**Playbooks**

* Vectra QUX – Process Case Playbook: Assigns a Vectra user to the entity in Vectra and adds a note to link to the Google SecOps Case.
* Vectra QUX – Resolve Case Playbook: Resolves the entity in Vectra with reasoning and closes the case in Google SecOps.

### Attachments

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


---

# 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/configuration/response/soar/google-secops-soar-integration-qux.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.