DeepSurface: Agent-Based Deployment
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)
The DeepSurface agent is a small (less than 30MB resident when running) unobstrusive executable installed on hosts in your environment. The RiskAnalyzer Main Console and subordinate consoles receive communications from the agents over SSL/TLS. DeepSurface agents upgrade themselves automatically when appropriate by downloading updated versions from the DeepSurface Main Console. This deployment method requires a fully-qualified domain name (FQDN) for the Main Console and a valid SSL/TLS certificate.
Many organizations now have remote employees whose computers are not always connected to a VPN, especially during scan times. Deploying agents means that off-site hosts will still be scanned at (or close to) your scanning cadence. Scan results upload automatically when the host can reach the DeepSurface Main Console or subordinate.

To configure an agent-based DeepSurface RiskAnalyzer deployment, start by entering the DeepSurface console's FQDN in the initial setting screen. Then configure the agent settings, and copy the deployment string and download the script appropriate to the host operating system (Windows, Linux or Mac). Deploy the agent to the hosts you wish to scan using Active Directory group policies (for Windows hosts) or other orchestration service. The deployment string can be run manually on individual hosts, but that approach is not scalable in large environments. Once the agent is installed and registers with the console, it “phones home” on a configurable cadence to update its settings, its software, and to send scan data back to the console.