DeepSurface: Base Network Requirements
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)
No matter the scanning or API configuration of the DeepSurface RiskAnalyzer appliance, a certain amount of network access is required:
updates.deepsurface.com
The DeepSurface Main Console must be able to reach port 443 of the updates server to receive both software updates as well as daily vulnerability/patch/rule data streams. This access can be configured to use an HTTP proxy, if required. Note that automatic software updates can be disabled if desired, but the same network access is required when manually upgrading.
pypi.org
The DeepSurface console uses Python, and access to the Python package repositories are required on HTTPS (TCP port 443). The servers used may vary, but as of this writing, these include: pypi.python.org, pypi.org, pythonhosted.org, and files.pythonhosted.org.
Ubuntu and Debian Package Servers
The base operating system deployed on the DeepSurface appliance must be able to reach the package servers for both Ubuntu and Debian. This allows the VM to install security updates and install additional packages, as required. The host names and IP addresses of these servers vary over time. Typically egress access to these servers is opened by default in popular firewall software. If you are experiencing difficulty with software updates, consult the /etc/apt/sources.list file on your DeepSurface appliance to identify the server names that must be accessible.
HTTPS and SSH Services
The DeepSurface Main Console exposes SSH (TCP/22) and HTTPS (TCP/443) for the purposes of configuration and administration. DeepSurface Administrators must be able to reach these ports to perform essential tasks.
HTTPS on TCP/44305
DeepSurface Subordinate VMs, if in use, connect to this port on the Main Console in order to communicate status and submit scan results. These communications would typically occur over the internal network or a VPN link. For more information on how subordinates are used, see the Deployment Options guide.