Dynamic Address Groups (DAGs) are essential for Palo Alto Networks policy management, allowing firewall rules to dynamically adapt to changes in network conditions. Elisity's integration now supports Panorama, providing centralized management of DAGs across multiple Palo Alto Networks firewalls.
Key Benefits of Panorama Integration
- Centralized Security Management: Instead of configuring individual firewalls, Panorama acts as a single control plane, ensuring consistency.
- Automated Security Updates: DAGs dynamically update based on Policy Groups (PGs) defined in the Elisity platform.
- Scalability & Efficiency: Synchronization to all firewalls from Panorama eliminates manual configuration effort.
- High Availability Support: Support for Panorama HA mode with automatic switchover for DAG synchronization.
Integration Workflow
- Policy Groups in Elisity: Devices, users, and endpoints are assigned to PGs based on identity and behavior.
- Mapping to DAGs: PGs are converted into DAGs and published to Panorama.
- Panorama Polling for Device Groups: Instead of pushing DAGs directly to a predefined Device Group, Elisity queries Panorama for all Device Groups under 'Shared'.
- DAG Synchronization: Retrieved Device Groups are updated with DAG entries to ensure all managed firewalls receive the correct data.
- Commit Behavior Control: Administrators can now choose whether to commit DAGs directly to Panorama or to both Panorama and managed firewalls. This setting gives customers control over DAG propagation timing, supporting workflows such as change control windows.
- Tag Distribution: DAGs require IP-TAG redistribution for their values to be recognized and applied on managed firewalls.
- Firewall Policy Enforcement: DAGs in Panorama are referenced in security policies for automated enforcement.
Prerequisites
Before proceeding, ensure the following prerequisites are handled:
-
Panorama Configuration
- Enable DAGs within Panorama.
- Ensure Panorama is configured to manage the intended firewalls.
- Configure User-ID Redistribution to allow tag propagation to firewalls.
- For security rule visibility Elisity requires creating a common username in Panorama (matching the username used to onboard the Panorama VEN) to be pushed to the different firewalls.
- Firewalls with separate API keys / usernames than the one used to manage Panorama are not supported.
-
Firewall Configuration
-
DAGs will not show any entries under Objects -> Address Groups until they are referenced in a Security Policy.
-
Verify IP-Tag Redistribution settings to enable DAG updates.
-
-
API Access & Credentials
- Dedicated Panorama admin user with API permissions.
- Generate an API key for Elisity integration.
- For security rule visibility Elisity requires creating a common username/password in Panorama's device groups (matching the username used to onboard the Panorama VEN) to be pushed to the firewalls.
Creating Dedicated User Credentials
Create a unique user account on the firewall for Elisity’s Virtual Edge (VE) nodes to use for API communication.
The account should have:
Superuser permissions: Required for full API functionality.
XML API access: To allow DAG updates and configuration commits.
Avoid sharing credentials with other services or administrators to maintain security and reduce conflicts.
Management Profile Setup
Configure the firewall’s management interface to allow HTTPS communication from the VE IPs. Ensure the appropriate IP addresses for the VE nodes are whitelisted under the firewall’s permitted IP settings.
Generate an API Key
- Firewall IP Address
- Username (shown in example as veusername)
- Password (shown in example as vepassword)
https://<FIREWALL_IP>/api/?type=keygen&user=<USERNAME>&password=<PASSWORD>
example:
https://192.168.1.1/api/?type=keygen&user=veusername&password=vepassword
<response status="success">
<result>
<key>
LUFRPT1LSXduVStJanRobnU5eVl2K3c1TFNhZEFZSUE9aFVmWTRZRXBiMUxlMmpiRGxrb1BxT2VGcTY5aGxYOS8rWnZDMlVLMVArRFpMTERuRnlKYlI4eU4zUElheDRLVw==
</key>
</result>
</response>
Connectivity Requirements
| Direction | Required Traffic |
|---|---|
| Virtual Edge to Virtual Edge Node |
HTTPS (TCP/443)
|
| Virtual Edge Node to Virtual Edge |
HTTPS (TCP/443)
|
Onboarding Panorama in Cloud Control Center (CCC)
Step 1: Create a Firewall Integration VE Group
Navigate to Edge Management > Virtual Edges and create a VE group dedicated for Panorama integration.
See our Virtual Edge Groups and Virtual Edge Deployment articles for steps on how create VE Groups and Virtual Edges.
Step 2: Deploy Panorama as a Virtual Edge Node
1. Launch the Virtual Edge Node Wizard
Add a Virtual Edge Node to a previously created Virtual Edge Group using the wizard. Launch the wizard by clicking on + Add Virtual Edge Node in Edge Management > Virtual Edge Nodes.
Select a dedicated Virtual Edge Group for Palo Alto Networks.
2. Choose the Virtual Edge Node Type
On the Virtual Edge Node Type step, select the Security Platform tile and click Next.
On the Security Platform Type step, select Palo Alto Networks. Under Deployment Type, select Panorama and click Next.
3. Enter Integration Details
Fill out the required fields to configure communication between the Virtual Edge Node and Panorama:
-
Firewall IP: Management IP of Panorama or both primary/secondary IPs if using HA.
-
Username: Admin account with superuser permissions and API access.
-
API Key: Paste the API key generated with the credentials above.
-
Description (optional): Add a description to help identify the Virtual Edge Node.
Tip: Generate an API key using the following URL (replacing placeholders as needed):
Replace <FIREWALL_IP>, <USERNAME>, and <PASSWORD> with the appropriate values.
The response contains the API key inside the <key> element. Copy this value.
Note: The Prerequisites section covers account permissions and User-ID redistribution required for DAG synchronization and rule visibility.
4. (Optional) Enable High Availability Mode
If deploying in Panorama HA mode, toggle High Availability and provide both primary and secondary Panorama IP addresses.
5. Configure Advanced Options
Before continuing, review the advanced options available in this step:
-
Palo Alto Commit Behavior: Choose to commit DAG changes to Panorama only, or commit and push directly to firewalls. This setting gives customers additional control over DAG propagation timing, supporting workflows such as change control windows.
-
Palo Alto DAG Rule Visibility: Optionally enable visibility into local (non-Panorama-managed) firewall rules.
These settings can also be modified later by editing the Virtual Edge Node.
6. Finalize Configuration
Review your settings in the summary view and click Finish to deploy the Virtual Edge Node. A confirmation appears once the Virtual Edge Node is added.
7. Post-Onboarding View
After deployment, verify the Virtual Edge Node status in the Virtual Edge Node Information card on the Virtual Edge Node details page. If HA is enabled, the currently active Panorama instance is marked with a green indicator.
Assigning Policy Groups as DAGs in Cloud Control Center
Elisity's integration with Panorama polls Panorama for Device Groups and allows Administrators in Cloud Control Center to selectively distribute Policy Groups to Device Groups in Panorama. Each Device Group in Panorama can have independent collections of Policy Group mappings, enabling flexible and precise control of how DAGs are populated. The process is as follows:
Elisity Polls Panorama for Device Groups
- CCC retrieves all Device Groups under All from Panorama.
- These device groups are populated in Cloud Control Center in the details view of the Panorama VEN.
Nested (Hierarchical) Device Groups
Panorama supports hierarchical Device Group structures, with Device Groups nested beneath the top-level Shared Device Group. Panorama allows up to five levels of nesting (counting Shared as the first level), and in production environments it is common to see four or five levels in use, with the physical firewalls assigned to the lowest-level (leaf) Device Groups.
When Elisity polls Panorama, it retrieves every Device Group across all hierarchy levels and lists them in Cloud Control Center. The example below, taken from a production Panorama, shows a Device Group tree nested up to five levels deep.
How nested Device Groups appear in Cloud Control Center
Cloud Control Center retrieves and supports the complete set of Device Groups from Panorama, including those nested at every level of the hierarchy. Note, however, that CCC lists Device Groups in alphabetical order rather than in Panorama's parent-child tree order, so the nesting relationships are not represented visually in the Device Group list. When deciding where to assign Policy Groups, refer to your Panorama configuration to confirm which Device Groups are parents and which are children.
How DAG inheritance affects distribution
Panorama automatically propagates a Dynamic Address Group (DAG) applied to a parent Device Group down to every child Device Group beneath it. This is native Panorama behavior and is not controlled by Elisity. An inherited DAG reports the parent Device Group in its Location column, indicating it was not configured directly on the child.
Recommended distribution methods for nested Device Groups
To distribute Policy Groups cleanly in a nested hierarchy, choose one of the following approaches so that CCC's per-Device-Group assignments match what Panorama enforces:
- Assign to the leaf Device Groups only (recommended). Assign the Policy Group only to the lowest-level Device Groups that actually contain the firewalls (for example, the two Test Device Groups in the first screenshot). Because nothing is applied to a parent, there is no inheritance for the consistency check to misinterpret, and the DAG stays scoped to the Device Groups that own the firewalls.
- Assign to every Device Group in the branch. Assign the Policy Group to the parent and all of its child Device Groups in CCC. The consistency check then expects the DAG everywhere it appears and leaves the inherited copies in place.
- Assign at the Shared Device Group. Applying the Policy Group at Shared makes the DAG global, so every Device Group already has it and there is nothing for the consistency check to remove. Use this only when the broadest scope is acceptable.
When reviewing Device Groups in CCC, refer to your Panorama configuration to understand the parent-child relationships before deciding where to assign Policy Groups. As noted above, CCC lists Device Groups alphabetically rather than in Panorama's hierarchy order, so the parent-child structure is not shown in the selector itself.
Add Policy Groups to be mapped to DAGs
- By default, no Policy Groups are sent. You must select which PGs you want to publish as DAGs within each Device Group by selecting the group on the left hand side and clicking Edit Policy Groups in the additional options menu.
The Device Group Mapping menu allows you to specify which Policy Groups will be mapped as Dynamic Address Groups for each Device Group in Panorama.
The interface will display the total number of IP addresses being pushed for each Policy Group mapping. After assigning Policy Groups to Device Groups in Panorama, the total number of mapped PGs will appear next to each Device Group (1).
Click Commit Changes to confirm. You can then check the Dynamic Address Groups in Panorama for each Device Group and see the Elisity-programmed DAG has been populated.
The naming for each DAG pushed from Cloud Control Center is standardized as:
Elisity_<PG_ID>_policy_group_name
Commit Configuration to Panorama
- Choose Commit to Panorama and Devices (Recommended Default).
- Monitor commit status logs in CCC to confirm success.
- Verify that DAGs appear under Objects > Address Groups in Panorama.
Final Configurations and Validation in Panorama
Configure User-ID Redistribution for DAG Tag Distribution
- Log in to Panorama and navigate to User-ID Redistribution Settings. Enable Redistribute User Mappings to managed firewalls by going to the Management Interface Settings and checking the User-ID box in the Network Services section. Panorama acts as a User-ID Redistribution Point, forwarding DAG tags to managed firewalls.
- Ensure that firewalls are configured to receive IP TAG mappings from Panorama by navigating to the Data Redistribution settings and ensuring that the IP Tags check box is selected for each relevant Firewall.
- Verify DAG tags appear on managed firewalls.
Managing Changes to Policy Group Derived Dynamic Address Groups
Adding New PGs
- Automatically pushed to Panorama when added in Elisity.
- Commit required in Panorama to apply.
Removing PGs
- If PG is still referenced in policies, it will not be deleted from Panorama.
- Administrators will receive a warning before deletion.
Renaming Policy Groups
When a Policy Group that is mapped to a Dynamic Address Group is renamed in Cloud Control Center, the corresponding DAG on Panorama or the firewall is renamed in place. This preserves any existing security rules that reference the DAG, eliminating the need for manual reconfiguration in Panorama after a rename.
- The rename operation propagates automatically to all associated Device Groups.
- Security rules referencing the DAG continue to function without modification.
- The updated DAG name follows the standard naming convention: Elisity_<PG_ID>_policy_group_name.
- No additional commit or administrator action is required beyond the standard commit workflow.
Decommissioning and Off-Boarding Panorama
Decommissioning the Panorama Virtual Edge Node takes the integration out of service. The Virtual Edge deletes the Elisity DAGs from every mapped Device Group and commits the change to Panorama. Cloud Control Center keeps the Virtual Edge Node configuration for recommissioning.
Step 1: Identify Rules That Use Elisity DAGs
In Cloud Control Center, open the Panorama Virtual Edge Node and review the security rules for each Device Group (see Policy Group Usage Visibility in Palo Alto Security Rules). In Panorama, search Policies > Security > Pre Rules and Post Rules in each Device Group for address groups whose names begin with Elisity_. If the managed firewalls have local rules, also check those rules for Elisity DAGs. When Palo Alto DAG Rule Visibility is enabled, the Cloud Control Center view also lists these local rules.
Step 2: Remove the DAG References
Edit each rule to remove the Elisity DAG, or delete the rule if it is no longer needed. Then commit to Panorama and push to the affected Device Groups.
Step 3: Decommission the Virtual Edge Node
Navigate to Edge Management > Virtual Edge Nodes, open the Panorama Virtual Edge Node, and click Decommission in the top right.
You can also decommission from the Virtual Edge Nodes list: click the more options button in the Actions column and select Decommission Virtual Edge Node.
To decommission several Virtual Edge Nodes at once, select their check boxes, click Bulk actions, and select Decommission.
For a Palo Alto Networks Virtual Edge Node, the confirmation dialog shows this warning: "If any of the Policy Groups configured as Dynamic Address Groups by the Virtual Edge on this Virtual Edge Node is in use in a firewall policy the decommission will fail after 15 minutes. Virtual Edge Node can be deleted upon failure." Click Decommission.
Step 4: Verify the Decommission
The Virtual Edge Node status moves through Decommission In Progress to Decommissioned. In Panorama, confirm that no Device Group lists Elisity DAGs in Objects > Address Groups. If Palo Alto Commit Behavior is set to commit to Panorama only, push the configuration to the Device Groups so that the managed firewalls also remove the DAGs (see Configure Advanced Options).
The Activity tab of the Notifications panel (bell icon, top right) shows the progress of the decommission.
To remove the integration permanently, delete the decommissioned Virtual Edge Node from its details page. To return it to service, select Recommission Virtual Edge Node.
If Decommissioning Fails
If a DAG is still referenced when the 15-minute window ends, the status shows Decommission Failed. The more options menu for the node then offers Decommission Virtual Edge Node, Recommission Virtual Edge Node, and Delete Virtual Edge Node.
To recover, remove the remaining DAG references in Panorama, commit and push, and then select Decommission Virtual Edge Node again.
If you delete the Virtual Edge Node instead, the Virtual Edge no longer manages Panorama, so manually remove any remaining address groups whose names begin with Elisity_ from the Device Groups, and then commit and push.
While the status is Decommission In Progress, Force Delete (in Bulk actions and the row menu) removes the Virtual Edge Node from Cloud Control Center immediately. Force Delete does not remove DAGs from Panorama, so the same manual cleanup applies.
Best Practices
- Use dedicated Virtual Edges (VEs) for Panorama to avoid exceeding API session limits.
- Ensure IP-Tag Redistribution is Enabled. Without it, DAG tags will not propagate.
- Review Resource Limits: Panorama/firewall DAG capacities should be monitored.
- Track Commit Logs: Regularly verify commit success/failure in Panorama.
Policy Group Usage Visibility in Palo Alto Security Rules
When Policy Groups are published to Palo Alto Networks firewalls as Dynamic Address Groups (DAGs), their usage within firewall security rules can be viewed directly from the associated Virtual Edge Node (VEN) in Cloud Control Center.
For direct firewall integrations, the left panel displays the Policy Groups assigned to the VEN. The security rules table lists all rules on the associated firewall that reference those DAGs. Each row includes a timestamp indicating when the rules were last retrieved. Rules no longer present on the firewall are automatically removed during the next update cycle.
In Panorama-managed environments, Policy Groups are shown grouped under their assigned Device Groups. The corresponding firewalls and their security rules are displayed per device group. Rules that reference multiple DAGs (e.g., in both source and destination fields) are displayed under each relevant Policy Group for clarity. The left panel supports expandable views per device group, and all columns in the rules table support standard filtering, global search, and list-style expansion for multi-value fields.
Firewall rules are refreshed at a configurable interval, and the most recent update time is shown in the "Last Update" column. This ensures administrators have a current view of how identity-driven segmentation policies are enforced within the firewall infrastructure.
Note: Visibility from the VEN view is currently supported. Viewing policy group usage across all firewalls from the Policy Group details page is not yet available.