Import a masking algorithm
Overview
Algorithms can be imported from an on-prem Continuous Compliance engine into Delphix Compliance Services, in the form of a protobuf object. This process is used with Delphix Compliance Services to achieve consistent masking across both products. When transitioning from on-prem to Delphix Compliance Services, importing algorithms from Continuous Compliance eliminates any change in the way your data is masked.
To import an algorithm, an on-prem Continuous Compliance user can call the export API (from the on-prem masking APIs) to retrieve a JSON file containing metadata and a serialized protobuf blob of the on-prem algorithm object.
Currently, Delphix Compliance Services only supports importing algorithms from on-prem engines. Thus, object_type USER_ALGORITHM should be used while exporting engine sync files from an on-prem Continuous Compliance engine. This algorithm object includes the following fields:
Name
Framework (component) name
Config json
Key
Associated lookup files
All of the algorithm frameworks supported are listed in the verview
Algorithms can be imported from an on-prem Continuous Compliance engine into Delphix Compliance Services, in the form of a protobuf object. This process is used with Delphix Compliance Services to achieve consistent masking across both products. When transitioning from on-prem to Delphix Compliance Services, importing algorithms from Continuous Compliance eliminates any change in the way your data is masked.
To import an algorithm, an on-prem Continuous Compliance user can call the export API (from the on-prem masking APIs) to retrieve a JSON file containing metadata and a serialized protobuf blob of the on-prem algorithm object.
Currently, Delphix Compliance Services only supports importing algorithms from on-prem engines. Thus, object_type USER_ALGORITHM should be used while exporting engine sync files from an on-prem Continuous Compliance engine. This algorithm object includes the following fields:
Name
Framework (component) name
Config json
Key
Associated lookup files
All of the algorithm frameworks supported are listed in the verview
Algorithms can be imported from an on-prem Continuous Compliance engine into Delphix Compliance Services, in the form of a protobuf object. This process is used with Delphix Compliance Services to achieve consistent masking across both products. When transitioning from on-prem to Delphix Compliance Services, importing algorithms from Continuous Compliance eliminates any change in the way your data is masked.
To import an algorithm, an on-prem Continuous Compliance user can call the export API (from the on-prem masking APIs) to retrieve a JSON file containing metadata and a serialized protobuf blob of the on-prem algorithm object.
Currently, Delphix Compliance Services only supports importing algorithms from on-prem engines. Thus, object_type USER_ALGORITHM should be used while exporting engine sync files from an on-prem Continuous Compliance engine. This algorithm object includes the following fields:
Name
Framework (component) name
Config json
Key
Associated lookup files
All of the algorithm frameworks supported are listed in the Pre-set Masking Algorithms article.
Prerequisites
A Continuous Compliance engine on version 6.0.13.0 and above is required, simply export the algorithms of the frameworks that Delphix Compliance Services supports. If the exported file is encrypted, provide the passphrase in Delphix Compliance Services to decrypt the file while importing.
The following algorithm instances/frameworks are not yet supported:
Secure Shuffle
Mapping
Dependent Date Shift.
Interface
Select the Import button located on the Algorithms page in Delphix Compliance Services, then use the dialog to select a file for import.
Naming rules
When accessing an algorithm in a Continuous Compliance engine, the algorithm name displayed in the edit or view details dialog may differ from the name displayed in the table. For instance, the item "ADDRESS LINE 2 SL" is listed as "AddrLine2Lookup" in the dialog, which is a name that may be used in DCS.
Upon importing algorithms into DCS, any algorithm name with the prefix "dlpx-core:" will have the prefix removed. For instance, "dlpx-core:CM Digits" will become "CM Digits."
In addition, DCS does not permit duplicate algorithm names. If duplicates are detected after any necessary prefix removal, a three-digit number will be added as a suffix to distinguish between them. For example, "CM Digits 001," "CM Digits 002," and so on.
‘Created by’ field of imported algorithms
The ‘Created by’ field is set to be the `exportHost` attribute in the exported file from the masking engine. Usually, it is the domain name of the masking engine.