Skip to main content

Privacera Documentation

Table of Contents

Privacera Discovery scan targets

Privacera Discovery crawls targeted data sources to identify and applies metadata labels called tags to potentially sensitive data, such as credit card numbers or email addresses.

Access Manager Tag Policies can then be created so that user access can be controlled and monitored.

Privacera Discovery is enabled by default.

Disable or reenable Privacera Discovery on PrivaceraCloud

Privacera Discovery is enabled by default.

The account owner or the administrator can disable or reenable Privacera Discovery.

To disable or reenable Privacera Discovery:

  1. Go to Settings > Account.

  2. Under the Discovery heading, toggle Enable Discovery to ON or OFF.

Connect Applications

You can configure the applications supported by Privacera Discovery in Settings > Applications . For more information, see Data sources on Privacera Platform.

Discovery scan targets

After an application has been connected, subsets of that data can be configured as scan targets.

To define a Privacera Discovery scan target:

  1. To add specific databases and tables to be scan targets, go to Discovery > Data Source.

  2. Click the desired application in the Applications section.

  3. Click ADD to define a subset of that Datasource for scanning.

    • Enter the database name (database or for Snowflake database.schema) or wildcard asterisk for all databases.

    • Enter one or more comma-separated table names or wildcard asterisk for all tables. Wildcard asterisks can also be used in table names as prefix, suffix, or inside the name.

Start a scan

After a scan target is established, it can be scanned. Each database/table set is listed by row, under Scanning Details. The columns are: Database, Tables, and Actions.

To start a scan, click SCAN RESOURCE.

The following message is displayed:

Scan request is in the queue, please check after 2 minutes.

View a scan

Completion status and various statistics for all scan Discovery > Scan Status.


  • During JDBC database scanning, data for binary type columns is skipped and only non-binary columns data is scanned.

  • During JDBC database scanning, data for string or text column types is trimmed to avoid Out of Memory error.