The purpose of the Catalog Masking mechanism is to perform masking based on the Catalog's Classifications. It provides a great simplification of the masking implementation, since it allows to base the masking logic on the Discovery results in the Catalog rather than defining it manually in each LU table population.
To apply the Catalog Masking mechanism on either a flow or a population, start with running the Discovery job and building the Catalog artifact. Then, create an LU and add either the CatalogMaskingMapper Actor or the CatalogMaskingRecord Actor to LU populations.
The following 3 actors have been introduced by the Catalog Masking mechanism:
Their purpose is to mask the values based on the Catalog’s Classification and the masking rules definition. The object (or record) to be masked is set, using the following 3 actor’s input parameters that identify it in the Catalog: dataPlatform, schema and dataset.
The Catalog-based masking logic is included in the CatalogMaskigField Actor while the CatalogMaskingMapper and the CatalogMaskingRecord Actors serve as a wrapper - on a dataset level and a record level respectively.
The CatalogMaskingMapper Actor receives a dataset, which maps the data on the fly, and does not load the entire dataset to memory; this actor iterates internally on each record and invokes the CatalogMaskingRecord Actor. The CatalogMaskingMapper Actor returns a dataset with the same structure it was received.
The CatalogMaskingRecord Actor receives a record, splits it internally into key-value pairs and invokes the CatalogMaskingField Actor for each pair. The CatalogMaskingRecord Actor returns an object with the same structure it was received.
The CatalogMaskingField Actor’s purpose is to mask a single field’s value based on the Catalog’s Classification and the masking rules definition.
While the Classification and PII properties are added to the Catalog nodes by the Classifier plugins, the Masking property should be added manually when it is required to control the masking mechanism of some fields.
The purpose of adding the Masking property to a field is to override the Classification level definitions. This property indicates that this field requires special handling by the Catalog Masking mechanism. The Masking property can have one of the following valid values:
The purpose of the Catalog Masking mechanism is to perform masking based on the Catalog's Classifications. It provides a great simplification of the masking implementation, since it allows to base the masking logic on the Discovery results in the Catalog rather than defining it manually in each LU table population.
To apply the Catalog Masking mechanism on either a flow or a population, start with running the Discovery job and building the Catalog artifact. Then, create an LU and add either the CatalogMaskingMapper Actor or the CatalogMaskingRecord Actor to LU populations.
The following 3 actors have been introduced by the Catalog Masking mechanism:
Their purpose is to mask the values based on the Catalog’s Classification and the masking rules definition. The object (or record) to be masked is set, using the following 3 actor’s input parameters that identify it in the Catalog: dataPlatform, schema and dataset.
The Catalog-based masking logic is included in the CatalogMaskigField Actor while the CatalogMaskingMapper and the CatalogMaskingRecord Actors serve as a wrapper - on a dataset level and a record level respectively.
The CatalogMaskingMapper Actor receives a dataset, which maps the data on the fly, and does not load the entire dataset to memory; this actor iterates internally on each record and invokes the CatalogMaskingRecord Actor. The CatalogMaskingMapper Actor returns a dataset with the same structure it was received.
The CatalogMaskingRecord Actor receives a record, splits it internally into key-value pairs and invokes the CatalogMaskingField Actor for each pair. The CatalogMaskingRecord Actor returns an object with the same structure it was received.
The CatalogMaskingField Actor’s purpose is to mask a single field’s value based on the Catalog’s Classification and the masking rules definition.
While the Classification and PII properties are added to the Catalog nodes by the Classifier plugins, the Masking property should be added manually when it is required to control the masking mechanism of some fields.
The purpose of adding the Masking property to a field is to override the Classification level definitions. This property indicates that this field requires special handling by the Catalog Masking mechanism. The Masking property can have one of the following valid values: