Supported connectors

The Continuous Compliance supports profiling, masking, and tokenizing a wide range of data sources including distributed databases, mainframes, PaaS databases, and file formats. These connectors fall under two categories:

  • Delphix connectors (Standard, Select, and Premium): These are built-in connectors within the Delphix Continuous Compliance Engine, designed to natively support profiling, masking, and tokenization. Standard Connectors are included with the Delphix Continuous Compliance Engine by default. Select and Premium Connectors are optional add-ons that require separate installation and configuration.

  • FEML-based sources(File Extract, Mask, and Load): FEML is a technique used for sources that lack dedicated connectors. It leverages the source system’s APIs to extract data into files, applies masking on the extracted files, and then reloads the masked data back using those same APIs.

Standard connectors

Standard connectors are bundled with the Delphix Continuous Compliance engine and require no separate install.

Supported Sources:

  • Distributed database: Db2 LUW, Oracle, MS SQL, MySQL, SAP ASE (Sybase), PostgreSQL, MariaDB

  • Files: Fixed Width, Delimited, XML, JSON, Parquet

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

Select and premium connectors

Select and premium connectors require separate installation. They include support for additional data sources not bundled in the Continuous Compliance Engine.

Supported Sources:

  • Distributed database:

  • Mainframe/Midrange: Db2 Z/OS, Db2 iSeries, Mainframe data sets.

For a complete breakdown of versions, features, and compatibility details, refer to the dedicated 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.

  • Structured documents i.e. JSON and XML that are stored in database columns and delimited files can be masked using Document Store Type masking.