DeepSurface: Microsoft LAPS

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)

DeepSurface supports Microsoft’s LAPS tool as a method of privileged access management that can be used when DeepSurface performs Authenticated Scanning of your Windows hosts.

How it Works:

If your organization has enabled LAPS as the method for managing local Administrator account passwords, you can configure a Scan Credential in DeepSurface to use LAPS for accessing the local Administrator passwords for the associated hosts. To use this feature, a configured LAPS credential should be added to the desired Scan Group(s) prior to running an Authenticated Scan.

When performing an Authenticated Scan of a host with LAPS configured, DeepSurface will first connect to a domain controller using the provided Scan Credentials. Upon successfully authenticating to the domain controller via LDAP, DeepSurface will retrieve the LAPS-managed local Administrator password for each host, as needed. DeepSurface will use the obtained local Administrator credentials to authenticate to each host while performing DeepSurface scanning tasks. This can improve the security of scans by avoiding the exposure of domain credentials to each individual host.

Windows Environment Configuration Requirements:

• LAPS must be installed on each host and domain group policy must be configured to support this. For more information, see: Microsoft LAPS Installation
• DeepSurface must be able to access LDAP on at least one domain controller of the configured domain using port 636 or 389.
• At least one domain controller must have a properly configured TLS certificate.
• The provided Scan Credentials must include privileges that allow DeepSurface to retrieve the host credentials in the domain group with LAPS support configured.

Configuring your Scan Credentials in DeepSurface:

• Select a LAPS supported Credential protocol: SMB, SMB/WMI, or WinRM w/ PSRP.
• Optionally add a Custom Label.
• Add the name of the Domain associated with the credential. This is required for any Scan Credential with LAPS configured.
• Enter the username of the domain user and associated password.
• Select LAPS as the PAM Type.
• If you have configured LAPS to manage a local user account name other than “Administrator”, be sure to change the value in the DeepSurface “LAPS Local User” field to match.
• Note that for a scan using LAPS to work, you must have previously scanned a Domain Controller associated with the given Domain, or scan the Domain Controller in the same scan as the scan that is using LAPS to authenticate on hosts.