SentinelOne SentinelOne

Configure the SentinelOne connector to retrieve information via the SentinelOne API

This document describes the procedure for configuring the SentinelOne connector to retrieve information via the SentinelOne API.

Objective

The purpose of this connector is to provide a method for retrieving the following information:

  • Tenant URL
  • API Token + expiration date

Prerequisites

  • Access to the SentinelOne portal with the required permissions.

Information to provide in OverView

FieldDescription
API TokenSentinelOne API authentication token
Console URLSentinelOne console URL

Parameters

These parameters are optional. Leave them at their default value unless you have a specific reason to change them.

ParameterDescriptionDefault
Retrieve VulnerabilitiesRetrieve vulnerabilities from the SentinelOne APIEnabled
Retrieve Vulnerabilities from XSPMRetrieve vulnerabilities from the XSPM Vulnerabilities API instead of Application Risk. With a Singularity Vulnerability Management licence, each vulnerability also carries its EPSS score, its CISA KEV status and the fixed version. Severities then match the Vulnerabilities page of the SentinelOne console. The API token must have access to XSPM; otherwise the connection check fails.Disabled
Retrieve Rogue AssetsRetrieve rogue assets from the SentinelOne APIDisabled
Resolved Alerts Retention (days)Retention period for resolved alerts in days30

Procedure

Generate API Token

  1. Access the SentinelOne portal:
    • Log in to the SentinelOne portal with administrator or account owner rights.
  2. Navigate to API Token Settings:
    • Click on User menu (top right).
    • Select My User or your user account.
    • Go to Options section.
  3. Generate API Token:
    • Click Generate API Token.
    • Review the token permissions.
    • Copy the generated API Token immediately.
    • Store the token securely.
  4. Note the Tenant URL:

Configure in OverView

  1. In OverView, go to Data Sources Settings > Sources.
  2. Select SentinelOne and click Configure.
  3. Enter the Tenant URL (e.g., https://usea1-api.sentinelone.net).
  4. Paste the API Token in the authentication field.
  5. Click Save Configuration.
Alternative: file import through DropPoint

The API access described above is the recommended method for this connector. Where it is not available (a segregated network, a version or licence without API, an export you already produce), OverView accepts file exports, to be uploaded to the bucket dedicated to SentinelOne.

Where do the files go?

Bucket : s3://sentinelone/

Example : s3://sentinelone/export.csv

The procedure is described in the OverView DropPoint guide: generating credentials, configuring the client, then sending files from the OverView web interface, the AWS CLI or an SDK. Its examples come pre-filled with this bucket when you follow this link.

Official Documentation

The API token generation guide is available from within the SentinelOne Management Console under User > My User > Options. For additional details, contact your SentinelOne support representative.