Continuous Compliance in DCT provides a centralized platform for defining, executing, and monitoring data compliance workflows. In Continuous Compliance, DCT acts as the control plane for compliance configuration. All configuration objects, such as algorithms, classifiers, rule sets, and compliance jobs, are created and managed in DCT. Execution infrastructure runs masking jobs using configuration delivered from DCT at runtime. This architecture separates configuration management from execution capacity. As a result, organizations can scale masking workloads while maintaining consistent configuration and centralized visibility.
In traditional masking deployments, each masking engine maintained its own configuration and execution history. As environments grew, maintaining consistent configuration across engines required manual coordination. This increased operational overhead and introduced the risk of configuration drift.
Continuous Compliance in DCT eliminates this challenge by establishing DCT as the single source of truth for compliance configuration and job execution history.
How different roles use Continuous Compliance
Continuous Compliance supports several roles across an organization, including platform administrators, masking developers, and application teams. The following table describes how each role interacts with the platform.
| Role | Primary responsibilities | How the architecture supports this role |
|---|---|---|
| Administrators | Operate the Compliance platform and manage execution infrastructure. | Configure Job Orchestrators, manage headless masking engines as execution capacity, and rebalance workloads without redefining compliance logic. |
| Masking rules developers | Define and validate how sensitive data is classified and masked. | Create and manage algorithms, classifications, rule sets, and jobs centrally in DCT, relying on enforced consistency and centralized execution history. |
| Application teams | Run masking jobs and consume masked data. | Execute jobs from DCT without managing infrastructure, with centralized visibility into execution status and history. |