Loading

SentinelOne Integration for Elastic

Serverless Observability Serverless Security Stack 9.2.1

Version 2.0.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API

The SentinelOne integration collects and parses data from SentinelOne REST APIs. This integration also offers the capability to perform response actions on SentinelOne hosts directly through the Elastic Security interface (introduced with v8.12.0). Additional configuration is required; for detailed guidance, refer to documentation.

This module has been tested against SentinelOne Management Console API version 2.1.

This integration periodically queries the SentinelOne REST API to retrieve Activity, Agent, Alert, Application, Application Risk, Group, Threat and Threat Event logs.

This integration collects log messages of the following types:

  • Activity: Captures general actions or events occurring within the SentinelOne environment, such as policy updates or administrative operations.
  • Agent: Provides details about endpoint agents, including their status, configuration, and activity on protected devices.
  • Alert: Represents security notifications triggered by detected suspicious or malicious activity requiring attention.
  • Application: Logs information about installed or executed applications identified on endpoints.
  • Application Risk: Assesses and records the risk level or reputation of discovered applications based on behavior and source.
  • Group: Contains configuration and status information for endpoint groups within a site or tenant.
  • Threat: Logs confirmed malicious detections, such as malware, exploits, or ransomware identified by SentinelOne.
  • Threat Event: Provides detailed event-level information related to a specific threat, including process, file, and network indicators.

Integrating SentinelOne Activity, Agent, Alert, Application, Application Risk, Group, Threat, and Threat Event logs with Elastic SIEM provides centralized visibility across endpoint operations and security events. Dashboards deliver insights into agent status, detections, application behavior, and threat lifecycle, helping SOC teams quickly identify malicious activity, enforce policy compliance, and accelerate investigation and response efforts.

To collect data from SentinelOne APIs, you must have an API token. To create an API token, follow these steps:

  1. Log in to the SentinelOne Management Console as an Admin. SentinelOne dashboards
  2. Navigate to Logged User Account from top right panel in the navigation bar.
  3. Click My User.
  4. In the API token section, navigate to Actions > API Token Operators > Generate API Token.
    SentinelOne generate API token
  5. Enter the MFA code, if enabled. SentinelOne generate MFA Code
  6. You will see the API token on the screen.

Permissions Required for the Role Attached to the User

Data Stream Permission
Activity Activity -> view
Agent Endpoints -> view
Alert STAR Rule Alerts -> view
Application Applications -> view
Application Risk Applications -> viewRisks
Group Groups -> view
Threat Threats -> view
Threat Event Threats -> view

The alert data stream depends on STAR Custom Rules. STAR Custom Rules are supported in Cloud environments, but are not supported in on-premises environments. Because of this, the alert data stream is not supported in on-premises environments.

This integration supports both Elastic Agentless-based and Agent-based installations.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

  • The API token generated by the user is time-limited. The user must reconfigure a new API token before it expires.
    • For console users, the default expiration time limit is 30 days.
    • For service users, the expiration time limit is the same as the duration specified while generating the API token.
  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type SentinelOne.

  3. Select the SentinelOne integration from the search results.

  4. Select Add SentinelOne to add the integration.

  5. Enable and configure only the collection methods which you will use.

    • To Collect SentinelOne logs via API, you'll need to:

      • Configure URL and API Token.
      • Enable/Disable the required datasets.
      • For each dataset, adjust the integration configuration parameters if required, including the Interval, Preserve original event etc. to enable data collection.
  6. Select Save and continue to save the integration.

  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type SentinelOne.
  3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

This is the activity dataset.

This is the agent dataset.

This is the alert dataset.

This is the application dataset.

This is the application risk dataset.

This is the group dataset.

This is the threat dataset.

This is the threat event dataset.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.