Compliance jobs execute configured discovery, masking, tokenization, or re-identification workflows on selected data sources.
Non-conformant data handling is available for masking jobs only. The setting supports Use global setting, Fail on encounter, Don't mask value, and Set value to null. In the API, the field name is non_conformant_data_handling. Use the Create a masking job or Edit a Compliance job task to configure it.
When a compliance job runs, the job is deployed to a compliance node associated with the Job Orchestrator. The system processes the selected rule set and performs the configured operation:
-
Discovery jobs scan the defined tables and columns to identify sensitive data based on configured classifiers and discovery policies.
-
Masking jobs apply the configured masking algorithms to the identified columns and write the transformed data back to the target system.
-
Tokenization jobs apply tokenization algorithms to identified columns, replacing sensitive values with tokens and writing the tokenized data back to the target system.
-
Re-identification jobs reverse the tokenization process by replacing tokens with their original values and writing the re-identified data back to the target system.
You can migrate existing Masking, Tokenization, and Re-identification jobs from a connected Compliance Engine to DCT. Profile jobs are not eligible. See Migrate jobs from Compliance Engines to DCT.
Running compliance jobs enables organizations to discover, classify, and protect sensitive data across data platforms used for development, testing, analytics, and other non-production use cases.
You can perform the following operations:
Create a discovery job for files
Create a masking job for files
Compliance Job Execution report (Preview)