Help CenterFile Audit Endpoint Security File Analysis Risk Analysis Release Notes
- 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
- 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
Setting up File Analysis
Setting up Data Risk AssessmentDashboard
About DataSecurity Plus
How-ToQuick Start File Audit Endpoint Security Risk Analysis File Analysis About DataSecurity Plus Release notes Contact us
Since the File Analysis module doesn’t offer real-time information, incidents will only be recognized when the scheduled scans are run. By default, the below cases will be raised as incidents:
Low Disk Space: An incident is created when the available disk space falls below 10 percent.
Inactive Files with Sensitive Data: An incident is raised when PII/ePHI is detected in inactive or stale files.
Note:The Inactive or Stale files configuration can be changed by following the steps in this guide.
Duplicate Files with Sensitive Data: An incident is raised when PII/ePHI is detected in duplicate files.
Open Access Files with Sensitive Data: An incident is created when PII/ePHI is detected in files with unrestricted access to users.] Not for Beta
Ransomware File Types: An incident is raised when known ransomware file types are found.
For steps on configuring or adding a new incident, click here.