> 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/siem/crowdstrike-nextgen-siem-integration-qux.md).

# Crowdstrike Next-Gen SIEM integration (QUX)

Send Vectra Detect (QUX) logs to CrowdStrike NextGen-SIEM via a log collector and HEC, using the provided parser and setup guide.

Integrating **Vectra Detect** data with **CrowdStrike NextGen-SIEM** enables seamless threat detection and enhanced security visibility. This guide outlines the steps required to configure and direct Vectra’s log output to CrowdStrike’s NG-SIEM platform. By leveraging syslog output directed through a log collector (such as Humio), the data is transmitted to CrowdStrike’s NextGen-SIEM using the HEC (HTTP Event Collector) data connector. A custom parser within NG-SIEM processes this data, ensuring that it is accurately parsed and stored in CrowdStrike’s NextGen-SIEM environment. This setup allows security teams to monitor Vectra alerts and events within the broader CrowdStrike ecosystem, supporting improved threat correlation and streamlined incident response.

### Attachments

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

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


---

# 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/siem/crowdstrike-nextgen-siem-integration-qux.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.
