DeepSurface: Sensitive Assets: Polices

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)

Sensitive Asset policies are a powerful way to automate sensitive asset tagging in your environment. While it is still possible to manually search for and tag sensitive assets, policies make that process much simpler. DeepSurface comes with 3 default policies already included in the application. These policies are meant to serve as a starting point for creating more detailed and specific policies that better suit the specifics of your environment.

Based on the filters for a specifc policy (which will go over in a moment) the policies interface attempts to create a sentence that explains what the policy is doing in a user-friendly way. The different sections of the policy are color-coded to correspond to the different sections of the filter that form the policy.

• Green corresponds to the impact score portion of the filter
• Blue corresponds to the scope portion of the filter
• Purple corresponds to the tag portion of the filter
• Red corresponds to asset/node portion of the filter

The filters for a given policy tell DeepSurface what to look for when attempting to automate sensitive asset tagging. DeepSurface will run the policy initially when it is created, but also any time scans and analysis are run. Therefore, any newly discovered hosts and assets are automatically tagged if they fit into a policy.

Because of the nature of sensitive asset policies, it is possible that policies can overlap or even contradict each other. Therefor it is possible to set the policy priority order by dragging and dropping the policies within the list. The policies at the top of the list will take precedence over the policies at the bottom of the list.