Data Discovery FAQ

Data Discovery requires a deployed worker node for worker-node scans. The worker node uses the applicable data source connector and the source's native mechanisms to perform scans. For more information, see the Worker Node Management and Deployment Guides sections in the Data Discovery Knowledge Base.

A maximum of 5 scans can be run per data source type. RDBMS sources are the only exception: at most 5 can run simultaneously across all RDBMS sources. Example: 3 Oracle and 2 SQL can run, while if 5 Oracle are run, the SQL ones will be placed in pending until the 5 Oracle have completed.

Data Discovery typically requires read-only access, but the required permissions depend on the data source. For databases, grant access to the schemas and users required to cover the intended scan scope. For SaaS products, configure OAuth-based access with the appropriate read-only permissions where supported.

After a worker node is deployed, connected data sources begin a catalog scan. This helps identify the data structure and alerts the system to the types of files in the source. Then it scans, first starting at the data element level. Once the data is profiled, metadata is sampled. For more information, see Data Discovery Architecture Overview.

Credentials are stored on the worker node, which is protected by your established security controls.

Yes, for select providers like Azure or AWS. For more information on supported platforms, see Data Discovery Deployment Options.

As the scan occurs, data is read and sent to the classification service for sampling. The sample is copied and sent to the cloud. The data is then pulled in a single batch. The scan begins with the schemas, followed by the tables, and then proceeds through the remaining scan stages.

Data is performed in memory, purely ephemeral. Once processed, the data is dropped, and metadata is populated in the cloud. Customers can dictate whether data persists based on custom classifiers or data sources.

Once the data is retrieved and scanned, it can be refreshed on an ad hoc basis and used for further discovery operations within the application.

Typically, metadata doesn't require index storage unless it is used for a DSAR request. In this instance, OneTrust would query the index storage in the cloud, then use that information to search the database and retrieve the data. When a scan begins, you have the configuration option to index store or not.

The module, OneTrust Data Discovery, is for discovering data that is unknown or has no known location. The market solution, TDD, is for targeted data searches across catalog sources. TDD does not leverage performance-based searches; instead, it knows all existing tables, data sources, etc., to look for and retrieve back to the application.