DeepSurface: SentinelOne
DocumentationInstallation GuideOverviewLet DeepSurface Host For YouGetting StartedSystem RequirementsSelf Hosted Quick Start - Installing to Cloud PlatformsSelf Hosted - Installation Using an OVARegistration, Package Installation, and InitializationFirst Steps After Initialization of the ConsoleDeployment OptionsMain and Subordinate ConsolesAgent-Based DeploymentUser Managed Scan DeploymentCredentialed Scanning DeploymentMixed EnvironmentDeployment ToolsActive Directory Group PolicyMicrosoft Endpoint Configuration Manager (part of InTune)Tanium DeployHCL BigFixIvantiVirtual MachinesVMWareVirtual BoxVirtualBox Guest AdditionsAWS EC2 (BYOL)AWS EC2 (Usage Based)Azure CloudGoogle CloudAdditional Items to ConsiderMain Console Server CertificatesLDAPTOFUClock SyncDeepSurface CommandsMultiple Vulnerability SourcesAPI DocumentationUser GuideReportingDashboardsExportsRisk InsightHostsPatchesVulnerabilitiesVulnerability InstancesUsersRemediation Workflow ManagerPlansSettingsIntegrationsWorkflowExportingAccepted Risk PlansAccepted Risk WorkflowExploreModelPathsActivityTasksConfiguration AlertsScan LogsNotification SettingsScanningStatusAgentsUser ManagedCredentialed Scanning SettingsCredentialsScan GroupsGeneral SettingsCloud ScanningNetwork ConnectivitySubordinatesVulnerability SourcesSetupSensitive Assets: PolicesSensitive Assets: ManualAdmin SettingsSMTP SettingsCertificatesOutbound ProxyAuthentication ProvidersUsersTagsIntegrations GuideVulnerability SourcesCrowdStrike SpotlightSentinelOneCarbon Black CloudMicrosoft Defender for EndpointWazuhLansweeper CloudNessus APITenable.io APISecurity Center/Tenable.sc APIRapid7 InsightVM APIQualys APINozomi GuardianEclypsiumAWS InspectorRemediationJira SoftwareTanium (BETA)Authentication ProvidersLDAP (Active Directory)SAML (Azure Active Directory)SAML (Google)SAML (Okta)PAMCyberArkDelinea (Thycotic)Microsoft LAPSSecurity GuideFirewall ConfigurationBase Network RequirementsAgent Network RequirementsCredentialed Scanning Network RequirementsAPI Network RequirementsHow DeepSurface Scans WorkDomain (LDAP) ScanningHost Scanning RoutineReasons for the Administrative Access RequirementEndpoint Protection ConsiderationsOther ItemsScope of Data Storage and RetentionIPS/IDS ConsiderationsLoggingResetting the DSADMIN passwordProduct InformationChangelogsOpen source LicensesEnd 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:

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:
- 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"


- 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

- 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.

- 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.
