DeepSurface: SentinelOne

Documentation
Installation Guide
Overview
Let DeepSurface Host For You
Getting Started
System Requirements
Self Hosted Quick Start - Installing to Cloud Platforms
Self Hosted - Installation Using an OVA
Registration, Package Installation, and Initialization
First Steps After Initialization of the Console
Deployment Options
Main and Subordinate Consoles
Agent-Based Deployment
User Managed Scan Deployment
Credentialed Scanning Deployment
Mixed Environment
Deployment Tools
Active Directory Group Policy
Microsoft Endpoint Configuration Manager (part of InTune)
Tanium Deploy
HCL BigFix
Ivanti
Virtual Machines
VMWare
Virtual Box
VirtualBox Guest Additions
AWS EC2 (BYOL)
AWS EC2 (Usage Based)
Azure Cloud
Google Cloud
Additional Items to Consider
Main Console Server Certificates
LDAP
TOFU
Clock Sync
DeepSurface Commands
Multiple Vulnerability Sources
API Documentation
User Guide
Reporting
Dashboards
Exports
Risk Insight
Hosts
Patches
Vulnerabilities
Vulnerability Instances
Users
Remediation Workflow Manager
Plans
Settings
Integrations
Workflow
Exporting
Accepted Risk Plans
Accepted Risk Workflow
Explore
Model
Paths
Activity
Tasks
Configuration Alerts
Scan Logs
Notification Settings
Scanning
Status
Agents
User Managed
Credentialed Scanning Settings
Credentials
Scan Groups
General Settings
Cloud Scanning
Network Connectivity
Subordinates
Vulnerability Sources
Setup
Sensitive Assets: Polices
Sensitive Assets: Manual
Admin Settings
SMTP Settings
Certificates
Outbound Proxy
Authentication Providers
Users
Tags
Integrations Guide
Vulnerability Sources
CrowdStrike Spotlight
SentinelOne
Carbon Black Cloud
Microsoft Defender for Endpoint
Wazuh
Lansweeper Cloud
Nessus API
Tenable.io API
Security Center/Tenable.sc API
Rapid7 InsightVM API
Qualys API
Nozomi Guardian
Eclypsium
AWS Inspector
Remediation
Jira Software
Tanium (BETA)
Authentication Providers
LDAP (Active Directory)
SAML (Azure Active Directory)
SAML (Google)
SAML (Okta)
PAM
CyberArk
Delinea (Thycotic)
Microsoft LAPS
Security Guide
Firewall Configuration
Base Network Requirements
Agent Network Requirements
Credentialed Scanning Network Requirements
API Network Requirements
How DeepSurface Scans Work
Domain (LDAP) Scanning
Host Scanning Routine
Reasons for the Administrative Access Requirement
Endpoint Protection Considerations
Other Items
Scope of Data Storage and Retention
IPS/IDS Considerations
Logging
Resetting the DSADMIN password
Product Information
Changelogs
Open source Licenses
End User License Agreement (EULA)

For Configuring DeepSurface to interface with SentinelOne APIs, you need to gather the correct information from SentinelOne and enter it into the appropriate configuration screen in DeepSurface.

Setting Up SentinelOne

For DeepSurface to work with SentinelOne, you need your Hostname/Server and a Secret.

We will start with the Hostname/Server. Log in to SentinelOne and take note of the URL for your management console. It should looks something like the following:

Vulnerability Sources - SentinelOne

Copy/Paste the highlighted portion into the Hostname/Server field in DeepSurface.

To get a valid secret, DeepSurface recommends creating a service user within SentinelOne. A regular console user will work, but credentials will have to be rotated quite regularly and this could unexpectedly break the SentinelOne integration for DeepSurface. A service user, however, can be created to have credentials that do not expire for months or even years. To create a service user in the SentinelOne Management Console, follow these steps:

  1. In the left menu, go to settings and click the "Users" tab along the top of the screen. From here, select "Service Users" in the menu and from the Actions menu, click "Create New Service User"

Vulnerability Sources - SentinelOne

Vulnerability Sources - SentinelOne

  1. You should see a modal pop up with a form to create a new service user, give this service user a name and description and set an expiration date that you are comfortable with. In order for the SentinelOne integration to work properly within DeepSurface, this service user will have to still be active

Vulnerability Sources - SentinelOne

  1. You will now have to select the scope of this service user, select "Site" and then select the site(s) that will be associated with this API Token that will be generated.

Vulnerability Sources - SentinelOne

  1. You should now see a screen displaying your API Token. Be sure to copy this token, because this will be the only time that SentinelOne will show it to you. Paste the token into the secret field in DeepSurface, and save the configuration.

Vulnerability Sources - SentinelOne