Create a masking job

Use this task to create a masking job that executes the masking algorithms defined in your rule set and generates masked output files

This setting requires a Continuous Compliance engine version 2026.2.0.0 or later.

Steps

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

2. Click Actions > + Masking 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. Masking Method: Select a masking method. The available values are In-Place and On-The-Fly.

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

   4. Stop job on first nonconforming data: To abort a job on the first occurrence of non-conformant data. The default is for this checkbox to be clear.

      1. The job behavior depends on the settings specified in the Algorithm Settings page and on the individual algorithm pages that define how you view the presence of non-conforming data.

      2. The setting on the Algorithm Settings page is global and can be overridden by the setting on the algorithm page for that algorithm. These settings declare if the presence of Nonconforming data is a failure or a success for the job.

      3. If Mark job as Failed is selected as a result of the above settings then the job would be aborted on the first occurrence of nonconforming data. If Mark job as Succeeded is selected as a result of the above settings then the job will not be aborted.

   5. Non-conformant data handling: Select how the job responds when an algorithm encounters a value that does not match the expected format. Use this setting to override the global engine default for this job only.

      • Use global setting: Use the default behavior configured for the compliance engine.

      • Fail on encounter: Stop the job when a non-conformant value is encountered.

      • Don't mask value: Leave the original value unchanged when the value is non-conformant.

      • Set value to null: Replace the non-conformant value with a null value.

      On database masking jobs, selecting Set value to null for a column with a NOT NULL constraint can leave the non-conformant value unmasked without an error, execution event, or warning. Verify that target columns do not have NOT NULL constraints before selecting this option.

   6. Number of Streams: The number of parallel streams to use when running the job. This value will allow the compliance engine to process multiple tables at the same time. When a streams value is selected, the compliance engine will divide the given workload into the number of streams selected to be run in parallel. It is both likely and expected that some of these streams will complete before others and that during the job you will see the number of active streams running decline as their workloads complete.

      • Choosing the number of streams

        • Jobs, even with a single stream, will have separate execution threads for input, processing, and output logic.

        • For more information on how to improve job performance, see Masking Performance, Streams, Threads, Slice Jobs KB.

   7. Row Limit: The number of data rows that may be in process simultaneously for each stream. For file jobs, this controls the number of delimited or fixed-width lines, mainframe records, or XML elements in process at one time.

      • Setting this value to 0 allows unlimited rows into each stream.

      • Setting this value to -1 or leaving it blank will select a default limit based on rule set type.

      • Choosing the Row Limit

        • The default Row Limit values have been selected to allow typical jobs to run successfully with the default job memory and streams number settings.

        • This assumes a maximum row or record size of approximately 2000 bytes with 100 transformed columns. If the actual row or record size, or column count, exceed these values, it may be necessary to either allocate more memory to the job by increasing Max Memory, or reduce the Row Limit to a smaller value. Conversely, if the transformed rows are quite small and have few assignments, increasing the Row Limit may improve job performance. Remember to consider the worst case (the largest rows, the most assignments) table or file format in the Rule Set when making this determination.

   8. Feedback Size: The number of rows to process before writing a message to the logs. Set this parameter to the appropriate level of detail required for the logs.

   9. Min/Max Memory: Minimum/Maximum amount of memory to allocate for the job, in megabytes. It is recommended that the Min/Max Memory should be set to at least 1024.

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.