Skip to main content

SentinelOne Event Collector

This Integration is part of the SentinelOne Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.8.0 and later.

This integration fetches activities, threats, and alerts from SentinelOne. This integration was integrated and tested with API version 2.1 of SentinelOne.

This is the default integration for this content pack when configured by the Data Onboarder in Cortex XSIAM.

Configure SentinelOne Event Collector on Cortex XSIAM#

  1. Navigate to Settings > Configurations > Data Collection > Automation & Feed Integrations.

  2. Search for SentinelOne Event Collector.

  3. Click Add instance to create and configure a new integration instance.

    Server URL (e.g., URL to use for connectionTrue
    API TokenThe API Token to use for connectionTrue
    Trust any certificate (not secure)Use SSL secure connection or not.False
    Use system proxy settingsUse proxy settings for connection or not.False
    Fetch eventsWhether to bring events or not.False
    Event typesWhat types of events to bring, Possible values are (activities, threats, alerts)False
    First fetch timeFirst fetch query <number> <time unit>, e.g., 7 days. Default 3 days)False
    The maximum number of events per fetch should be between 1-1000The limit is per event type. For example, if you choose 3 event types (ACTIVITIES, THREATS, ALERTS) with a limit of 100, the actually limit will be 300.False
  4. Click Test to validate the URLs, token, and connection.


You can execute these commands from the Cortex XSIAM CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.


Gets events from SentinelOne.

Base Command#



Argument NameDescriptionRequired
should_push_eventsIf true, the command will create events, otherwise it will only display them. Possible values are: true, false. Default is false.Optional
limitMaximum number of results to return. Value should be between 1 - 1000. Default is 1000.Optional

Context Output#

There is no context output for this command.