Help Center
File Audit Endpoint Security File Analysis Risk Analysis Release NotesQuick Start
- System requirements
- Minimum privileges required
- Default port configuration
- Installing DataSecurity Plus
- Uninstalling DataSecurity Plus
- Starting datasecurity plus
- Launching datasecurity plus
- Configuring your solutions
Setting up File Audit
Dashboard
Reports
Alerts
Incidents
Advanced configurations
- Predefined audit reports
- Creating new audit reports
- Creating new alert profiles
- Creating new incident profiles
- Configuring exclusion-based settings
- Configuring retention and archive settings
Setting up Endpoint Security
Reports
Advanced configurations
- Predefined policies
- Creating new policies
- Predefined audit profiles
- Creating new audit profiles
- Predefined incident profiles
- Creating a new incident
- Exclude configuration
Setting up File Analysis
Dashboard
Reports
Incidents
Configuration
Setting up Data Risk Assessment
DashboardReports
Advanced configuration
- Predefined policies
- Creating new policies
- Predefined rules
- Creating new rules
- Creating new incident profiles
- Scan configuration
About DataSecurity Plus
How-To
Quick Start File Audit Endpoint Security Risk Analysis File Analysis About DataSecurity Plus Release notes Contact usContact us
2019
2018
2017
2016
2015
Account Logon » Default Port Configuration
Scan configuration
Follow the steps below to configure new data discovery scan schedules:
- Click the Risk Analysis tab. Go to Configuration > Scan Configuration > Schedule.
- Click + Add Schedule in the top-right corner.
- Name the schedule and include an appropriate description.
- Choose the policies to be scanned.
- Select the shares to scan.
- Select the OneDrive folders to scan.
- Enable Incremental File Scan.
- Enter Schedule Duration.
- Select the Starting Date.
- Specify the exclusion timing.
- Click Add.
- Click Save.
Tip:Always choose the incremental file scan option unless it's a one-time scan. This reduces the runtime by scanning only new or modified files.
Tip: Data discovery by itself is a CPU intensive task. Add the most critical business hours to exclusion timings to minimize disruptions in productivity.