> 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/operations/detection-specific-guidance/data-gathering-detected-between-brain-and-sensor.md).

# Data Gathering - detected between Brain and Sensor

Vectra detected data gathering between the brain and the sensor, triggering an alert.

#### **Problem**

#### Vectra detected data gathering between the brain and the sensor communication during the upgrade process and triggering an alert as "Data gathering: Exfiltration".

#### **Root Cause**

The exchange of information between the brain and the sensor is a standard procedure during updates. However, as per the product design and transparency, we let customers understand fully what's going on in their network (even if it's our own product) and make informed decisions about how to handle that. If the customer does not want to trigger the detection, we request customer to create a triage filter that would normally prevent such alerts during the upgrade process.

#### **Solution**

We need to create a Triage Filter for Brain and Sensor communication. For that:

* Login to the Vectra portal
* Navigate to detection where you found the Vectra Sensor and the Brain communication is identified as "Data gathering"
* Select the detection > Triage
* Create a filter to exclude brain/sensor or sensor/sensor communication during updates.

Below KB may help you to create a "Triage Filter"

[https://support.vectra.ai/vectra/article/KB-VS-2681](/configuration/tuning/triage-best-practices.md)


---

# 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/operations/detection-specific-guidance/data-gathering-detected-between-brain-and-sensor.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.
