To begin using Continuous Compliance in DCT, configure the execution infrastructure, connect your data sources, and define how sensitive data should be discovered and masked.
Continuous Compliance enables teams to centrally manage masking configuration while distributing execution across scalable infrastructure. Before running compliance jobs, you must set up the infrastructure, connect data sources, and configure policies that determine how sensitive data is identified and protected.
If you have existing Compliance Engine jobs, see Migrate jobs from Compliance Engines to DCT.
The following workflow outlines the typical steps for setting up and using Continuous Compliance.
Continuous Compliance workflow
Continuous Compliance typically involves three phases: infrastructure setup, data discovery, and data protection.
1. Set up the infrastucture
Configure the infrastructure and connections required to run compliance jobs.
-
Set up infrastructure
Configure Job Orchestrators and register Compliance Nodes that provide execution capacity for compliance jobs.
-
Connect data
Create connectors that allow DCT to access the data sources that will be discovered and masked.
-
Prepare data
Configure database permissions and metadata required for discovery and masking operations
2. Identify sensitive data
Discover and classify sensitive data in connected data sources.
-
Identify sensitive data
Use data classes, classifiers, and discovery policies to detect sensitive information such as personal data, financial data, and other regulated data types.
3. Secure and use masked data
Apply masking policies and run compliance jobs to protect sensitive data.
-
Secure sensitive data
Configure masking policies by defining algorithms, and rule sets.
-
Run compliance jobs
Create and execute compliance jobs that apply masking policies to the selected datasets.
-
Provision masked data
Deliver masked datasets for downstream use, such as development, testing, and analytics.
Next steps
After reviewing this workflow, continue with the following sections to configure Continuous Compliance in your setup: