When you configure the audit log, you create both connection rules and security rules in the Management Console.
A connection rule defines the connection criteria that the Dynamic Data Masking Rule Engine uses to identify a connection and the target database. Connection rules use a matcher and a rule action to identify and route a connection. The matcher defines the criteria that the Rule Engine uses to identify a match. The rule action determines how the Rule Engine processes the matched connection.
A security rule defines the criteria that the Rule Engine uses to parse and rewrite an SQL request. Security rules consist of a matcher, a rule action, and a processing action. The Rule Engine applies security rules to incoming SQL statements to identify a match to the criteria that you define. If a match occurs, the Rule Engine applies the security action to the SQL statement.
For more information about Dynamic Data Masking rules, see the
Informatica Dynamic Data Masking User Guide.
Create the following connection and security rules to identify, route, and rewrite incoming SQL requests to the Data Vault:
Connection rule folder
Connection rule that routes all incoming connections to the rules in the folder. The folder contains the switch to database and use rule set rules.
Switch to database rule
Connection rule that routes incoming connections to the Data Vault database.
Use rule set rule
Connection rule that sends incoming Data Vault SQL requests to the security rule set that contains the log and rewrite rules.
Log rule
Security rule that logs whenever an incoming SQL request is sent to the security rule set. The Rule Engine writes this information to the
rule.log
file.
Rewrite rule
Security rule that identifies the columns that you want to trigger the audit. If these columns are included in an SQL request sent to the Data Vault, the rewrite rule also rewrites the SQL statement to append an audit tag.