Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking
  3. Rules
  4. Connection Rules
  5. Security Rules
  6. Security Rule Set Simulator
  7. Masking Functions
  8. Stored Procedure Result Set Masking
  9. Integration with Informatica Products
  10. Appendix A: XML Functions Reference
  11. Appendix B: Glossary

Parser Matcher

Parser Matcher

The Parser matcher identifies requests that Dynamic Data Masking is unable to parse.
You can use the Parser matcher with security rule actions to change the request. For example, if you want to block requests that Dynamic Data Masking cannot parse, you can create a rule with the following properties:
Rule Name
Enter a name for the rule. In this example, the rule name is parsed_statement.
Rule Matcher
Select the Parser matcher.
Rule Action
Select the Block Statement rule action. Enter a message that Dynamic Data Masking sends to the client when the statement is blocked. In this example the message is
UNABLE TO PARSE STATEMENT
.
Processing Action
Select Continue. The Continue processing action indicates that the Rule Engine should continue to the next rule in the rule tree.
Log When Rule is Applied
Select the
Log When Rule is Applied
check box to create an entry in the
rule.log
file if the Rule Engine applies the rule action to the request.
The following image shows the rule parameters:
The rule uses the Parser matcher and the Block Statement rule action.

0 COMMENTS

We’d like to hear from you!