Configure SentinelOne Singularity Endpoint to send logs to Arctic Wolf
You can configure SentinelOne® Singularity Endpoint to send the necessary logs to Arctic Wolf® for security monitoring.
To configure log monitoring for multiple SentinelOne products, only complete these instructions once. Make sure that the credentials that you submit to Arctic Wolf are associated with all required licenses and permissions.
- Singularity Core or higher SentinelOne license
- Admin permissions for the applicable SentinelOne environment
After configuring Arctic Wolf monitoring of your SentinelOne Singularity Endpoint environment, you can configure SentinelOne Singularity Endpoint to contain possibly compromised hosts. For more information, see Configure SentinelOne for Arctic Wolf Active Response.
Create a new service account
Each service user generates one API token that Arctic Wolf uses 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 provide 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 then provide it to Arctic Wolf.
Provide SentinelOne credentials to Arctic Wolf
Time-based events are polled with a delay to make sure that data is available. For new deployments, Arctic Wolf begins polling and reviewing activity from approximately one hour prior to configuration success. If API credentials fail, for example due to expired credentials, Arctic Wolf notifies you and requests a new set of credentials. After receiving refreshed credentials, Arctic Wolf can only retrieve data from the previous 12 hours. Provide refreshed credentials within 12 hours of expiry to enable complete data polling and coverage.