The Masking definitions page shows information related to Masking definitions of a Data masking plan and its Blocks.
|Table of contents
|Create Masking definition
|Edit Masking definition
|Delete Masking definition
|View Block details
Masking definition is used for generating or defining masked data. It consists of Blocks that contain Generators and are executed under specific conditions. Masking definitions can be used in:
Masking tasks or
Other Masking definitions
The Masking Definitions list contains definitions for masking. Details about the selected Masking definition are displayed in the Details section:
Figure 1: Masking definitions
To create a new Masking definition, click Create masking definition button. A new pop-up is displayed. It allows entering information about the new Masking definition:
Figure 2: Create Masking definition - inputs
Inputs of a Masking definition are defined by Name and Type. User can add as many inputs as needed for wanted masking. Types can be specified as generic (basic) types or CLR (advanced) types.
Generic input types are:
CLR (advanced) input types are displayed by turning on the Advanced view. CLR types are:
Figure 3: Create Masking definition - outputs
Outputs of a Masking definition are defined by Name and Type. User can add as many outputs as needed for wanted masking. Types can be specified as generic (basic) types or CLR (advanced) types.
Generic output types are:
CLR (advanced) output types are displayed by turning on the Advanced view. CLR types are:
Figure 4: Create Masking definition - repeater
*Repeater contains values that, once created and saved in the database, can be used again so that the same original value ('RepeaterKey') is always replaced with the same masked value ('RepeatingValue'). While creating Masking definition, user can specify if repeaters will be used and additional information about them:
Repeater name - repeater name is automatically generated according to the name of masking definition and will be used in conjunction with repeater store configuration.
Is unique - If 'Is unique' is set to true, then different output is always generated.
Is persisting - If 'Is persisting' is set to true, then information about the repeater is saved as a list of values identified by name and they contain a key and its belonging value. That specific repeater can then be used in future maskings.
Once a Masking definition is registered, all information can still be edited. Click on Edit Masking definition in the Details section and a pop-up window will be displayed. In the Edit context all fields are editable.
Figure 5: Edit Masking definition
Masking definition can be deleted by selecting 'Delete Masking definition' in the Details section. The delete Masking definition confirmation dialog will be displayed and Masking definition will be permanently deleted after confirming the dialog.
Figure 6: Delete Masking definition
Blocks are used as decision making statements of a Masking definition. Those decisions are made by using "Run condition" and order of Blocks in the Masking definition. Each Masking definition can have multiple Blocks, but at least one is required.
Blocks consist of two parts:
Blocks of a specific Masking definition are displayed in an overview table, displaying details about them:
Figure 7: Blocks
One Block is automatically created upon creating a Masking definition. To register a new Block, click Create Block button. A new pop-up is displayed. It allows entering information about the new Block:
Name - name of the Block
Note - description of the Block
Status - status of the Block. Possible statuses are:
Enabled - block may be executed according to its run condition
Disabled - block will not be executed.
Is default - marks the Block as default. That Block runs in case no other Blocks are executed because of their run condition.
Run condition - condition that needs to be fulfilled for Block to execute.
Run always - condition that is automatically set to 'True'
Custom condition - used for specifiying more complex conditions using C#.
Figure 8: Create Block
Once a Block is created, all information can still be edited. Select Edit Block from the context menu and a pop-up window will be displayed. In the Edit context all fields are editable.
Figure 9: Edit Block
Blocks can be deleted by clicking on 'Delete Block' from the context menu. The delete Block confirmation dialog will be displayed, and Block will be permanently deleted after confirming the dialog.
Figure 10: Delete Block
Blocks will be executed in certain order, based on their place on list and their run condition. Order of Blocks in the list can be changed by using drag & drop method.
For every created Block, which is displayed in Blocks Overview table, Block details, all its created Generators and Assignments can be viewed through option 'View block details' in the context menu.