Create a Discovery Job

You can create discovery jobs for relational databases (e.g., Oracle, PostgreSQL, etc.).

When a discovery job runs, it applies all of the recognition logic specified in the discovery policy to each data element present in the rule set. The behavior of the discovery is also influenced by several application settings, refer to the ASDD group settings section.

Discovery can use rule sets with either Mask or Tokenize purpose. The rule set's purpose may affect the discovery behavior, with additional validations or processing applied based on the rule set's purpose. Discovery assigns each sensitive data element to a data class, with each data class having a default masking or tokenization algorithm. Then, in the inventory, algorithms can be manually updated as needed to establish the rule sets for your data sources.

Steps

1. In the left navigation pane, click Compliance Jobs.

2. Click Actions > + Discovery Job.

3. In the Details step:

   1. Enter the job name and (optional) description.

   2. To add tags, enter a Tag Key and Tag Value, then click + Tag.

4. Click Next.

5. In the Configuration step:

   1. Multi Tenant: Check the box if the job is for a multi-tenant database. This option allows existing rulesets to be re-used to mask identical schemas via different connectors. The connector is selected at job execution time.

   2. Select the Rule Set (must be a DCT-managed rule set). Discovery can use rule sets with either Mask or Tokenize purpose.

   3. Multiple Profiler Expression Check: Check this box if the job should assign a default algorithm if multiple classifiers match in different data classes with the same level of confidence. The discovery report will indicate multiple matches and the algorithm specified by the DefaultMultiphiAlgorithm application setting will be assigned.

   4. Select a Discovery policy.

   5. Clear previous auto domain assignments: Checking this setting would reset or clear the data class assignments for the columns (with 'Enable Automatic Updates' enabled) from previous runs.

   6. Number of Streams: The number of parallel streams to use when running the jobs. For example, you can select two streams to discover two tables in the ruleset concurrently in the job instead of one table at a time. By default, it sets DefaultStreams value from Application settings under group "mask".

   7. Feedback Size (optional): The number of rows to process before writing a message to the logs. Set this parameter to the appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual number of rows in a job, the progress for that job will only show 0 or 100%.

   8. Min Memory (MB) (optional): Minimum amount of memory to allocate for the job, in megabytes.

   9. Max Memory (MB) (optional): Maximum amount of memory to allocate for the job, in megabytes. When an ASDD discovery policy is selected, the max memory for the job must be at least 1024MB for each stream. For example, if No. of Streams is 4, this value would need to be 4096 or higher.

6. Click Next.

7. In the Summary step, review the job configuration.

8. If you need to make changes, click Back to update the previous steps. Otherwise, click Submit.