SentinelOne

Create a Collect Rule

1

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.

2

Configuration

Set a Display Name, such as my-sentinelone-logs.

3

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.

4

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.

5

Review and Create

Review all configuration settings. Any errors and/or missing fields must be resolved before completion.

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.

Create an Index Rule

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