You can create and enable custom rules that determine how statements received by the DBMS are handled. Rules can be used to allow statements that match, or they can be used to generate alerts regarding statements that do not match the policy. A rule can also be used to automatically terminate potentially dangerous sessions.
Based on your organization's ongoing monitoring of potential risks, custom rules can be defined to provide protection against activity that is considered suspicious per your IT policy and to help you protect specific DBMSs according to their functionality.
For example, you might want to monitor access to sensitive tables in an HR DBMS, such as tables with employee compensation information, or you might want to protect against the usage of specific SQL query tools on production databases. Before trying to create custom rules, familiarize yourself with the Application Mapping functionality, which can save considerable time in creating custom rules.
Each rule consists of one or more comparator statements. The relationship between multiple comparator statements is based on Boolean logic, using AND, OR, or NOT.
You can define exceptions to a rule by creating an Allow rule for the exception case and placing it before the rule in the Rules list. You can also create an exception in the rule itself.