Structured data scan limitations
Forcepoint DSPM applies limits to the size of a structured data scan so that scans complete reliably. Limits are based on the size of the selected scan scope, including the number of tables, columns and trustees (users and groups).
Before a database scan starts, Forcepoint DSPM checks the size of the selected scope against the technical limits of the platform and the limits of your subscription plan. Validation completes quickly, so scans within limits start without noticeable delay.
Validation runs when you:
- Save a new or updated scan configuration for a supported database data source.
- Start a database scan.
If the scope is within limits, the configuration is saved and the scan runs as normal. If the scope exceeds a limit, the configuration is not saved or the scan does not start, and a notification identifies which limit was exceeded
Connector supportPre-scan validation is managed per connector.
| Database connector | Pre-scan validation |
|---|---|
| PostgreSQL | Enabled by default |
| MySQL | Enabled by default |
| Oracle | Enabled by default |
| Microsoft SQL Server | Enabled by default |
| IBM Db2 | Enabled by default |
| SAP ASE | Enabled by default |
| Databricks | Not enabled by default |
| Snowflake | Not enabled by default |
| Teradata | Not enabled by default |
To enable validation for a connector where it is not enabled by default, contact Forcepoint Support or your account team.
If a scan is blockedIf a scan configuration or scan is blocked because it exceeds scan limits, do one or more of the following:
- Narrow the scan scope. Instead of scanning the entire data source, select [Specific Path / confirm UI label] and choose fewer databases, schemas or tables.
- Split the scan. Create multiple scan configurations, each covering a portion of the database.
- Review your plan. If you regularly need to scan larger databases, contact your Forcepoint account team to discuss plan options.