--- title: "How firewall rule groups work" slug: "how-firewall-rule-groups-work-2" updated: 2026-08-30T14:35:52Z published: 2026-10-07T18:14:56Z canonical: "docs.trellix.com/how-firewall-rule-groups-work-2" --- > ## 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. # How firewall rule groups work Firewall rule groups organize firewall rules for easy management. The software includes predefined rule groups with rules that allow needed services, such as ePO - On-prem and DNS, to run. Firewall rule groups don't affect the way Firewall handles the rules; the software processes rules from top to bottom. Firewall processes the settings for the group before processing the settings for the rules it contains. If a conflict exists between these settings, the group settings take precedence. You can create customized rule groups such as **Timed groups** which are active for a set time. You can also create nested groups. The nested groups help in enhancing the efficiency of firewall rule organization. For instance, you can apply protocol settings at the group level, determine the direction at the group level, and schedule a group (also known as timed group) to be active during specific intervals. The subgroups and rules nested beneath it will also be in effect for the same designated period. ### Sample configuration with Nested rules The group **Protocol_G1** has nested group **Protocol_G2** and within the group you will find the actual rule **Protocol_G1G2R1_rule**. ![GUID-F9EE5666-0FFC-4E8B-A902-C7C436C932CA-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-dd20e4e4-ef84-42f8-665d-418da7b45ce9(1).png?sv=2026-02-06&spr=https&st=2026-11-18T23%3A38%3A03Z&se=2026-11-19T00%3A38%3A03Z&sr=b&sp=r&sig=1x40lcmeO0%2FmPXuZV09dF1CraTaRhAwTxPZNU84zDxg%3D) > [!NOTE] > Note > > The direction of the groups, subgroups, and rules should match. For instance, If the direction of **Protocol_G1** is **In**, the direction for the nested group **Protocol_G2** should also be **In**. In the conflicting case, **Protocol_G2** will not be enforced.