Continuous Compliance in the DCT supports discovery and masking for a range of database platforms and file-based sources. The current DCT release supports connectors for distributed databases, file connectors, and mainframe datasets.

  • Extended connectors (such as FEML-based sources) are not currently supported in DCT.
  • Password vault integrations and Kerberos authentication are not currently supported for DCT-managed connectors.

File connectors

File connectors let DCT Compliance access flat data files for discovery and masking. DCT supports the following file connector types:

  • Mainframe connectors — use FTP or FTPS to connect directly to IBM z/OS MVS datasets, SFTP to connect over SSH, Mount to connect through a locally mounted file system, or AWS S3, other S3-compatible storage, and Azure Blob Storage when mainframe data is staged in object storage.

  • FTP / SFTP connectors — connect to file servers over FTP or SFTP.

  • Cloud file connectors — connect to cloud object stores (Amazon S3, S3-compatible, Azure Blob Storage).

  • Mounts — connect via NFS/CIFS mounts (VM-based engines) or external mounts (containerized engines in Kubernetes).

Standard connectors

Standard connectors are bundled with the DCT and require no separate installation.

Distributed databases

  • Db2 LUW (Linux, Unix, Windows)

  • Db2 iSeries

  • Db2 z/OS

  • Oracle

  • Microsoft SQL Server

  • MySQL

  • SAP ASE (Sybase)

  • PostgreSQL

  • MariaDB

DCT also supports the following PostgreSQL-compatible or managed database platforms:

  • CockroachDB

  • Amazon RDS for PostgreSQL

  • Amazon Aurora PostgreSQL

  • YugabyteDB

For a complete breakdown of versions, supported features, and compatibility details, refer to the dedicated documentation pages for each connector.

  • Database Masking applies only to physical tables within databases. It does not support masking for other types of database objects such as views, materialized views, federated systems, or proxy objects. Ensure that all data requiring masking resides within physical tables to utilize the masking functionality effectively.
Last updated
Oct 8, 2026