Administrator Guide

9.9
- 9.9.4
- 9.9.3
- 9.9.2
- 9.9.1
- 9.8.4
- 9.8.3
- 9.8.2
- 9.8.1
- 9.8.0

Back Next

Predefined Security Rule Sets

You can use predefined security rule sets with the generic database node if you want to run commands that alter the user context. The rule set captures the commands and updates the Dynamic Data Masking symbols for the session.

You must configure Dynamic Data Masking to direct the database request to the predefined rule set before the request goes to the user-defined masking rules.

Dynamic Data Masking includes predefined rule sets for the following databases:

Greenplum: You can find the predefined security rule set for a Greenplum database in the following location:
<Dynamic Data Masking installation>\Wrappers\ImpersonationRules\GreenplumRS.xml
MySQL: You can find the predefined security rule set for a MySQL database in the following location:
<Dynamic Data Masking installation>\Wrappers\ImpersonationRules\MySQL.xml
Netezza: You can find the predefined security rule set for a Netezza database in the following location:
<Dynamic Data Masking installation>\Wrappers\ImpersonationRules\Netezza.xml

If you execute commands that alter the user context, you might want Dynamic Data Masking to skip one or more of the impersonation commands. To skip an impersonation command, create a security rule that sets the symbol value to DDM_SYSTEM_COMMAND1. Dynamic Data Masking skips, and does not execute, any impersonation command that uses a symbol whose value is DDM_SYSTEM_COMMAND1. For example, on a Netezza database, if you want to skip the command that uses the AUTH_CURRENT_SCHEMA symbol, you would create a rule with the following rule action:

The Action Type is Define Symbol. The Symbol Name is AUTH_CURRENT_SCHMEA. The Symbol Value is DDM_SYSTEM_COMMAND1. The Keep Per Session value is YES.

Rename Saved Search

Table of Contents

Administrator Guide

Administrator Guide

Predefined Security Rule Sets

Predefined Security Rule Sets