Skip to main content

Create Dynamic Masking Policy

To create a Dynamic Masking policy for DBMS, go to Policy > DBMS Dynamic Masking. The Add Policy button allows the user to create a new dynamic masking policy.

The following screenshot depicts the user interface to create a new policy for DBMS dynamic masking:

Dynamic masking policies in PK Protect need policy groups and masking options, which are configured under the Policy Groups and Masking Methods screens.

Provide the following details while creating a new dynamic masking policy:

  1. Policy Name: Enter the name of the policy. The name must be unique for each policy. Blank spaces and special characters except _ (underscore) and – (dash) are not allowed in this field.

  2. Policy Description: Enter a brief description for the policy. This field accepts letters, numbers, symbols as well as special characters. It can hold 256 characters.

  3. Select Policy Group (Required): This field will list down all the policy groups created under the Policy Groups screen. Select the policy group(s) with which you want to associate the DBMS dynamic masking policy.

  4. Sensitive Type List: A list of all the Pre-Defined and Custom Sensitive Types are displayed in the bottom section of the screen along with the Masking Options.


    To include the Sensitive Type(s) in the policy, check the checkbox(es) available with the Sensitive Type name. You can also select the entire group of the sensitive type. To do so, check the checkbox available with the Sensitive Group name.

    On clicking the drop-down corresponding to the selected sensitive type displays the list of all Masking Options created under the Masking Methods screen. Select the required masking option from the drop-down.

  5. Click the Save button to save the dynamic masking policy in the system, else click the Cancel button.

  6. Click Save As button to save the dynamic masking policy with the same configuration but with different name.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.