Versions Compared

Old Version 5

changes.mady.by.user Kevin Wu

Saved on

compared with

New Version 6

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In the Data Masking profile, you configure the masking method you want to use, which UDR types and fields you want to mask/unmask, and any masking method-specific settings.

...

To create a new Data Masking profile, click the New Configuration button in Desktop and select the Data Masking Profile option. This configuration contains four different tabs; Fields, Crypto, Database, and Hash. The Masking Method you select in the Fields tab determines which of the other three tabs will be active , since these tabs contain masking method-specific configurations.

...

The contents of the menus in the menu bar may change depending on which configuration type that has been opened. The Data Masking profile uses the standard menu items and buttons that are visible for all configurations, and these are described in Build View.

...

Setting
Description

Masking Method

In this drop-down - list, you select which masking method you want to use;

- Crypto - which uses either AES-128 or AES-256 encryption. Can only be used for fields of string or bytearray types.

- Database Storage - which stores the unmasked and masked data in a database. Can be used for fields of byte, double, int, string, long, and short types. When selecting Database, Oracle, Postgres, and SAP HANA can be used.

- Hash - which only masks the data, i.e. it is not possible to unmask. Can be used for most simple types of fields.

Storage Fields

In this section, you add the fields you want to map the UDR fields to when using Database Storage. If you have selected another masking method, this section will be inactive.

UDR Field MappingsIn this section, you add all the UDR types and fields you want the profile to process.

...

Creating a Data Masking Profile Using the Database Storage Method

To use the database storage method, you need to create a table to store the mappings between masked and unmasked data. It is important that there are unique indexes for both the masked and unmasked data since the masking method implementation depends on the database constraints to ensure consistency in the table data.

The example below shows what a definition with a single storage field in an Oracle database may be:

Info
titleExample - A definition with a single storage field in an Oracle database


Code Block
CREATE TABLE masking_info (
    unmasked NOT NULL,
    masked NOT NULL,
    CONSTRAINT masking_info_pk PRIMARY KEY (unmasked)
);
 
CREATE UNIQUE INDEX idx_masking_info_masked ON masking_info (masked);


...