--- title: "Configure the action for a DBMS" slug: "configure-the-action-for-a-dbms-1" tags: ["Product Usage", "DS 10.x", "Database Security"] updated: 2026-09-10T15:20:30Z published: 2026-09-10T15:20:30Z canonical: "docs.trellix.com/configure-the-action-for-a-dbms-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure the action for a DBMS Configure an action to be taken per DBMS when the conditions of a specific vPatch rule are met. Alerts are enabled per rule; You can define only how the alert is handled for the selected DBMS. > [!NOTE] > Note > > Actions that are not enabled in the system properties are not available for selection. 1. On the **Rules** page, click the **vPatch Rules** tab. 2. In the rules list, click the **Properties** icon ![GUID-935B8A59-8600-4F15-943C-F3EEA12A79A6-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-099bc06d-0c0f-9d67-b1ac-4b620599d40a(3).png?sv=2026-02-06&spr=https&st=2026-11-22T15%3A58%3A52Z&se=2026-11-22T16%3A58%3A52Z&sr=c&sp=r&sig=AW1tWLVEXOe2Pkxxah897Gj3imlX%2BsatdYhUDcSW%2Fk4%3D) in the required row. The properties of the selected vPatch rule are displayed. 3. In the **DBMS and Groups** area, click **Change Actions** in the row for the DBMS for which you want to define a specific action. The **vPatch Rule Action Per DBMS** page is displayed. 4. To send an alert, select **Send Alert**, then select the relevant actions: - **Trellix Database Security Console** — Generates an alert on the alert screen, according to the selected alert priority, such as, **LOW**, **MEDIUM**, or **HIGH**. - **SNMP Trap** — Sends an alert as an SNMP trap when the rule is matched. - **To Archive** — Sends the alert only to the archive (without displaying it in the console or any other location). This option is suitable for auditing information that does not require monitoring on a day-to-day basis. - **Syslog** — Sends an alert to the Syslog when the rule is matched. - **Windows event log** — Sends an alert to the Windows event log when the rule is matched. - **Log to file** — Sends the alert to a log file. - **Send alert to email** — Sends the alert to the specified email addresses. 5. To terminate a session if the rule is matched, select **Terminate user session**. > [!NOTE] > Note > > This option should be used with caution because terminating sessions can disrupt legitimate business transactions. Depending on environmental variables (such as command type and table size), session termination might not stop the current SQL command. Stronger termination capability is provided for DCL and DDL commands that use a before trigger (see DDL triggers). If you select **Terminate user session**, the **Quarantine user for** option is displayed. To quarantine a user, select **Quarantine**, then enter the number of minutes the user is prevented from reconnecting. For the purposes of quarantine, "user" represents the database user, OS user, host name, IP address, or a combination of these parameters. The user definition for quarantine purposes is defined in **System** → **Quarantine** → **Settings** area. 6. To run an action script if the rule is matched, set the script to run on the host DBMS. You can use all parameters that Database Security monitors within the script, by using $ as a prefix. For example, if you want to use the *user* parameter in a script, enter `$user`. For example, `revoke dba from $user` as part of a script revokes the DBA permissions of the database user who executed the SQL command. > [!NOTE] > Note > > This option is intended for advanced users only. 7. (Optional) Configure limitations on the frequency of alerts as follows: - From the **Limit alerts per second** drop-down list, select the maximum number of alerts to generate per second. - From the **Limit alerts per session** drop-down list, select the maximum number of alerts to generate per session or select **Unlimited**. > [!NOTE] > Note > > The session is uniquely identified by the **Session ID** and **Serial** fields in Oracle, and by the **Serial ID** and **Logon time** in MSSQL. - Select **Apply action when rule triggers** for which the selected action in the rule is not executed unless the alert happens the specified number of time in the specified period. - Select **Automatically resolve** to automatically resolve an alert when triggered. - To prevent the triggering of alerts by signed scripts, select the **Ignore Signed Scripts** checkbox. 8. (Optional) To prevent the display of sensitive data in alerts, select **Mask Sensitive Data** and enter a regular expression in the **Regular Expressions** text box using standard regular expression syntax. > [!NOTE] > Note > > For more information about standard regular syntax, see [http://java.sun.com/javase/6/docs/api/java/util/regex/Pattern.html](http://java.sun.com/javase/6/docs/api/java/util/regex/Pattern.htmlbbb). 9. Click **Save**.