> For the complete documentation index, see [llms.txt](https://docs.fusion.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.fusion.vectra.ai/enrich-traffic-with-context/configure-context-integrations/sentinelone.md).

# SentinelOne

This document provides instructions for configuring SentinelOne in order for the Vectra Context Integration to have the correct access to pull label contexts. Prerequisites Configure API token Bef

This document provides instructions for configuring SentinelOne in order for the Vectra Context Integration to have the correct access to pull label contexts.

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

### Configure API token <a href="#configure-api-token" id="configure-api-token"></a>

Before configuring the SentinelOne Context Integration in Vectra, you will need to an API token configured in SentinelOne. For more information configuring the API token from the SentinelOne management console, see the [API Overview](https://usea1-300-nfr.sentinelone.net/api-doc/overview) documentation.

## Vectra Portal Steps <a href="#vectra-portal-steps" id="vectra-portal-steps"></a>

Navigate to Integrations (make sure you are on the Context tab) and click "Add Integration", then select `SentinelOne`

<div align="left"><img src="https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-71e14aa4971bb6e6d4010284e9468a9c4f087c26%2Fb0e2111e3b5cde406e668cf2be92dce17930ae994901f7a897553ebfaea3e263.png?alt=media" alt=""></div>

### Configuration <a href="#configuration" id="configuration"></a>

The following fields are specific to the SentinelOne integration.

| Field            | Required | Description                                                                           | Example                                                                     |
| ---------------- | -------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| `Base URL`       | yes      | The SentinelOne domain URL to query                                                   | `https://<subdomain>.sentinelone.net` `https://<subdomain>.sentinelone.com` |
| `Account Id`     |          | The SentinelOne account ID to query                                                   |                                                                             |
| `Filter Id`      |          | The SentinelOne filter ID to limit query, SentinelOne API result size limit is 10,000 |                                                                             |
| `Include Ranger` |          | If enabled, include Ranger labels                                                     |                                                                             |

### Authentication <a href="#authentication" id="authentication"></a>

The following fields are necessary for the integration to authenticate with SentinelOne.

| Field   | Required | Description                         |
| ------- | -------- | ----------------------------------- |
| `Token` | yes      | API token to use for authentication |


---

# 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.fusion.vectra.ai/enrich-traffic-with-context/configure-context-integrations/sentinelone.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.
