How To: Deploy SentinelOne via Addigy's Custom Software

This article serves as a guide to install SentinelOne via Addigy's Custom Software.

Note: SentinelOne requires a token file that is unique per organization.

Prerequisites

In order to build the Custom Software, you will need the SentinelOne Installer (.pkg file) and token.

The following command will create the token file:

echo "TOKEN_HERE" > "com.sentinelone.registration-token"

Replace TOKEN_HERE with the actual token provided by SentinelOne. This should create the token in your user's folder. Alternatively, you can search for the token in the Finder app by searching for "com.sen".

Creating the Custom Software

1. Upload the .pkg file and token into Addigy using our file manager. The custom software should look similar to the below:
   
2. SentinelOne also has PPPC profiles that our Smart Software will detect when the package file is uploaded. Add them in as shown below:
   
   Note: In the event that a PPPC profile is unsigned, the signatures for known SentinelOne applications are available in the table below.
   
3. Upon uploading the PKG, the Add button will appear next to the package name, as shown in Step 1. Click this button to have the installation script automatically added to the Installation Script section of the Custom Software. It will look similar to the below image:
   
   

Full Disk Access

To build a PPPC payload for Full Disk Access, see our article about creating a Full Disk Access payload. The table below contains known binaries for SentinelOne:

You should be all set to deploy SentinelOne after creating and adding these items to your policy!