DeepSurface: Azure Cloud

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)

Installing DeepSurface on Azure

Installing the DeepSurface console into Azure Cloud is easy. Initial minimum requirements to start the installation process are the following items:

1. An Azure Cloud account. You can sign up for Azure cloud here, and can start with $200 in free trial credits if you have not signed up for Azure cloud in the past - it will require a credit card to start that they do not initially charge, but will incur charges after the free trial credits are expended.
2. A DeepSurface RiskAnalyzer License. You can request a license here.

To Begin

Log into your Azure Cloud account, and from the home page type ‘Marketplace’ into the search bar and select the Marketplace icon that appears:

In the Marketplace search bar, type in deepsurface and hit enter. The DeepSurface RiskAnalyzer Virtual Machine will appear. Click ‘Create’ and select ‘DeepSurface Vulnerability RiskAnalyzer (BYOL)’:

If you do not have an Azure subscription, it will direct you to start one - select the appropriate link from the screen that appears as befits your situation:

If you have a subscription, or after you set up your subscription or free trial, it will guide you through the process of setting up a Virtual Machine.

Create Virtual Machine

When creating a DeepSurface RiskAnalyzer virtual machine, keeping the recommended settings is best practice. The required settings that Azure imposes should be evaluated for your environment and your company’s standards. Some points to consider:

1. Resource Group: Selecting the correct resource group determines the whether the machine is accessible by those needing to administer it. Resource group selection should adhere to your company’s standards.
2. Virtual machine name: What is selected becomes the virtual machine’s resource name and host name initially - the resource name cannot be changed; the host name may be changed as Microsoft allows that, but it is not recommended. Select a machine name that fits your company’s naming standards.
3. Zones and sizing: You can add additional zones and can increase the size of the virtual machine, but it is not recommended to reduce the size of the virtual machine.
4. Authentication type: The virtual machine runs a Linux operating system, and as such best practice is to use SSH key pairs to authenticate to the shell of the operating system using an SSH client such as OpenSSH or Putty. Azure can create a new key pair for you that you can download, or you can upload your own public key. The Username you select by default starts as ‘azureuser’ but can be changed to fit your needs. You will also need to enter a value in the Key pair name field.
5. Disks: Disk size should be evaluated for your environment. Default setting is 30GB, but if you have a large number of hosts, you will more than likely want to increase that value. Consult with DeepSurface support to decide on an appropriate disk size if you are unsure. The remaining disk options should be left as default.
6. Networking: Selecting or creating the appropriate network VPC for your VM is critical. The virtual machine itself has pre-configure network security group rules appropriate for the function of the VM, however what public IP you select, if any, and what Virtual network you attach the VM to must be thought through to ensure the VM can reach your vulnerability scanner, and the hosts that are scanned by DeepSurface can reach the VM itself.

When the VM is set up to your specification, click ‘Review + Create’. This will give you a summary of what Azure will do to create the virtual machine. If the settings displayed are to your liking, click ‘Create’. Azure will begin the process of bootstrapping the VM.

Setting up the DeepSurface Console

After the VM bootstrap is complete, it is time to set up the console.

1. Click the button labelled ‘Go to Resource’ after the VM deployment is complete.
2. In the window that appears, find the ‘Networking’ section under ‘Properties’ and get the public IP or the private IP (if you can get inside the private network via VPN or otherwise), and use SSH to log into the VM’s shell.

Register your DeepSurface Analyzer instance

Proceed to Installation using an OVA to register with DeepSurface and begin the system initialization process.