1. Log in to your SentinelOne console and navigate to Settings > Users.
2. Select the Roles tab in the side menu.
3. Locate the Viewer role in the list and select the checkbox.
4. Select Actions > Duplicate Role.
   
5. Name the role "Viewer - Expel".
6. In addition to the defaults, add these permissions:
   • Endpoints: Remote Shell, Initiate Scan, File Fetch, and Fetch Logs.
   • Endpoint Threats: Fetch Threat File.
7. Select Save.
8. In the side menu, select Console Users.
9. Select Actions > Add New User.
   
10. Configure the new user as follows:
    • Full Name - enter "Expel SOC".
    • Email Address - enter "soc+<Your_Organization_Name>@expel.io".
      • For example, if your organization were Acme Corp, the format would be "soc+acme_corp@expel.io".
    • Access Level - select Account and select the account for access.
    • Role - enter a role name and then select the View permission. If you wish to enable status syncing, you must also select the Manage permission.
      
11. Select Create User. This triggers an email invitation allowing the Expel SOC to create an account and complete console access configuration in Workbench on your behalf.

1. Navigate to Settings > Users.
2. Select the Service Users tab in the side menu.
3. Select Actions > Create New Service User.
   
4. Configure  the new user as follows:
   • Name - enter "Expel API".
   • Description - enter "API Service user for Expel integration".
   • Expiration date - select an expiration period that suits your organization.
5. Select Next.
6. On the Scope of Access screen:
   • Access Level - select Account.
   • Select the account to grant access, and assign it the IR Team role.
     
7. Select Create User.
8. Copy and save the API token in a safe place for use in a later step. You will only be shown this value once.
9. Select Close.

Step 3: Add SentinelOne Singularity Endpoint as a Security Device in Workbench

Now that you have the necessary credentials configured, you can set up the integration in Workbench.

1. Log in to Workbench.
2. In the side menu, navigate to Organization Settings > Security Devices.
3. Select Add Security Device.
4. In the search box, type “SentinelOne” and then select the SentinelOne Singularity Endpoint integration.
   
5. Complete the fields as follows:
   • Name - enter a name that might help you more easily identify this integration, such as “CompanyName - S1 EDR”.
   • Location - enter the location of your integration, for example “cloud" or "on-prem”.
   • Server address - enter the server address (URL) of the SentinelOne console. For example: https://usea1-1001.sentinelone.net
   • API key - enter the API token you generated in Step 2.
   • Enable status syncing? - if you have chosen to grant Manage permissions in Step 1, select Yes to enable the status syncing.
6. Select Save.
7. On the console access screen, select Set up later. Expel will set up console access using the newly created console user. 
8. Select Save.
9. Select Done.
10. Your device should be created successfully within a few seconds. A few reminders:
    • After your connection is healthy, it will take some time for your device to begin polling and receiving data.
    • To check on the status, select the downward arrow for your device in the first column and choose View details. You can then scroll to the Connection section to see if your device is fully connected.
    • Polling will happen first; data will be received after that. You must refresh the page to see updates.
    • If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, contact our Support team for help.
    • To check if alerts are coming through, navigate to Dashboards > Alert Analysis. Scroll to the device you want to check, and select the Expel Alerts tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

Reference

About Status Syncing

If you have chosen to grant Manage permissions to Expel during your setup and have also enabled status syncing in the security device, syncing will be enabled upon completion of this guide. Syncing is currently one-way and Workbench serves as the source of truth. This means statuses in SentinelOne are updated by Workbench, but Workbench is not informed or updated by status changes made in SentinelOne. 

Workbench status syncing is available for any SentinelOne customer using the Singularity Endpoint platform. The addition of Wayfinder MDR or other SentinelOne services do not impact API permissions or Workbench status syncing.

Limitations

1. Syncing only applies to SentinelOne threats that generate an Expel Alert. 

If a SentinelOne alert is ingested but does not meet our detections threshold (i.e. remains a vendor alert), then nothing “happens” in SentinelOne. We acknowledge this creates a possible blind spot into knowing what our SOC is or is not triaging, and are committed to supporting this use case in the future.

2. Status syncing behaviors are limited to alert status and commenting. 

Expel Alert assignment metadata (i.e. assigned to Expel, assigned to your organization) does not map back to SentinelOne threats.

Object Mappings

*There is no apples-to-apples object def mapping between Workbench and SentinelOne. Workbench Investigation/Incident states instead map to all S1 Threats associated with the Incident/Investigation. 

State Mappings

*Undefined is the typical, default status for a threat that has not been triaged and thus does not map to an Expel “Closed” state.

Comments

In addition to state syncing, the close reason and associated analysis is added as a comment to the SentinelOne Singularity Endpoint alert or incident upon closure.  

Supported Events