A connection rule matcher defines the criteria that the Rule Engine uses to identify incoming SQL requests that receive the connection rule action.
For example, to identify requests from a specific application, such as Toad, create a connection rule that uses the Client/Application Information matcher. Add Toad to the matcher Include List, and the Rule Engine returns a match. When a match occurs, the Rule Engine applies the rule action.
You can use the following connection rule matchers:
All Incoming Connections
The Rule Engine applies the rule action to all incoming connections.
Check Database Connection
The Rule Engine returns a match based on the availability of the database connection.
Check Database DSN
The Rule Engine returns a match based on the data source name of the database.
Check Database URL
The Rule Engine returns a match based on the URL that the client application gives for the driver.
Check Property
The Rule Engine returns a match based on a DSN property of the driver.
Check Server Name
The Rule Engine returns a match based on the name of the Dynamic Data Masking Server that sends the SQL request.
Client Information
The Rule Engine returns a match based on the client that sends the SQL request. The Client Information is available for the DDM for JDBC and DDM for ODBC services.
Client/Application Information
The Rule Engine returns a match based on the client or application that sends the SQL request. The Client/Application Information matcher is not available for the DDM for JDBC and DDM for ODBC services.
Current Target Database
The Rule Engine returns a match based on the target database of the SQL request.
Incoming DDM Listener Port
The Rule Engine returns a match based on the listener port where Dynamic Data Masking receives the request.
Incoming DDM Listener Address
The Rule Engine returns a match based on the address of the Dynamic Data Masking listener in the connection request.