DeepSurface: Multiple Vulnerability Sources
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)
Multiple Vulnerability Sources
When multiple vulnerability sources are integrated with DeepSurface, it is likely that duplication of vulnerabilities and hosts will be transmitted to the DeepSurface console. The RiskAnalyzer does attempt to de-duplicate data, with the following caveats:
First the DeepSurface needs to uniquely identify each device. This can be challenging if the data we receive from a vulnerability source is incomplete, but we try several methods to cluster identifying information.
Next, a "vulnerability instance" (host + vulnerability) is considered to be unique if the same device has the same vulnerability across multiple scanners' output.
If some scanners report the vulnerability, but others don't, we assume the vulnerability DOES exist. So if any scanner reports a vulnerability on a given device, then we assume the vulnerability instance exists.
Even though we de-duplicate these vulnerability instance reports, you can still filter the data in some of our reports to show vulnerability instances only from a specific source. This can be a great way to compare coverage and accuracy of your various tools.
Uniquely identifying devices is the hardest part. If one of your vulnerability scanners fails to gain authenticated access to a device, often the identifying information for the device will be unreliable. We do use things like hostnames and IP addresses in this case, but IP addresses are not always reliable because a single device may have multiple dynamic addresses (think WiFi, VPN clients that come and go, etc) that may be duplicated as the IP address leases expire, or if the interface for a device uses some sort of non-static MAC address. Hostnames are only available in this case if reverse DNS or NBNS (or something similar) is available and configured.