Initialize the SentinelOne Beat

Prerequisites

Direction

Port

Protocol

Source

Outbound

443

HTTPS

SentinelOne Beat

Initialize the Beat via the Web Console (Recommended)

  1. Ensure that the Open Collector Connection to the SIEM (WebUI) setup has been completed.

  2. Ensure that the System Monitor Agent to which you intend to send these logs has been Configured for JSON Parsing.

Use either the Enable JSON Parsing on System Monitor Agents or the Enable JSON Parsing for an Existing System Monitor Agent sections at the above link to configure the System Monitor Agent for JSON Parsing.

  1. Follow the steps outlined in Add a Beat in the Web Console to create the Beat via the Web UI.

Initialize the Beat via Command Line (Legacy)

  1. To confirm the Open Collector is running, run the following command:

    ./lrctl status
    

    You should see the open_collector and metrics versions.
    If the Open Collector is not running correctly, see Troubleshoot the Open Collector in the Open Collector Installation and User Guide.

  2. In the Open Collector, run the following command:

    ./lrctl sentinelonebeat start
    
  3. Enter a unique identifier for the beat instance.

  4. Enter the SentinelOne API URL.

The following URLs are supported for this Beat:

https://<your sentinelone domain>/web/api/v2.1/activities

https://<your sentinelone domain>/web/api/v2.1/cloud-detection/alerts

https://<your sentinelone domain>/web/api/v2.1/device-control/events

https://<your sentinelone domain>/web/api/v2.1/exclusions

https://<your sentinelone domain>/web/api/v2.1/threats

  1. Enter the API Token (Bearer Token) obtained during the steps outlined in Configure the SentinelOne Portal.

  2. (Optional.) Enter any unique Site IDs from which you would like to collect.

Site IDs are optional, and can be left blank by pressing 'c' on the keyboard.

  1. Enter the hostname or IP and Port Number of the Sysmon JSON Parser.

  2. Press Enter.
    The beat starts successfully.