> 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/deployment/getting-started/respond-ux-deployment/global-groups-and-triage-filters.md).

# Global groups and triage filters

Create, synchronize, and manage global groups and triage filters.

## Introduction

[Global View](https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment/global-view.md) is a feature that enables a unified view in an anchor instance of prioritized host and account entities from configured child instances.

Global groups and global triage filters can be created in the anchor instance. The groups and filters will be synchronized to the child instances. Because the anchor instance only reads data from configured child instances, not all group types can be configured in the anchor instance.

### Group Types Supported

Global groups can be configured from the following types

* IP Groups
* Domain Groups
* Dynamic Groups (Regex) - both host and account dynamic groups can be created

### Unsupported Group Types

The following groups types are not supported for the global groups feature:

* Active Directory (AD) groups
* Static host or account groups

## Applicability and Requirements

You must have at least two Respond UX instances if you want to use Global View.

* Quadrant UX (QUX) deployments are NOT supported.
* If you are unsure of your deployment type, please see [Vectra Analyst User Experiences (Respond vs Quadrant)](https://docs.vectra.ai/deployment/getting-started/analyst-ux-options-rux-vs-qux.md).

You must request a Global View anchor instance or already have one.

* For additional onboarding details please see [Global View](https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment/global-view.md#onboarding-deployment) in the main Global View article.

You **must** be a **Super Admin** in the Global View anchor instance to be able to create and manage global groups and triage filters.

## Creating Global Groups

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

Global groups can only be configured and managed in the anchor instance that houses the Global View for your RUX deployment. In child instances, the global groups created in the anchor instance will be in a read only state once synchronized.
{% endhint %}

{% stepper %}
{% step %}

#### Start Group Creation

In your Global View anchor instance, navigate to *Configuration → Global Groups.*

You will see a list of any existing global groups which can be filtered with choices made at the top of the screen.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FNXQP96nfoj3oBSmxrpLq%2Fimage.png?alt=media&amp;token=059c1e28-0997-4230-b805-e137d81926a0" alt=""><figcaption></figcaption></figure>

Click **Create Global Group.**
{% endstep %}

{% step %}

#### Create the Global Group

Give your global group a name, type, importance, and description.

Types can be: Host (Regex), Account (Regex), IP, or Domain.

Choose to **Apply to all Vectra Instances** or specific **Vectra Instances**

* By default, the box will be checked to **Apply to all Vectra Instances**, and the group will be synchronized to all existing and any future child instances.
* If you want the group to only apply to specific child instances, uncheck the box and choose specific instances for the group to apply to by clicking on them in the dropdown.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2Ftj1Ly2C701meQiBENaMM%2Fimage.png?alt=media&amp;token=24bed603-230b-43ee-ab0a-5b50ade05988" alt="" width="375"><figcaption></figcaption></figure>

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

When creating global triage filters, you must similarly choose which instances the triage filter will apply to. If the global group used in the triage filter does not exist on any of the child instances that are associated with the global triage filter, the filter creation dialog will give an error message.

It is recommended to apply groups to all instances unless there is a specific requirement to not synchronize a global group to some child instances.
{% endhint %}
{% endstep %}

{% step %}

#### Add Group Members

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

Depending on the group type selected in step 2, you will either continue to add group members as the next step, or you will need to find the group you just created, click on it, and add members. Vectra is working to update this in the future so that all group types will behave the same way and you will be led directly to member addition.
{% endhint %}

After adding your group members, **Create** the group.

**Supported Global Group Types:**

* **IP Groups** - Add individual IPs or ranges (in standard CIDR format).
* **Domain Groups** - Add individual domains or subdomains.
  * You can use a `*` to represent anything.
  * For example, a domain group for the cloud storage service “Box” might include members such as `*.box.com`, `*.box.net` , and `*.boxcloud.com` .
* **Dynamic (Regex) Groups** - For details on dynamic groups, please see the [Dynamic groups](https://docs.vectra.ai/configuration/tuning/dynamic-groups.md) article.

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

For Dynamic (Regex) global groups, previewing members for a give regex is not support since the anchor instance doesn't store the host or account objects that the child instances will eventually match against.

It is recommended that you test a regex using the preview capability in the dynamic group creation process in child instances and then save it as a global dynamic group in the anchor instance.
{% endhint %}
{% endstep %}

{% step %}

#### Wait for Synchronization

After you have created a global group, it must be synchronized to the child instances it was scoped to before it can be used in global triage filters.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FN2Sj6hpCYiPAnuRGgpcW%2Fimage.png?alt=media&amp;token=0110dd87-90e9-42c8-8942-3f7394df0ec5" alt=""><figcaption></figcaption></figure>

Global groups can have the following statuses:

* **Pending sync** - Group is being prepared to send to the child instance.
* **Syncing** - Child instance has received the group and is in process of storing the group.
* **Synced** - Child instance has stored the group.
* An error condition can also be displayed.

Additional detail about the status of synchronization for every child instance the group is scoped to can be seen by clicking on the group name in the first column.

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

The service level objective (SLO) is that synchronization should occur within 5 minutes. It is expected that most syncs should happen more quickly.

Problematic internet connectivity to child instances in other regions or a child instance that is overloaded could be potential reasons for a sync to fail.
{% endhint %}
{% endstep %}
{% endstepper %}

## Managing Global Groups

In your Global View anchor instance, navigate to *Configuration → Global Groups.*

To manage an existing global group, simply click on it in your list of global groups.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2Fi1Nfz4OE3uPJdccg6K2b%2Fimage.png?alt=media&amp;token=2fdf8d44-7412-4e0b-9021-4b26c8b961d9" alt=""><figcaption></figcaption></figure>

In a child instance, you can also click the **Open Group in Global View** at the top of a group detail screen to be connected to the anchor instance where you can then manage the group.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2F2EKIFYwLbcVLeuadOo6c%2Fimage.png?alt=media&amp;token=a32878f7-d3fe-40b5-b441-c00edafd8242" alt=""><figcaption></figcaption></figure>

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

To delete a global group, there must be no global triage filters that reference the group.
{% endhint %}

## Creating Global Triage Filters

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

Global triage filters take precedence over any local child instance triage filters if there are conditions that would otherwise match detections in either filter rule.

Global triage filters can only be configured and managed in the anchor instance that houses the Global View for your RUX deployment. In child instances, the global filters created in the anchor instance will be in a read only state once synchronized.
{% endhint %}

{% stepper %}
{% step %}

#### Start Triage Filter Creation

In your Global View anchor instance, navigate to *Configuration → Global Triage Filters.*

You will see a list of any existing global triage filters which can be filtered with choices made at the top of the screen.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FI9PqkX2X8l9sXMK2allz%2Fimage.png?alt=media&amp;token=7aa37388-954f-4ca7-bd6f-f19233cde3b4" alt=""><figcaption></figcaption></figure>

Click **Create Global Filter.**
{% endstep %}

{% step %}

#### Create the Global Filter

You can choose to create a **New** filter rule or a **Suppression Rule**.

* **Filter Rule** - Triage filter rules, also known as custom filters, are rules that are applied to detections as they are being created by the system. This is the most commonly used option for Vectra customers.
* **Suppression Rule** - Suppression rules (formerly known as whitelist filters) are NOT recommended to be used because the detections they impact are entirely hidden from the Vectra UI. It is generally recommended to create a normal triage filter instead of a suppression rule. Analysts often benefit from seeing the normal behaviors done by machines that have already been analyzed by others. This knowledge can help in their analysis of other behaviors that may be occurring on the entity.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FUFcJZd26c7xb4QdybYJu%2Fimage.png?alt=media&amp;token=b9e9e1c2-dd57-499b-a0af-6efafde4c370" alt="" width="375"><figcaption></figcaption></figure>

[Triage best practices](https://docs.vectra.ai/configuration/tuning/triage-best-practices.md) provides more details about triage filters. Some of the material in the linked article does not apply to global triage filters. For example, global filters cannot be made from a detection detail screen. The only way to create global triage filters is from the *Global Triage Filters* screen in the anchor instance.

Give your global filter a name, and description.

Choose to **Apply to all Vectra Instances** or specific **Vectra Instances**

* By default, the box will be checked to **Apply to all Vectra Instances**, and the filter will be synchronized to all existing and any future child instances.
* If you want the filter to only apply to specific child instances, uncheck the box and choose specific instances for the filter to apply to by clicking on them in the dropdown.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FmcfDJGJJIiDBxAednxcN%2Fimage.png?alt=media&amp;token=66e08160-4dc4-470d-8dda-fcb0c725bdde" alt=""><figcaption></figcaption></figure>

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

When creating global groups, you must similarly choose which instances the group will apply to. If the global group used as a condition in the triage filter does not exist on any of the child instances that are associated with the global triage filter, the filter creation dialog will give an error message.

It is recommended to apply groups and triage filters to all instances unless there is a specific requirement to not synchronize a global group or filter to some child instances.
{% endhint %}

When choosing conditions that can involve a global group, you can choose from the global groups that have been created. Global rules do not need to include a global group.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FHkrMpDrVGmacxQhFBDtB%2Fimage.png?alt=media&amp;token=3f60038a-7a61-436d-ae3d-8c5b0afff765" alt=""><figcaption></figcaption></figure>

The conditions available will vary by the detection type you are creating the filter rule for. [Triage best practices](https://docs.vectra.ai/configuration/tuning/triage-best-practices.md) provides additional guidance.

When you are done creating the rule, click **Create**.
{% endstep %}

{% step %}

#### Wait for Synchronization

After you have created a global filter, it must be synchronized to the child instances it was scoped to before it can be used in global triage filters.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FAHRjpHCBl09G1HUCE9UG%2Fimage.png?alt=media&amp;token=7ef41d22-6ccd-4d97-9871-9399afb3e665" alt=""><figcaption></figcaption></figure>

Global filters can have the following statuses:

* **Pending sync** - Filter is being prepared to send to the child instance.
* **Syncing** - Child instance has received the filter and is in the process of storing it.
* **Synced** - Child instance has stored the filter.
* An error condition can also be displayed.

Additional detail about the status of synchronization for every child instance the filter is scoped to can be seen by clicking on the eyeball icon next to the sync status for each rule.

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

The service level objective (SLO) is that synchronization should occur within 5 minutes. It is expected that most syncs should happen more quickly.

Problematic internet connectivity to child instances in other regions or a child instance that is overloaded could be potential reasons for a sync to fail.
{% endhint %}
{% endstep %}
{% endstepper %}

## Managing Global Triage Filters

In your Global View anchor instance, navigate to *Configuration → Global Triage Filters.*

To manage an existing global filter, simply find it in your list of global triage filters and click either the edit (pencil) or delete (trash) icon.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2F5I7wdm1tm5hlDzZALk6E%2Fimage.png?alt=media&amp;token=72b9dac7-2f09-457a-a6d5-1af73729b961" alt=""><figcaption></figcaption></figure>

You can also click the arrow icon at the right side of a triage filter in a child instance to be connected to the anchor instance where you can then manage the filter.

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2Fz9ECld5l9O5Xu0qQrPgg%2Fimage.png?alt=media&amp;token=5d3505b5-f0ce-4af4-a195-629a77b255fe" alt=""><figcaption></figcaption></figure>

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

When a global triage filter is deleted, all detections there were triaged by the filter will be restored to their original type and remaining triage filters will be ran against the detections.

Because global triage filters take precedence over any local triage filters in a child instance, the detections that were previously triaged by the global filter rule may now be triaged by a local filter.
{% endhint %}


---

# 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/deployment/getting-started/respond-ux-deployment/global-groups-and-triage-filters.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.
