SentinelOne Containment

Updated Sep 27, 2023

Configure SentinelOne containment

Arctic Wolf® uses SentinelOne® APIs to monitor SentinelOne logs and alert you about suspicious or malicious activity. When required, the Active Response service can then contain hosts in your network using SentinelOne.

Note: The SentinelOne containment integration is different from the SentinelOne Endpoint Detection and Response (EDR) integration. You only need to complete these steps if you want Arctic Wolf to contain your endpoints using SentinelOne. For more information on the EDR configuration, see SentinelOne Monitoring.

To implement this functionality, you must provide these credentials to Arctic Wolf:


Before you begin


  1. Create a new service account.
  2. Provide credentials to Arctic Wolf.

Step 1: Create a new service account

Each SentinelOne service user generates a single API token. Arctic Wolf uses this token to monitor the SentinelOne environment.


  • If you manage Arctic Wolf services for multiple customers, you must create a new service user for each customer that you want to configure monitoring for.
  • The API token is only available to view during token creation. If this information is lost before you submit it to Arctic Wolf, you must create a new token for the API.
  • The service user token expires after two years. At that time, you must generate a new token for that user and submit it to Arctic Wolf.
  1. Go to https://<prefix>, where <prefix> is the prefix value that SentinelOne provided to your company.

  2. Sign in to the SentinelOne Console as an administrator.

  3. Hover your mouse over the SentinelOne logo to open the navigation pane.

  4. Click Settings.

  5. Click the USERS tab.

  6. In the navigation pane, click Service Users.

  7. In the Actions list, select Create New Service User.

  8. In the dialog, configure these settings:

    • Name — Enter a relevant name. For example SentinelOne Arctic Wolf Sensor.
    • Description — (Optional) Enter a description for this user.
    • Expiration Date — Select 2 Years.
  9. Click Next.

  10. If you manage multiple customers:

    1. In the Select Scope of Access section, click Site.
    2. Select the site that belongs to the customer that you are configuring monitoring for.
  11. If you do not manage multiple customers:

    1. In the Select Scope of Access section, click Account.
    2. Select the account that the user should have access to.
  12. In the role type list, select SOC.

  13. Click Create User to save the newly created user.

  14. In the API Token dialog, copy the API Token value to provide to Arctic Wolf later.

  15. Exit the dialog and sign out of the account.

Step 2: Provide credentials to Arctic Wolf

Note: If API credentials fail, for example, due to expired credentials, Arctic Wolf will notify you and request a new set of credentials. After a polling failure, Arctic Wolf cannot perform actions such as containment until the updated credentials are provided.

  1. Sign in to the Arctic Wolf Unified Portal.

  2. In the menu bar, click Telemetry Management > Connected Accounts.

  3. Click Add Account +.

  4. On the Add Account page, from the Account Type list, select Cloud Detection and Response.

  5. From the list of cloud services, select SentinelOne Containment.

  6. On the Add Account page, complete these steps:

    1. Account Name — Enter a unique and descriptive name for the account.

    2. In the URL field, enter the URL that you use to sign in to the SentinelOne console.

      This URL usually follows this format, where <prefix> is the prefix value that SentinelOne provided to your company: https://<prefix>

    3. In the API Token field, enter the API token obtained in Create a new service account.

    4. Credential Expiry — (Optional) Enter the expiration date if the credentials have an expiry date.

  7. Click Test and Submit Credentials.

    After your Concierge Security® Team (CST) enables security monitoring for this account, the connected account status changes to Healthy.

Test SentinelOne containment

After you configure SentinelOne containment and provide credentials to Arctic Wolf, you should test the containment and containment lifting procedures with your CST.

Before you begin

Generate a test observation

Note: Generate the test observation at least one hour before the call.

Use one of these methods to generate a test observation for SentinelOne:

Use an EICAR file

If you:

If these options don't work due to your security controls, contact your CST for assistance.

Use the forcedThreatMemes configuration (Windows only)

  1. Enable the forcedThreatMemes configuration option using one of these methods:

    • Run this command to manually enable forcedThreatMemes using SentinelCtl.exe:

      shell .\sentinelctl.exe config -p forcedThreatMemes -v true -k “<passphrase>”

    • Implement this SentinelOne Agent policy override: {"forcedThreatMemes":true}.

  2. Once forcedThreatMemes is enabled, generate one of these threat types:

    • Static threat — Run this command to create an executable named rickrolling2007.exe that starts with MZ and is not signed by a known vendor:

      echo "test" > rickrolling2007.exe
    • Dynamic threat — Run any executable named sneezingpanda2006.exe that is not signed by a known vendor.

Threats generated with the forcedThreatMemes configuration are classified as info stealer, malware, and generic heuristic threats.

Next steps

Note: Turn off your auto-mitigation policy before the call because Arctic Wolf can’t contain a host if the relevant application already addressed the possible threat.

During the scheduled call, your CST: