--- title: "Configure custom correlation rules" slug: "configure-custom-correlation-rules" tags: ["ESM", "Product Usage"] updated: 2026-09-12T21:19:29Z published: 2026-09-12T21:19:29Z canonical: "docs.trellix.com/configure-custom-correlation-rules" --- > ## 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 custom correlation rules Use a custom correlation rule to generate an alert when Trellix ESM detects 5 unsuccessful logon attempts from a single source on a Windows system, followed by a successful logon, all in 10 minutes. 1. In the **Rule Types** pane of the **Policy Editor**, click **Correlation**. 2. Click **New**, then select **Correlation Rule**. 3. Type a descriptive name, then select the severity setting. > ### Note > > Because an event generated by this rule could indicate that an unauthorized person has accessed the system, an appropriate severity setting is 80. 4. Select the normalization ID, which could be **Authentication** or Authentication → Login, then drag and drop the **AND** logic element. > ### Note > > Select **AND** because there are two types of actions that need to occur (logon tries first, then a successful logon). 5. Click the **Menu** icon ![Three_dots_icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-53dea48f-baf7-b5e6-13b3-eb15201497aa(1).png?sv=2026-02-06&spr=https&st=2026-11-22T16%3A26%3A43Z&se=2026-11-22T17%3A26%3A43Z&sr=c&sp=r&sig=lBcR7Jx9KOZDIvUnYHjxWfMhOwLm6IigmJ1VTlwLHS4%3D), then select **Edit**. 6. Select **Sequence** to indicate that the actions (first, five unsuccessful logon attempts, and second, a successful logon) must occur sequentially, then set the number of times this sequence must occur, which is one (1). 7. Set the period the actions need to occur in, then click **OK**. > ### Note > > Since there are two actions that require time windows, the 10-minute period must be divided between the two. For this example, five minutes is the period for each action. Once the unsuccessful attempts have occurred in five minutes, the system begins to listen for a successful logon from the same source IP address in the next 5 minutes. 8. In the **Group by** field, click the icon, move the **Source IP** option from the left to the right, indicating that all actions must come from the same source IP address, then click **OK**. 9. Define the logic for this rule or component: - Specify a filter to identify events (in this case, multiple failed logon attempts against a Windows system): 1. Drag and drop the **Filter** icon ![GUID-3296223A-4A53-491D-8C7E-34AEA4052AE9-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-982370a8-6d9d-5a05-f1e7-0981adb30b79(1).png?sv=2026-02-06&spr=https&st=2026-11-22T16%3A26%3A43Z&se=2026-11-22T17%3A26%3A43Z&sr=c&sp=r&sig=lBcR7Jx9KOZDIvUnYHjxWfMhOwLm6IigmJ1VTlwLHS4%3D) and drop it on the AND logic element. 2. On the **Filter Fields Component** page, click **Add**. 3. Select Normalization Rule → In, then select: - **Normalization** - **Authentication** - **Login** - **Host Login** - **Multiple failed login attempts against a Windows host** 4. Click **OK** . - Set the number of times the logon failure needs to occur and the period in which they must occur: 1. Drag and drop the **AND** logic element to the **Filter** bar. > ### Note > > The **AND** element is used because there are 5 separate attempts that must occur. The element allows you to set the number of times and the length of time that they must occur. 2. Click the **Menu** icon ![GUID-EF05B961-6F4A-4731-A56D-F985E10D1233-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-5caf6f68-70db-9bfb-a19b-5ecfbdc6c6f2(1).png?sv=2026-02-06&spr=https&st=2026-11-22T16%3A26%3A43Z&se=2026-11-22T17%3A26%3A43Z&sr=c&sp=r&sig=lBcR7Jx9KOZDIvUnYHjxWfMhOwLm6IigmJ1VTlwLHS4%3D) for the **AND** element you just added, then click **Edit**. 3. In the **Threshold** field, enter **5** and remove other values that are present. 4. Set the **Time Window** field to **5**. 5. Click **OK**. - Define the second filter type that needs to occur, which is the successful logon: 1. Drag and drop the **Filter** icon to the bottom prong of the first **AND** logic element's bracket. 2. On the **Match Component** page, click **Add**. 3. In the fields, select Normalization Rule → In, then select: - **Normalization** - **Authentication** - **Login** - **Host Login** 4. Click **OK** to return to the **Match Component** page. 5. To define "successful," click **Add**, select Event Subtype → In, then click the **Variables** icon and click **Event Subtype** **→** **success** **→** **Add**. 6. Click **OK** to return to the **Policy Editor**. :