---
title: Configuring Firewall Provisioning based on Profile Group
slug: configuring-firewall-provisioning-based-on-profile-group
createdAt: 2026-07-27T04:11:10.676Z
---

To configure firewall provisioning based on Profile group:

1. Admin configures local profiler on IPS to discover devices connected to network. For Profile group configuration, see [Configuring Profiler Groups](docId:2iyCP6oK0rkaAXDPI58VP). Auth Table Timeout option is used for dynamic auth table policy provisioning to firewall (Applies only to SRX firewall).:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/6_jbdIyCslAb6lqDHGAt-_pg0.png" alt caption size="80" width="1660" height="1078"}
2. Configure firewall as an Enforcer, select **Endpoint Policy > Infranet Enforcer > Connection&#x20;**&#x61;nd add the enforcer.
3. Configure Auth Table Mapping Policy based on Profile Group, select **Endpoint Policy > Infranet Enforcer > Auth Table Mapping**. Under Provision Settings, enable **Provision Auth Table based on Profile Groups**.
4. Select the Profile Group to which the policy applies and click Add and then click Save Changes.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/A-l3OoLFWVgc6HvPSd7l0_pg1.png" alt caption size="80" width="1401" height="1681"}
5. Configure Resource Access Policy based on Profile Group, select **Endpoint Policy > Infranet Enforcer > Resource Access Policy**. Under Provision Settings, enable **Provision Resource Access Policy based on Profile Groups**.
6. Select the Profile Group to which the policy applies and click Add and then click Save Changes.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/f16v74vU4DzK8qtd5FF7W_pg2.png" alt caption size="80" width="1424" height="2248"}
7. For IoT access policy, select **Endpoint Policy > IoT Access > Enforcer Policy Configuration**. Under Provision Settings, enable **Provision Resource Access Policy based on Profile Groups**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/JA5RcPJisgTKNmc4aUgAb_pg4.png" position="flex-start" size="80" width="1425" height="2925" initialPath="images/pg4.png" githubPath="images/pg4.png" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/SKF9exRVrCocgQvvKN59P_pg5.png" position="flex-start" size="80" width="1880" height="616" initialPath="images/pg5.png" githubPath="images/pg5.png" showCaption="false"}

:::hint{type="info"}
\- If there are Auth Table Mapping Policies based on Roles as well as Profile Groups and if there is an authenticated session for an endpoint which is also profiled and belongs to group(s), then user roles will be given precedence over profiler groups for firewall provisioning.
\- If the user is logged out but profiled information is still available in the Profiler database then endpoint information will not be provisioned to firewall based on profile groups. However, it will be synced with firewall during next reconciliation.
\- If there is an authenticated session and if the Auth Table Mapping policy provisioning is changed to groups from roles then the corresponding entry may get deleted from the firewall if there are no other policies applying to the user role(s).
:::

