This document applies to Classic/Legacy Integrations. You may continue to use these integration configurations. While no active development is happening for these integrations, we continue to provide Classic/Legacy Integrations in the product. You do not have to move to MSI Integrations. If your support engineer or TSC recommends or you choose to move to MSI Integrations, you can take advantage of the latest features and functionality. For more information, see the MSI Integration documentation in the Integrations Overview.
The SentinelOne Integration uses SentinelOne's API to function correctly. Versions 2.0 and 2.1 of the SentinelOne API are supported.
The API request that the SentinelOne integration uses is bound by time limits. The time on the Director and Actor must be kept synchronized, or else no events will match.
Update SentinelOne
To update SentinelOne
- Define a username that will be attached to the API key that the Validation Platform will use. The username must have at least Site Viewer access.
- Use the SentinelOne Portal to generate an API key that can be used in the integration setup in the Director.
Update Security Validation
Prerequisites
Information to gather before you start:
- The SentinelOne API key.
- The name of the host where SentinelOne is installed.
- The Actor configured with the exact name of the host that is running SentinelOne (shown in the SentinelOne Portal).
Configuration
To add the SentinelOne integration
Go to Settings > Integrations.
- Click Add Integration > SentinelOne.
Enter the Host.
This is the SentinelOne address given to the customer by SentinelOne.
- Enter the API Key.
- Select the API Version.
- (Optional) Update the Query.
Expand Advanced options.
(Optional) Update Query time and Delay time.
The Query time is the amount of time (minutes) before and after the query runs that the looks for events, while the Delay time is the amount of time (minutes) that the platform waits to run the query after a Job Action. For example, you configure your integration with the following values: Query time = 5, Query interval = 30 seconds, and Delay time = 0. When a Job Actions starts at 12:00:00, the first time the query runs, the platform looks for events from 11:55:00 to 12:00:00. Then 30 seconds later, it looks for events from 11:55:30 to 12:00:30. This interval continues, with the last query looking from 12:00:00 to 12:05:00. If you instead configured the Delay time to equal 10, it would run the same query, but it wouldn't start that query until 12:10:00.If your monitors are set to run more frequently than the query time, it will impact the pass/fail results for AEDA monitors.(Optional) Clear Discover network devices automatically.
Modify the Query Interval and Event Time Adjustment, if necessary.
(Optional) Assign a Name.
(Optional) Choose Yes to save suspicious events.
Click Submit.
Set up Proxy Assignment
If all outbound connections go through a proxy, you may want to set up a proxy definition and assignment for your integration. For information on setting up your proxy rules, see Proxy Rules.
Verify Connectivity
To verify connectivity to Sentinel One
Click Test to verify that:
- The Director can communicate with the Sentinel One IP address on the port specified.
- The API key is working and has the necessary privileges.