Palo Alto EDL vs Dynamic Address Group vs Static Address Group

Three PAN-OS objects can hold the IP addresses you want to block. They differ in who fills them, whether a change needs a commit, and how many entries they hold.

Open the Palo Alto setup guide
By CalMax Systems Security Research, founder · Published November 12, 2026 · Checked against Palo Alto Networks documentation (PAN-OS 12.2 help and current Network Security docs; sources below)

Short answer

On PAN-OS, an External Dynamic List (EDL) is a text file of IP addresses that the firewall downloads from a URL on a schedule. A dynamic address group (DAG) fills itself from IP-to-tag mappings registered by User-ID, the XML API, VM information sources or auto-tagging. A static address group holds only the objects an admin adds.

For blocking known VPN brute force sources: use an EDL for a published block list, a DAG with auto-tagging for attackers your own firewall detects, and a static group for the trusted networks you always allow.

What Is an EDL, a Dynamic Address Group and a Static Address Group?

If you have never heard the term “EDL”, it is simply a dynamic block list the firewall downloads by URL.

External Dynamic List (EDL)

A plain-text file on a web server. The firewall retrieves it on the interval you choose and turns each line into an entry it can enforce. An IP list holds IP addresses, ranges and subnets; other EDL types hold domains or URLs. Other vendors call the same idea a threat feed or an IP block list URL. See What is an external dynamic list?

Dynamic address group (DAG)

An address group whose members are chosen by tags. You define match criteria with AND and OR operators (Palo Alto notes that negation is not supported), and every registered IP address or address object carrying matching tags becomes a member. The IP-to-tag mappings come from a registration source such as User-ID, the XML API, VM Information Sources, a Panorama plugin or an auto-tag action on logs.

Static address group

A fixed collection of address objects. Palo Alto documents that a static group can contain address objects, dynamic address groups, or both. Its contents change only when an admin edits the group.

EDL vs Dynamic Address Group vs Static Address Group: Comparison

Values are from Palo Alto Networks documentation; check your model and PAN-OS release before you rely on a capacity number.

External Dynamic List (IP list) Dynamic address group Static address group
How it is filled The firewall downloads a text file from an HTTP or HTTPS URL. By default it uses the management interface; a service route can change that. Tags registered at runtime by User-ID, the XML API, VM Information Sources, a Panorama plugin or auto-tagging, plus any static address objects that carry a matching tag. An admin adds address objects or dynamic address groups.
Does a change need a commit? No. Palo Alto says the list is imported at the configured interval and enforced without a configuration change or commit. No for tag changes: dynamic tags are part of the runtime configuration. The group and the rule that uses it must be committed once. Yes. Editing the group is a configuration change.
Refresh Every Five Minutes (default), Hourly, Daily, Weekly or Monthly. As soon as a mapping is registered or removed. Auto-tag mappings can expire after a timeout of 0 to 43,200 minutes (0 means no expiry). Only when an admin changes it.
Capacity Up to 30 custom EDLs with unique sources per firewall. Total IP entries: 150,000 on PA-3200, PA-5200 and PA-7000 Series; 50,000 on all other models. Only lists used in policy count. Maximum dynamically registered IP addresses varies by model, from 1,000 (PA-220, PA-410, PA-820, VM-50) to 500,000 (PA-5200 Series, and PA-5400 Series except the PA-5450). Up to 32 tags per IP. Not covered by the pages cited here; check your model’s object limits.
How a range or subnet counts One entry. One registered IP address. Subnets and ranges must be IPv4. Each member is an address object or group you added.
Use in a Security rule Source or Destination Address. Source or Destination Address. Source or Destination Address.
If the source goes away The firewall keeps enforcing the last list it retrieved until the web server is reachable again. If authentication to the EDL fails, Palo Alto says the rule stops enforcing the list. Registered mappings stay until they are unregistered or time out. Not applicable.
Best for A block list someone else maintains and publishes at a URL. Addresses your own firewall or tools decide about at runtime, such as an IP that just triggered a brute force signature. A short, rarely changing set, such as trusted partner networks.

How Does a Dynamic Address Group Get Its IP Addresses?

A DAG never downloads anything by itself. Something has to register IP-to-tag mappings on the firewall or on Panorama.

Palo Alto documents these registration methods:

  • User-ID agent for Windows, which can monitor VMware ESXi and vCenter servers and share IP changes with the firewall.
  • VM Information Sources, which monitor VMware ESXi, vCenter Server, AWS VPCs and Google Compute Engine natively on the firewall.
  • Panorama plugins for Azure and AWS (Panorama only).
  • The XML API, which you call from a script or a tool such as cURL. Registrations can carry a timeout so the mapping expires on its own.
  • Auto-tagging, which tags the source or destination IP of a log entry that matches a filter. For Threat, Traffic, URL and similar logs you set this in a Log Forwarding profile; for User-ID, GlobalProtect and IP-Tag logs you set it under Device > Log Settings.

Palo Alto’s auto-tag documentation adds a warning: auto-tagging is designed for tagging a small number of users or IP addresses from specific log categories, not for large volumes of traffic. Keep the filter narrow.

To create the group, go to Objects > Address Groups, click Add, set Type to Dynamic, select Add Match Criteria with your tags, and commit. Then select the group as the Source or Destination Address in a Security rule.

Which Should I Use to Block VPN Brute Force IPs?

Each object answers a different question, so a GlobalProtect deployment can use all three.

Known attackers from a published list: use an EDL

An EDL needs no script. The firewall fetches the file itself, keeps the last good copy if the server is unreachable, and does not need a commit when the list changes. Feeding the same list into a DAG would mean writing and running an XML API script, and the registered-IP maximum is 1,000 on a PA-220, PA-410 or PA-820, which a block list of a few thousand entries would not fit, and only 2,500 on a PA-850, which leaves little room for anything else you tag.

Attackers your own firewall sees: auto-tag into a DAG

Auto-tag the source IP of a matching log into a DAG used by a deny rule, with a timeout so the block lifts on its own. This reacts only after an address has already tried your portal. Our GlobalProtect guide shows the Threat-log recipe.

Networks you always trust: a static group in an allow rule above the deny

Put trusted partner or office networks in a static address group and allow them in a rule above your deny rules. Security rules match top-down, so the allow wins for those sources.

Check capacity first. An IP EDL counts against the firewall’s total only when a rule uses it. Run request system external-list list-capacities or open Objects > External Dynamic Lists > List Capacities. Details are in Palo Alto EDL limits.

How to See What Each Object Contains

These are documented PAN-OS commands and screens.

EDL

Show the parsed list

request system external-list show type ip name <name>
request system external-list refresh type ip name <name>

In the GUI, open the EDL object and select List Entries and Exceptions. If a list is not loading, see Palo Alto EDL troubleshooting.

DAG

Show registered IP addresses

show object registered-ip all
show object registered-ip all option count

In the GUI, select Policies > Security, select the rule, open the drop-down next to the address group and choose Value to see the registered addresses. For a DAG populated through the XML API on Panorama, Palo Alto says the registered addresses are not visible in the Panorama web interface; run show object registered-ip all on the Panorama CLI.

Static

Check the members count

Under Objects > Address Groups, the Members Count column shows how many objects a static group holds.

Where a VPN Brute Force Block List Fits

ThreatListPro is published as a plain-text IP EDL, so it goes in the EDL column above.

Each line is one IPv4 address or CIDR, with single IPs written as /32. The customer URL format is:

https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt

The list covers 5.4M+ IPv4 addresses in a few thousand entries and is checked for new attackers every 6 hours. Its source is real attacks on live production Palo Alto GlobalProtect VPN portals in the US. It republishes every 6 hours, so set the EDL to Hourly.

Follow the Palo Alto GlobalProtect setup guide for rule placement, or test with the free sample EDL URL first.

Limits: a new IP’s first attempt still arrives. The feed is IPv4 only. CIDR ranges include addresses that did not each attack, so check your users’ source IPs first and allow-list trusted networks. A block list does not replace MFA, patching or logging.

EDL vs Dynamic Address Group FAQs

What is the difference between an EDL and a dynamic address group?

An EDL is filled by the firewall downloading a text file from a URL on a schedule. A dynamic address group is filled by tags: IP-to-tag mappings registered by User-ID, the XML API, VM information sources or auto-tagging. Both can be the source or destination address of a Security rule.

Does a dynamic address group need a commit when its members change?

No. Palo Alto documents dynamic tags as part of the runtime configuration, so registering or removing a tag does not need a commit. The dynamic address group and the Security rule that references it must be committed once.

How many IP addresses can a Palo Alto dynamic address group hold?

The limit is the model’s maximum number of dynamically registered IP addresses. Palo Alto lists 1,000 for the PA-220, PA-410, PA-820 and VM-50, 2,500 for the PA-850 and VM-100, 50,000 for the PA-440, and up to 500,000 for the PA-5200 Series. A subnet or range counts as one registered address.

Should I block VPN brute force IPs with an EDL or a dynamic address group?

Use an EDL for a block list someone publishes at a URL: the firewall fetches it, needs no script, and keeps the last good copy if the server is down. Use auto-tagging into a dynamic address group for attackers your own firewall detects, with a timeout so the block expires.

How often does a Palo Alto EDL refresh?

You choose Every Five Minutes, which is the default, or Hourly, Daily, Weekly or Monthly. Changes are enforced without a commit. Match the interval to how often the source publishes; for a list that republishes every 6 hours, Hourly is enough.

Sources

Block Known Sources Before They Reach GlobalProtect

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed. Yearly is $200. Enterprise is $99.99/month for up to 50 firewalls. Paid plans have a 14-day money-back guarantee.

Start a 14-day free trial Or test 200 entries first: free, no signup

Related Resources

Set up the EDL, size it, or fix one that is not loading.

Palo Alto GlobalProtect EDL Setup Guide What Is an External Dynamic List? Palo Alto EDL Limits Palo Alto EDL Troubleshooting GlobalProtect Hardening FortiGate Threat Feed Setup