> 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

To integrate Sentinel One with ThreatDefence, follow these steps:

## Step 1: Configuration in Sentinel One Management Console

1. Log in to the Sentinel One Management Console with administrative credentials.
2. Go to Settings > Users in the Management Console.
3. Click on the Admin user for whom you want to generate an API token.
   * Note: Creating a new user is not required; a Viewer user role is sufficient to query the SentinelOne API.
4. Click on the "Generate" link next to API Token.
5. A new window will open displaying the API Token. Click on "Copy" to save it to your clipboard.
6. You will also need the SentinelOne API URL for integration. This information is typically provided within the Sentinel One Management Console.

## Step 2: Configuration in ThreatDefence

**Provide ThreatDefence with Client Information**:

* Provide the following information to your ThreatDefence representative at support \[at] threatdefence.com:
* SentinelOne API Key
* SentinelOne API URL


---

# 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.