DeepSurface: Getting Started

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)

It is important to plan your DeepSurface risk analyzer deployment prior to rolling out the appliance. Several considerations are required to plan the launch of the console.

1. Will you host the console on premise or in the cloud?

Self hosting the DeepSurface console in your own cloud tenant can be done inside AWS (AWS (BYOL), AWS EC2 (Usage Based)), Azure, or Google Cloud utilizing the machine images developed by DeepSurface in those respective platforms. Access the marketplace for your cloud provider and search for 'DeepSurface'.

We also provide the option of hosting the DeepSurface console for you in our cloud environment - in this case, all the details concerning system requirements and set up are handled for you! Contact us if you would like us to host your DeepSurface console.

Using VMWare or VirtualBox or other on-premise virtualization platform uses an OVA distributed via downloadable link you can request by contacting us

.

Regardless of how you implement the DeepSurface RiskAnalyzer, select an appropriate fully-qualified domain name so that encryption communications can function and the console can be more easily managed and accessed.

2. You must have a source of vulnerability data available to import into DeepSurface.

DeepSurface supports integration with several top tier vulnerability scanners, and relies on their scanning and data collection efforts to analyze the true risk in your environment. DeepSurface combines this data with data collected by the DeepSurface agents to identify what assets are exploitable via the vulnerable attack paths DeepSurface discovers.

The list of supported vulnerability scanning platforms follows:

Vulnerability Sources
CrowdStrike Falcon Spotlight SentinelOne
Carbon Black Cloud Microsoft Defender for Endpoint
Wazuh Lansweeper Cloud
Tenable Nessus Pro Tenable VM (formerly Tenable.io)
Security Center (formerly Tenable.sc) Rapid7 InsightVM
Qualys VMDR Nozomi Guardian
Eclypsium AWS Inspector

3. Network Requirements

The DeepSurface console requires access to updates.deepsurface.com and the hosts to be scanned by DeepSurface need to communicate with the console to send scanning date. The console also must have access to the API endpoint appropriate to your vulnerability source. Firewall configurations and appropriate network routing between VLANs may be required. In the cloud the VPC or network configuration must be able to function with the correct ingress and egress paths opened to the appropriate network segments. Details regarding the network configurations for these options are found in the System Requirements

4. DeepSurface Deployment

There are several methods to deploy DeepSurface scanners, with the easiest being Agent-Based Deployment. However if that does not work for your environment or you have other controls that preclude installing DeepSurface agents onto hosts, it is vital that you review the Deployment Planning section of the documentation.

5. Digital Security

Securing the DeepSurface console itself and the digital communications it requires is documented in our Security Guide. Fundamental considerations are documented there, but as always a layered approach to security relevant to the requirements of your particular environment should be planned and implemented. Firewall Configuration, understanding How DeepSurface Scans Work, and the Other Items sections of the Security Guide should all be reviewed.