--- title: "Create a mapping exception rule" slug: "create-a-mapping-exception-rule-1" tags: ["Product Usage", "DS 10.x", "Database Security"] updated: 2026-09-10T15:20:46Z published: 2026-09-10T15:20:46Z canonical: "docs.trellix.com/create-a-mapping-exception-rule-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. # Create a mapping exception rule Use the sample information collected by Database Security about the access to the DBMS, to create exception rules. After Database Security collects sampled information about the access to the DBMS, the **DBMS Access Info** tab shows detailed information about the most commonly used clusters of applications, users, IP addresses, and more, which have accessed the DBMS during the sampling period, including a count for each cluster This information gathered can be used for the following: - Create exception rules For example, if a rule is created with an exception for a certain combination of IP address, application and user, then this rule will not generate alert or event when the syntax of a rule exception is matched. - Create monitoring rules For example, alert or audit each time the combination of user x, application y and IP z is detected. You can define exceptions to your custom rules by creating an **Allow** rule and placing it before the relevant rules in the **Custom Rules** list. This option is normally used when you identify an activity that happens often and does not require monitoring. You can also create an **Alert** rule for a specific combination. This option is used when you identify activity that should be monitored. 1. On the **Rules** page, select the **Application Mapping** tab, then select **DBMS Access Info**. 2. From the **Select DBMS** drop-down list, select the DBMS whose application mapping information you would like to review. Click **Apply**. The application mapping information for the selected DBMS is displayed in the **Display Settings** table. 3. (Optional) To filter the display settings for the DBMS, enter the relevant criteria in the filter area, then click **Apply**. 4. To create an **Allow** rule: 1. Click the **Create Allow Rule** icon ![GUID-B381E5EF-B9EE-4B57-96C7-6FDCFA6F538E-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-1d43da39-8fde-32e9-0433-c60378378f9d(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A58%3A27Z&se=2026-11-22T14%3A58%3A27Z&sr=c&sp=r&sig=5VuCXLuSqphEce9IjnCKjE3MGyFZ92b89MhnispHf9Y%3D) in the required row. The **Allow** rule is displayed in **Custom Rules** tab. 2. Click **Save**. The **Allow** rule is created and added to the **Custom Rules** list. 5. To create an **Alert** rule: Repeat for more entries in the table, as required. 1. Click the **Create Alert Rule** icon ![GUID-5EAD6465-FAA0-49F3-9B76-555D379C65FA-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-8ab39dda-ecac-2a9b-af8f-1053334fc3db(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A58%3A27Z&se=2026-11-22T14%3A58%3A27Z&sr=c&sp=r&sig=5VuCXLuSqphEce9IjnCKjE3MGyFZ92b89MhnispHf9Y%3D) in the required row. The **Alert** rule is displayed in **Custom Rules** tab. 2. Click **Save**. The **Alert** rule is created and added to the **Custom Rules** list. 3. Configure the **Alert** rule in the **Audit Wizard** tab of **Application Mapping**.