Configuring SentinelOne Connectors

This connector allows Stellar Cyber to collect data from external sources and add the records to the data lake.

SentinelOne integration with Stellar Cyber provides advanced threat detection and response capabilities, combining AI-powered endpoint protection with real-time threat intelligence and automated response workflows to improve case response and threat mitigation.

A SentinelOne connector allows you to collect logs, discover assets, and see vulnerabilities. If you enable Respond options on this connector, with the correct type of user account, you can perform the following endpoint response actions:

• Contain (Isolate) Host
• Initiate Scan
• Kill Threat
• Quarantine Threat
• Remediate Threat

The following error from Sentinel One, 503 Service Temporarily Unavailable, is treated by Stellar Cyber as the following error, 429 Too Many Requests, and is not shown on the DP connector list. This will be addressed in a later release.

This connector is improved to use less memory. Under certain scenarios if there is an error reaching the third-party API, some duplicate messages may be sent.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: SentinelOne

               Let us know if you find the above overview useful.

Adding a SentinelOne Connector

To add a SentinelOne connector:

1. Obtain SentinelOne credentials
2. Add the connector in Stellar Cyber
3. Test the connector
4. Verify ingestion

You can also configure SentinelOne to send logs to the Stellar Cyber parser. However, the connector allows you to assign a tenant, while the parser does not.

Obtaining SentinelOne Credentials

As part of this procedure, you specify the credentials of an account on the SentinelOne server that will be used to retrieve data. This account must have read/view permissions or better on the SentinelOne server. To perform response actions, the account must have an administrative role.

1. Log into your SentinelOne Management Console as an administrative user (for example: https://usea1-partners.sentinelone.net/login).

2. From the Management Console navigation pane, select Settings.

   

3. Navigate to Site Info.

   

4. Make sure that Licenses is Complete for the site and that Add-ons is STAR.

   Some content types require an upgraded subscription (STAR) as well as permissions, otherwise the connector will not produce expected results.

5. In the tab for Users, choose Roles.

   • To support the collect only function in Stellar Cyber, choose either Viewer or Admin.

     

   • To support the respond function in Stellar Cyber, choose Admin.

     

6. For the role, set the following permissions for certain content types:

   • To support the Deep Visibility content type, choose Deep Visibility View.

     

   • To support the Threats content type, choose Threats View.

     

   • To support the Rogues content type, choose Rogues View.

     

   If these features are Not allowed (greyed out), contact SentinelOne.

7. Click Save.

8. Choose the Users tab and select the option to add a New User for the account you will use with the Stellar Cyber connector.

   

9. In the User Details, enter the information for the new user.

   

10. Make sure to assign a role to the account, either Viewer or Admin.

    

11. Log out of the SentinelOne Management Console and then log back in with the username you created. You are prompted to create a password for that user. Create the password and complete the login.

12. When logged into the SentinelOne online console as an administrative user, you need to generate an API token for the connector configuration. The token can be generated from a console user or from a service user.

    The following steps are to generate the API token from a console user:

    1. Click the username from the top right of the console and select My User.

       

    2. In the dialog that displays, click the link to Generate an API Token.

    3. This displays the token with a warning to copy it. If you forget the token, you will need to regenerate it. Download it now or Copy it and save it to a file for later use in the connector you configure in Stellar Cyber.

       

    4. Exit the console and proceed to the next section.

    The following steps are to generate the API token from a service user:

    1. Click the USERS tab and choose Service Users. Then select Create New Service User from the Actions menu.

       

    2. Enter the Name of the New Service User and choose an Expiration Date.Then click Next.

       

    3. You can set the Scope of Access for the Account or the Site.

       

    4. To set the Scope of Access for the Account, select Account. Choose Admin or Viewer from the drop-down menu for the role. Choose Admin for respond actions.

       

    5. To set the Scope of Access for the Site, select Site. Choose Admin or Viewer from the drop-down menu for the role. Choose Admin for respond actions.

       

    6. Click Create User.

    7. Copy the API Token.

       

       Store the API key in a safe location. It cannot be retrieved later although it can be regenerated.

    8. Click Close.

Adding the Connector in Stellar Cyber

To add a SentinelOne connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | Integration | Connectors. The Connector Overview appears.

   

3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

   

   The asterisk (*) indicates a required field.

4. Choose Endpoint Security from the Category drop-down.

5. Choose SentinelOne from the Type drop-down.

6. Enable the Function for Collect and/or Respond.

7. Enter a Name.

   This field does not accept multibyte characters.

8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

9. Choose the device on which to run the connector.

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

10. (Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.

11. Click Next. The Configuration tab appears.

    

    The asterisk (*) indicates a required field.

12. Enter the Host URL. This is the address of your SentinelOne server.

    For release versions prior to v4.3.4, ensure the URL does not include a trailing "/" symbol.

13. Enter the API Key (token) you created above.

    In earlier releases, Stellar Cyber supported use of a Username / Password combination. However, SentinelOne now enforces use of 2FA, which necessitates use of a token with API communications.

14. Enter the Interval (min). This is how often the logs are collected.

15. Choose the Content Type. The following logs are supported:

    • Host (Agents)

    • Threat

    • Vulnerabilities

    • The following logs are supported for v4.3.5, and later.

      These content types require an upgraded subscription (STAR) as well as permissions. See Obtain SentinelOne Credentials for details.

      • Alerts

      • Deep Visibility

      • Events (Threat Events)

      • Rogues

      • Threat Notes

16. Click Next. The final confirmation tab appears.

    

17. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

18. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

1. Click System | Integrations | Connectors. The Connector Overview appears.

   

2. Locate the connector that you added, or modified, or that you want to test.

3. Click Test at the right side of that row. The test runs immediately.

   Note that you may run only one test at a time.

Display sample messages...

Success !

Failure with summary of issue: Show More example detail:

 

Verifying Ingestion

To verify ingestion:

1. Click Investigate | Threat Hunting. The Interflow Search tab appears.

2. Set the Indices to match the type of content you collected:

   • For Threat data, change the Indices to Syslog or Alerts.

   • For Host data, change the Indices to Assets. Note that hosts discovered through this connector show SentinelOne as a data source.

   • For Vulnerabilities, change the Indices to Scans.

   • For all other data types, change the Indices to Syslog.

3. Search for the msg_class corresponding to the data type you want to view:

   • Host (Agents): sentinelone_host

   • Threats: sentinelone_threat_detection

   • Vulnerabilities: sentinelone_vulnerabilities

   • Alerts: sentinelone_cloud_detection_alerts

   • Deep Visibility: sentinelone_deep_visibility

   • Events (Threat Events): sentinelone_threat_events

   • Rogues: sentinelone_rogues_table

   • Threat Notes: sentinelone_threat_notes