> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/sentinelone.md).

# SentinelOne

## Create a Collect Rule

{% stepper %}
{% step %}

### Begin Setup

In the Scanner UI, go to the Collect tab.

* From the Overview page click the '+' icon in the upper right corner
* Select create new **Collect Rule**
* Click **Select a Source Type**.
* Choose **SentinelOne**.
* Choose the specific SentinelOne log type (the instructions below apply to all log types).

You’ll be prompted to choose an Ingest Method:

* Select **API Pull**.
* Then, choose a Destination: Select **Scanner**.
  {% endstep %}

{% step %}

### Configuration

Set a Display Name, such as `my-sentinelone-logs`.
{% endstep %}

{% step %}

### Authenticate with SentinelOne

* If you’ve previously created an SentinelOne connection, select it from the list.
* Otherwise, select **New SentinelOne Connection** and fill in the required fields:
  * Connection Name: Give the connection a recognizable name.
  * Base URL: eg. `https://usea1-partners.sentinelone.net`
  * API Token: Generate this from your SentinelOne console.
    {% endstep %}

{% step %}

### Logs Destination

* Choose the S3 Bucket where the raw SentinelOne logs should be stored.
* (Optional) Enter a Key Prefix to organize the data path in your bucket.
  {% endstep %}

{% step %}

### Review and Create

Review all configuration settings. Any errors and/or missing fields must be resolved before completion.
{% endstep %}
{% endstepper %}

## Create an Index Rule

With the Collect Rule created, Scanner will poll the SentinelOne API every **5 minutes**, writing new events to your S3 bucket under the specified prefix.

Create an Index Rule to have Scanner index the logs for fast search and detections.

{% content-ref url="/pages/Gem9jwD4aqayN3OiChpN" %}
[Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md)
{% endcontent-ref %}

### SentinelOne Defaults

When you create the Index Rule from the Collect Rule, the following defaults are pre-populated:

* **File Type**: `Json`
* **Compression**: `Gzip`
* **Transformations**: Add Metadata, Parse JSON Columns, ECS Normalization: SentinelOne (Activities or Threats depending on subtype)
* **Timestamp Field**:
  * `.createdAt` for SentinalOne: Activities
  * `.threatInfo.createdAt` for SentinalOne: Threats


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/sentinelone.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.