> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/endpoint-protection/sentinelone.md).

# SentinelOne

Connect SentinelOne to ThreatDefence so our SOC can monitor your endpoint threats and alerts around the clock, see how each threat was handled, and investigate incidents with full context.

The integration uses SentinelOne's management API. You create one service user for ThreatDefence with the **Viewer** role in Step 2. That one service user covers:

| Capability          | What it enables                                                                                                                                 | Needed?                                  |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| Monitoring          | Threats and every change to them, alerts and console activity flow into ThreatDefence for 24×7 monitoring                                       | Required                                 |
| Context and posture | Endpoint and agent health, exclusions and blocklist, installed applications and network discovery give our analysts context in an investigation | Required                                 |
| Vulnerabilities     | Open vulnerabilities per endpoint, for prioritization and reporting, and whether a vulnerability was the way in                                 | Optional, needs Vulnerability Management |

The service user is read-only. ThreatDefence never changes anything in your SentinelOne console.

{% hint style="info" %}
**Before you begin:**

* Sign in to your SentinelOne Management Console with an **Admin** role. Only Admins can create service users.
* Check whether the console is your own or run by your IT provider. If a provider runs it, see [Consoles run by a provider](#consoles-run-by-a-provider).
* Note your console address (Step 1).
  {% endhint %}

***

### Step 1: Find your console address

Your console address is the start of the browser URL, up to and including `.sentinelone.net`, for example `https://usea1-yourcompany.sentinelone.net`. Leave out anything after the host name, such as `/dashboard` or `/settings`: the integration won't start with a path in the address.

The first part of the address shows where your data is held: for example `usea1` is US East, `euce1` is EU Central, and `apne1` and `apse2` are Asia-Pacific.

***

### Step 2: Create the ThreatDefence SIEM service user

Use a service user, not a personal API token. A service user's token belongs to the console, so it keeps working when staff leave or regenerate their own tokens.

1. Go to **Settings → Users → Service Users** and select **Actions → Create New Service User**.
2. Name it **ThreatDefence SIEM** and add a description such as "ThreatDefence 24×7 SOC monitoring".
3. **Expiration date**: choose the longest your console allows, and note the date. A service user token can't be extended, so create a new one before it expires (see [Rotating or revoking the token](#rotating-or-revoking-the-token)).
4. **Scope**: select **Site** and choose your site. Choose **Account** only if you own several sites on your own console.
5. **Role**: select **Viewer**. It includes every permission in the tables below, and nothing more is needed. If your organization uses custom roles, grant the **View** permissions listed.

**Monitoring**

| Data             | Permission     | How often        | What ThreatDefence uses it for                                                                                                                                                 |
| ---------------- | -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Threats          | Threats: View  | Every 15 minutes | Every threat your agents detect, and every later change to it: mitigation, analyst verdict and resolution                                                                      |
| Alerts           | Alerts: View   | Every 15 minutes | The unified alert queue: STAR custom rules, Identity, Cloud and third-party alerts. On consoles without the unified alert queue, STAR custom-rule alerts are collected instead |
| Console activity | Activity: View | Every 15 minutes | The console's activity log: logins, policy and exclusion changes, agent connects and disconnects, mitigations, user and service user changes                                   |

**Context and posture**

| Data                     | Permission                        | SentinelOne module                   | How often          | What ThreatDefence uses it for                                                                                                                       |
| ------------------------ | --------------------------------- | ------------------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Endpoints                | Endpoints: View                   | Any                                  | Daily              | Every agent and its health: version, operating system, network status, infection state and last activity                                             |
| Exclusions and blocklist | Exclusions: View, Blocklist: View | Any                                  | Daily              | What your agents are told to ignore (paths, hashes, certificates, browsers, file types) and the hashes you block. A new exclusion can hide an attack |
| Installed applications   | Applications: View                | Depends on licence                   | Weekly             | The software installed on each endpoint, for threat hunting and exposure                                                                             |
| Network discovery        | Ranger: View                      | Singularity Ranger                   | Daily              | Unmanaged devices that Ranger finds on your network                                                                                                  |
| Vulnerabilities          | Vulnerability Management: View    | Singularity Vulnerability Management | Weekly, on request | Open vulnerabilities per endpoint. Ask your ThreatDefence contact to turn this on                                                                    |

ThreatDefence collects every data type your token and licence allow. A data type your console doesn't include is skipped and everything else keeps flowing. If you add it later, collection starts within a day, with no change needed on your side.

6. Select **Create User**, then copy the **API token**. SentinelOne shows it only once.

{% hint style="info" %}
**Note:** Menu and permission names can differ slightly between SentinelOne console versions. If you can't find **Service Users**, look under **Settings → Users** for the service user option your console offers.
{% endhint %}

***

### Permissions ThreatDefence never asks for

ThreatDefence needs only the **Viewer** role. Never grant a ThreatDefence service user:

* **Remote Shell**: it opens an interactive shell with system privileges on your endpoints.
* **Endpoints: View Passphrase**: the anti-tamper passphrase lets anyone uninstall the agent.
* **Uninstall**, **Decommission**, **Disable Agent** or **Reset Local Config** on endpoints.
* **Create** on exclusions, or **Edit** on any policy.
* **Create** or **Edit** on users, service users or roles, or API token generation.
* **Edit** on your account or site.

If anyone asks you to grant these on ThreatDefence's behalf, contact us before you do.

***

### Step 3: Add the integration in ThreatDefence

Please follow the [Managing Integrations](https://docs.threatdefence.com/platform-management/managing-integrations.md) instructions and onboard the integration. You'll need:

* **SentinelOne API hostname**: the console address from Step 1
* **SentinelOne API key**: the service user token from Step 2

Threats, alerts and console activity from the last two days appear within about 15 minutes, and your endpoint, policy and application inventory follows shortly after.

{% hint style="warning" %}
Don't send API tokens by email or chat. If you can't use the platform form, ask your ThreatDefence contact for a one-time secure upload link.
{% endhint %}

#### Consoles run by a provider

If your SentinelOne is supplied through a managed service, such as Barracuda XDR Managed Endpoint or an IT provider's multi-tenant console, you may not be able to create service users yourself. Ask the provider for the console address and a service user token scoped to **your site only**, with the **Viewer** role. Don't use a token scoped to the provider's whole account: it can read other customers' data.

Barracuda XDR Managed Endpoint Security runs on SentinelOne, so moving to it doesn't end this integration. Only the console address and token change.

#### Rotating or revoking the token

* **Rotate**: create a new service user as in Step 2, paste its token into the ThreatDefence integration, then delete the old service user. Collection resumes from where it stopped, so nothing is lost.
* **Revoke**: delete the service user in SentinelOne. Collection stops straight away.

#### Troubleshooting

| Symptom                   | Likely cause                                                              | Fix                                                                                      |
| ------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| No data after onboarding  | The console address includes a path, or the token was copied incompletely | Use only `https://<name>.sentinelone.net` and paste the token again                      |
| Data stopped after a date | The token expired, or the service user was deleted                        | Create a new service user and update the integration                                     |
| A data type is missing    | Your licence or console version doesn't include it                        | No action needed: everything else keeps flowing. Contact us if you expected it to appear |

***

## Support

For questions or assistance, please contact:\
📧 **<support@threatdefence.com>**


---

# 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.threatdefence.com/siem-integrations/endpoint-protection/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.
