SentinelOne: Block Bad Hashes

This guide helps you set up your SentinelOne device and grant necessary permissions so that you can enable the Block Bad Hashes auto remediation in Workbench.

This guide is the first step of a larger process to enable auto remediations. After completing the steps on this page, you will be instructed to return to the Enable an Auto Remediation in Workbench guide to finish your setup.

How It Works

If our SOC identifies a hash that must be blocked, Workbench completes the action automatically unless it is specifically called out as a "Never block" asset (these hashes must be added as context and then configured in Workbench; see Step 2).

Endpoints Used

SentinelOne API

web/api/v2.1, sha1

sha1 reflects the hash type Expel's remediation currently declares. The hash algorithm is not sent to SentinelOne (only the raw hash value is submitted), so this remediation will likely also accept a sha256 hash. This has not been verified against SentinelOne's live API, however.

Method	Endpoint	Purpose
GET	web/api/v2.1/restrictions	Pre-check: find existing blocklist entries matching the hash
GET	web/api/v2.1/accounts	Resolve tenant scope (account IDs) for the restriction filter
GET	web/api/v2.1/sites	Fallback scope resolution, only if no account IDs are found
POST	web/api/v2.1/restrictions	Create a black_hash blocklist entry — called once per OS (Windows, macOS, Linux)

Revert (unblock): GET web/api/v2.1/restrictions to find the restriction ID(s), then DELETE web/api/v2.1/restrictions (batch delete by ID).

Step 1: Allow Appropriate Permissions in Your EDR Console

1. Make sure you assign all API permissions in the SentinelOne Setup for Workbench guide.
2. This includes enabling all deny list permissions for the API user.

   

Step 2: Update Your Context

If you do not want to specify any hashes for a "do not block" list, skip to Step 3.

Working with your Customer Success Manager, add any hashes that should be on the "do not block" list as org context for your environment. You will then be able to select those hashes as "Never block" assets when you enable the auto remediation in Workbench.

If our SOC identifies a hash that must be blocked, any hashes added as "Never block" assets are assigned to you as actions rather than being blocked automatically.

Step 3: Return to the Main Setup Guide

Your SentinelOne device is now ready for the Block Bad Hashes auto remediation. You should now do one of the following:

• If you do not need to set up any other devices for this auto remediation, you can return to the Enable an Auto Remediation in Workbench guide to finish Step 2 of the process.
• If you need to set up additional devices for this auto remediation, or wish to use this device with multiple auto remediations, be sure to complete those setup guides as well before returning to the Enable an Auto Remediation in Workbench guide to finish Step 2 of the process. Make sure to follow the setup guide that is specific to your auto remediation, as device setup instructions are unique to each auto remediation and device.