--- title: "Overlapping entitlements" slug: "overlapping-entitlements-v7-0" description: "Understand overlapping actions in entitlements, their precedence rules, and how to manage access exceptions effectively for secure network configurations." tags: ["Entitlements", "Overlapping Entitlements"] updated: 2026-06-08T16:56:45Z published: 2026-06-08T16:56:45Z canonical: "support.appgate.com/overlapping-entitlements-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Overlapping entitlements Actions in entitlements may overlap in terms of subnet, protocol, ports, and types, causing a packet to match more than one action. Overlapping actions can exist within the same entitlement or across different entitlements. The overlap may be unintentional, or it may be deliberate — for example, mixing `<ALLOW>` and `<BLOCK>` actions to add exceptions to a range. When a packet matches more than one action, only the action with the highest precedence applies. Non-matching actions are not logged, do not trigger user interactions, do not raise alerts, and do not influence whether the packet is allowed or blocked. > [!NOTE] > NOTE > > The `<EXCLUDE>` action type applies to local routes in the client and has no effect on overlapping entitlement rules on the Gateway. --- ## Action precedence rules The following rules determine which action takes precedence when actions overlap: **1. HTTP actions take precedence over TCP actions.** For example, `<ALLOW> HTTP up 172.23.23.100` (which implies ports 80 and 443) takes precedence over `<ALLOW> TCP up 172.23.23.100 port 80` and `<ALLOW> TCP up 172.23.23.100 port 443`. **2. A smaller subnet has higher precedence.** For example, `<BLOCK> 172.23.23.0/24 port 80` takes precedence over `<ALLOW> 172.23.0.0/16 port 80`. A packet to `172.23.23.1:80` is blocked despite matching both actions, because a `/24` subnet is smaller than a `/16` subnet. **3. If subnets are equal, a smaller port or type range has higher precedence.** For example, `<BLOCK> 172.23.0.0/16 port 80` takes precedence over `<ALLOW> 172.23.0.0/16 port 1-65535`. A packet to `172.23.0.1:80` is blocked despite matching both actions, because the range `80` is smaller than `1-65535`. **4. If subnets are equal and port or type ranges are equally small, the action with the higher starting port or type has higher precedence.** (Rare) For example, `<BLOCK> 172.23.0.0/16 port 11-100` takes precedence over `<ALLOW> 172.23.0.0/16 port 1-90`. A packet to `172.23.0.1:80` is blocked despite matching both actions, because the range `11-100` starts higher than `1-90`. **5. If subnets and port or type ranges are equal, an allowing action takes precedence over a blocking action.** "Allowing" means an action marked `<ALLOW>` in an entitlement whose conditions are currently met. "Blocking" means either an action marked `<BLOCK>` or `<ALERT>`, or an action marked `<ALLOW>` in an entitlement whose conditions are not currently met. For example, `<ALLOW> 172.23.0.0/16 port 80` takes precedence over `<BLOCK> 172.23.0.0/16 port 80`. Additionally, if two entitlements share the same `<ALLOW> 172.23.0.0/16 port 80` action but one entitlement is already available and the other requires a user interaction, the already-available entitlement is used and no user interaction is requested. **6. If two actions are identical — equal subnets, equal port or type ranges, and equal allow or block status — precedence is unpredictable.** Either action may be applied. This includes the case where a specific `<BLOCK>` action and an `<ALLOW>` action with an unmet condition are both present. While the outcome of the entitlement is the same regardless of which action is applied, the unpredictability affects audit logs. The audit log records only the applied action. For example, if entitlement `foo` has `<ALLOW> tcp-up to intranet port 80` and entitlement `bar` has the same action, a user connecting to `intranet:80` is allowed access. The audit log records either `foo` or `bar` — not both. --- ## Use cases for overlapping entitlements The precedence rules above can be used deliberately to handle access exceptions within a single entitlement. For example, to allow full access to subnet `192.168.0.0/24` while blocking `192.168.0.16/28`, permitting `192.168.0.20` for all users, and raising an alert on any access attempt to `192.168.0.21`, configure the following rules in a single entitlement: ```plaintext 192.168.0.0/24 port 1-65535 192.168.0.16/28 port 1-65535 192.168.0.20 port 1-65535 192.168.0.21 port 1-65535 ``` To require two-factor authentication for accessing a specific server within a blocked range — for example, `192.168.0.17` — place the rule `<ALLOW> 192.168.0.17 port 1-65535` in a separate entitlement that requires two-factor authentication. This takes precedence over `<BLOCK> 192.168.0.16/28 port 1-65535` in the first entitlement and triggers a user interaction if one is defined. You can also allow access to `192.168.0.0/24` under password authentication while requiring two-factor authentication for `192.168.0.16/28` by splitting the rules across two entitlements: - Entitlement A requires password authentication and contains `<ALLOW> 192.168.0.0/24 port 1-65535`. - Entitlement B requires two-factor authentication and contains `<ALLOW> 192.168.0.16/28 port 1-65535`. When using this configuration, add entitlement B to every policy that includes entitlement A. Omitting B from any such policy bypasses the two-factor authentication requirement for the `192.168.0.16/28` range.