--- title: "Create a custom rule in new rule page" slug: "create-a-custom-rule-in-new-rule-page-3" tags: ["Product Usage", "DS 10.x", "Database Security"] updated: 2026-09-10T15:20:12Z published: 2026-09-10T15:20:12Z canonical: "docs.trellix.com/create-a-custom-rule-in-new-rule-page-3" --- > ## 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. # Create a custom rule in new rule page Create a custom rule defining all rule properties in a single window. > [!NOTE] > Note > > If you are new to the rule creation process, you follow the wizard guided process when creating your first rules. 1. On the **Rules** page, select the **Custom Rules** tab, then click **Create New Rule**. 2. In the **Name** field, enter a name for the rule. It is recommended that the name selected clearly reflect the nature of the rule, for example, Sensitive HR tables or PCI-DSS password protection. 3. In the **If** fields, define the first rule comparator statement as follows: 1. In the first field, type the first letter of the identifier name, then select the required identifier from the drop-down list. 2. In the second field, select the required operator from the drop-down list. 3. In the third field, enter the literal component to be matched. If the literal component is a string, the text must be enclosed in single quotation marks. > [!NOTE] > Note > > Alternatively, you can enter the comparator statement directly into the text box under the **If** fields, entering a space to access the respective drop-down lists. 4. Click **Add**. If the rule includes more than one comparator statement, enter the relevant Boolean operator (AND, OR, or NOT) in the fourth field, then define the next comparator statement. Repeat for additional comparator statements as required. > [!NOTE] > Note > > If there is a problem with the rule syntax, validation fails and a message is displayed. For example, if you fail to enclose a text string in single quotation marks, a message is displayed regarding an unexpected token. 5. (Optional) To turn off the auto-completion feature, select **Disable auto completer**. > [!NOTE] > Note > > You can define rule objects, which can then be used as components in other rules. For example, a rule object might be used in the definition of a rule intended to allow a specific range of IP addresses. 6. To create an exception to this rule, click **Add Exception**. Then, in the **Exception(s)** text box, enter a comparator statement that defines the conditions which when matched are treated as an exception to this rule. Repeat to define additional exceptions as required. 7. In the **Then** area, select the required actions that the rule should trigger. > [!WARNING] > Caution > > The **Terminate** option should be used sparingly because terminating sessions can disrupt legitimate business transactions. Use the terminate option only in the following conditions: > > - You are certain that the rule will not create false positives (we recommended to use the rule first in alert only mode to make sure that legitimate traffic is not affected). > - The risk involved with the rule condition is high. > - Terminating a session causes only minimal disruption to other transactions. > [!NOTE] > Note > > Quarantine is done based on the quarantine settings in the **System** tab. Make sure that you edit the quarantine settings before you enable quarantine on any of your rules. 8. To allow the statement to be processed if the rule is matched, select **Allow**. This enables you to create an exception to a rule that appears later in the policy. 9. To stop the matching process if a rule is matched, select **Stop Verifying Additional Rules**. This is the default setting when the rule is set to **Allow**. If this option is not selected, the matching process continues. 10. To select the DBMSs where the rule is applied: The selected DBMSs and DBMS groups are listed in the **DBMSs & Groups** fields respectively. 1. In the **Install On**, click **DBMSs & Groups**. 2. In the **Install on DBMSs and DBMS Groups** , select one or more relevant DBMSs or DBMS groups, then click **Save** to return to the rule definition. 11. To assign a tag to the rule, enter the tag name in the **Tags** field or enter a space in the field to select the tag from the drop-down list. 12. (Optional) By default, all users can edit the properties of a custom rule. To limit the ability to edit the properties of this rule to specific users or users assigned a specific role, enter the user names or role names in the **Grant edit permission to role/s** field. 13. In the **Comments** field, enter a free text description or comment. 14. To enable the rule, select **Enable Rule**. > [!NOTE] > Note > > You can enable or disable the rule at any time by selecting or deselecting the **Enable Rule** checkbox. 15. To prevent the triggering of alerts by signed scripts, select the **Ignore Signed Scripts** checkbox. 16. Click **Save** to save the rule.