By CalMax Systems Security Research, founder · Published February 1, 2026 · Last updated: November 18, 2026
An External Dynamic List (EDL) is a plain-text file of IP addresses, domains or URLs, hosted at a web address, that a firewall downloads on a schedule and enforces in a security rule. When the file changes, the firewall picks up the change on its next refresh, with no manual edits.
This guide explains what an EDL is, how different firewall vendors implement the concept, and how a service like ThreatListPro turns an EDL into an automated shield against VPN brute force attacks.
Which Palo Alto EDL Do You Need?
“EDL” covers lists that do different jobs. Pick by what the rule should do:
- Allow a SaaS service: Palo Alto’s EDL Hosting Service publishes the IP and URL endpoints of SaaS services such as Microsoft 365, typically used to allow or route that traffic. These are not threat lists.
- Block generally malicious networks: with a Threat Prevention license, PAN-OS includes predefined lists such as Palo Alto Networks - Known malicious IP addresses, - High risk IP addresses and - Bulletproof IP addresses, updated daily by Palo Alto through content updates, with no feed URL to manage.
- Block sources attacking your VPN login: a third-party attacker feed, such as ThreatListPro, added as an IP List EDL and used in a deny rule in front of GlobalProtect.
What is the best EDL feed for Palo Alto?
There is no single best feed; choose by purpose. For VPN attack-source blocking, ThreatListPro is one option: its feed covers 5.4M+ IPv4 addresses from real attacks on live production Palo Alto GlobalProtect VPN portals in the US, and it is checked for new attackers every 6 hours. It is IPv4 only. Before choosing any feed, compare its source, format, fit with your firewall’s EDL capacity, price and what it leaves out. See the IP blocklist comparison and Palo Alto EDL limits.
Is there a free EDL for Palo Alto?
Yes. ThreatListPro publishes a free 200-entry sample at https://api.threatlistpro.com/v1/sample/blocklist.txt, with no signup, for testing the download, parsing and policy match. It is a limited sample, not the full feed. Other free sources are listed on the EDL list URLs page.
How do I add an EDL to Palo Alto?
Go to Objects > External Dynamic Lists > Add, choose IP List, paste the HTTPS feed URL and set a refresh schedule; for HTTPS sources, a certificate profile can authenticate the server. Reference the list as the source in a deny Security policy rule, commit, then check that the entries downloaded and that the rule gets hits. The GlobalProtect setup guide covers protecting the VPN portal.
Defining the External Dynamic List
An External Dynamic List is a plain-text file hosted on a web server that contains a list of IP addresses, domain names, or URLs. Your firewall downloads this list on a recurring schedule and enforces whatever security rule references it, blocking (or allowing) traffic that matches the entries on the list. PAN-OS, for example, offers five-minute, hourly, daily, weekly and monthly refresh intervals.
The key word is dynamic. Unlike a static address group that an administrator must update manually, an EDL updates itself. When the list changes on the remote server, your firewall picks up those changes on the next refresh cycle without any human intervention. On Palo Alto firewalls, a dynamic address group is the other self-updating option; see EDL vs dynamic address group for when to use each.
Palo Alto Networks popularized the term “External Dynamic List” in PAN-OS, but every major firewall vendor offers an equivalent feature under a different name:
| Vendor | Feature Name | Configuration Path |
|---|---|---|
| Palo Alto Networks | External Dynamic List (EDL) | Objects → External Dynamic Lists |
| Fortinet FortiGate | External Block List / Threat Feed | Security Fabric → External Connectors |
| Cisco Secure Firewall (FTD, managed by FMC) | Security Intelligence feed | Objects → Object Management → Security Intelligence |
| Check Point | Network Feed object | SmartConsole → Objects → Network Feed |
| Sophos Firewall | Third-party threat feed | Active threat response → Third-party threat feeds |
| SonicWall (SonicOS 7) | Dynamic External Address Group | Object → Match Objects → Dynamic Group |
| pfSense / OPNsense | URL Table Alias (IPs) | Firewall → Aliases (type URL Table (IPs)) |
Regardless of the vendor, the underlying concept is the same: the firewall reaches out to a URL, downloads a list of indicators, and enforces policy based on that list.
How an EDL Works Step by Step
Understanding the lifecycle of an EDL helps you configure it correctly and troubleshoot issues when they arise. Here is what happens from end to end:
- List creation: A threat intelligence provider (or your own team) compiles a list of malicious IP addresses. The list is saved as a plain-text file with one entry per line and hosted on a web server accessible to your firewall.
- Firewall configuration: An administrator creates an EDL object on the firewall, providing the URL of the hosted list and setting a refresh interval (e.g., every hour or once per day).
- Initial download: The firewall fetches the list immediately upon commit. It parses each line and loads the entries into memory as an address object.
- Policy binding: The administrator references the EDL object in a security policy rule—typically a deny rule placed early in the rulebase. Any traffic whose source IP matches an entry in the EDL is blocked before it reaches your VPN portal, web application, or other protected resource.
- Scheduled refresh: On every refresh cycle, the firewall re-downloads the list. New IPs are added; IPs that were removed from the list are unblocked. No commit or manual action is required.
- Logging: If logging is enabled on the deny rule, each blocked session appears in the traffic log under that rule’s name, so you can see why it was denied. Name the rule after the list to make this obvious.
EDL Format Requirements
EDL formatting is deceptively simple, but small mistakes cause big headaches. The list must meet these requirements to be parsed correctly by most firewalls:
- Served over HTTPS (recommended) or HTTP
- Plain text, ideally with a Content-Type: text/plain response header, and nothing else in the body
- One entry per line. On Palo Alto an IP list entry can be a single address (e.g.,
198.51.100.23), a subnet (e.g.,203.0.113.0/24) or a start-end range, IPv4 or IPv6, and each counts as one entry (Palo Alto IP list format) - An IP list holds IP entries only; URLs and domains go in separate URL or domain lists
- Palo Alto accepts an optional comment after the entry on the same line, separated by a space; other vendors may not accept comments, so a bare list is the most portable
- Avoid blank lines and trailing whitespace; some firewalls tolerate them, but it is safest to leave them out
- Keep the file small. FortiOS 7.2, for example, caps each threat feed at 10 MB (Fortinet threat feeds)
EDL Server and Hosting Requirements
Any web server can host an EDL, but the firewall only trusts what it can fetch reliably. A good EDL host:
- Serves HTTPS with a valid certificate. Many firewalls refuse self-signed or expired certificates unless you add a certificate profile.
- Returns
text/plainwith one entry per line and nothing else: no HTML error pages, no login pages, no byte-order mark. - Keeps a stable URL. The firewall stores the URL in its configuration, so a changed path means a silent failure until someone edits the object.
- Answers quickly and stays up. If a refresh fails, most firewalls keep using the last list they downloaded, so an outage freezes your protection instead of removing it. Check the object's last-updated time after any change.
- Protects private lists. Use a hard-to-guess token in the URL or basic authentication, and never paste a private list URL into public forums.
- Stays within your platform's limits. Count entries, not addresses: a single /24 range is one entry. See the Palo Alto and FortiGate limits guides.
You can host your own list on a web server, an object-storage bucket or a raw file in a code repository, or point the firewall at a managed EDL URL (see what to check in a hosted EDL service). For a ready list to test with, use the free 200-entry sample (also on GitHub, with setup examples for six firewalls) or compare working EDL list URLs.
Why EDLs Are Critical for VPN Security
VPN portals such as Palo Alto GlobalProtect, Fortinet SSL-VPN, and Cisco AnyConnect have to face the internet to work, which makes them a steady target for credential stuffing and password spraying. On our own portals, campaigns have caused 50+ account lockouts per day.
An EDL gives you a way to block known attackers at the firewall level, before their traffic reaches the VPN portal. For an address on the list, the session is dropped before login, so that attempt never reaches your authentication server and never counts toward an account lockout. Addresses not yet on the list still need MFA and lockout policies; see GlobalProtect hardening.
ThreatListPro as a Ready-Made EDL Source
Building and maintaining your own threat intelligence list takes steady work. You need a source of real attack data, a way to analyze logs and separate noise from real attacks, and a pipeline to publish the list in the right format on a reliable server.
ThreatListPro handles all of this for you. When you subscribe, you receive a private HTTPS URL that serves a curated blocklist of IPs and CIDR ranges caught attacking live production Palo Alto GlobalProtect VPN portals in the US. The list is formatted as a standard EDL—one IP or CIDR range per line, plain text, served with the correct headers—so it works out of the box with Palo Alto, Fortinet, Cisco, Check Point, Sophos, pfSense, and any other firewall that supports external IP lists.
What the list is and is not: entries come from attacks on live production Palo Alto GlobalProtect VPN portals in the US, and the list is IPv4 only. CIDR ranges cover addresses where attacks came from many hosts, so not every address in a range attacked.
Common EDL Pitfalls and How to Avoid Them
- Firewall cannot reach the URL: Ensure the management interface (or data plane, depending on configuration) has outbound HTTPS access to the EDL host. Check DNS resolution and proxy settings.
- SSL certificate errors: If the EDL is served over HTTPS, the firewall must trust the certificate chain. Use a certificate from a well-known CA.
- Exceeding entry limits: On Palo Alto the limit is per firewall, not per list: all IP-type EDLs used in policy share one total, which depends on the model (Palo Alto’s PAN-OS 10.0 documentation lists 50,000 for most models and 150,000 for PA-5200 and PA-7000 Series). Entries past the limit are skipped and a System log is written. Check your model under
Objects → External Dynamic Lists → List Capacities; details in our Palo Alto EDL limits guide. ThreatListPro covers 5.4M+ addresses in only a few thousand entries, well inside these limits. - Stale data: If the EDL server goes down, the firewall continues using the last successfully downloaded list. Monitor your EDL refresh status to ensure updates are happening on schedule.
Common EDL Feeds for Firewall IP Blocking (2026)
A small number of focused feeds is easier to size and audit than dozens of overlapping mega-lists. Here are widely used sources, organized by category. Sizes and file dates for the free lists were checked October 23, 2026, and will change; check the file before you rely on a number.
VPN Brute Force Protection
| Feed | Focus | Update Frequency | Size | Cost |
|---|---|---|---|---|
| ThreatListPro | VPN brute force IPs from real attacks on live production Palo Alto GlobalProtect VPN portals in the US; works on any firewall that takes an IP list | Checked for new attackers every 6 hours | 5.4M+ IPv4 addresses | $19.99/mo after 14 days free |
| CrowdSec | Attacker IPs shared by a community of CrowdSec agents | Set by CrowdSec | Varies by list and plan | Free + paid |
ThreatListPro is built for VPN portal attacks. Its curated list keeps false-positive risk low because its entries come from real attacks on VPN portals, and its compact size fits entry-level devices like the PA-220 or FortiGate 40F. CrowdSec takes a different approach: you run its agent, which detects attacks on your own services and shares signals with a community network that publishes blocklists back.
General Threat Intelligence (C2, Botnets, Scanners)
| Feed | Focus | Update Frequency | Size | Cost |
|---|---|---|---|---|
| Spamhaus DROP | Hijacked and criminal-run netblocks. EDROP was merged into DROP on April 10, 2024, so use DROP alone | Re-evaluated daily; Spamhaus asks for downloads at least an hour apart | About 1,700 ranges | Free (see Spamhaus terms) |
| abuse.ch Feodo Tracker | Botnet C2 servers | File last updated March 4, 2026 | 5 IPs | Free |
| Emerging Threats compromised IPs | Known compromised hosts (Proofpoint ET Open) | File dated October 23, 2026 | 482 IPs | Free |
Two lists that older guides recommend need a note. The abuse.ch SSLBL IP blacklist was empty and last updated January 2, 2025, so it adds nothing as an EDL. The Cisco Talos bulk IP blocklist download did not return a list when we checked; Talos still offers per-address reputation lookups at talosintelligence.com. We have left both out of the table.
Aggregated / Scored Feeds
| Feed | Focus | Update Frequency | Size | Cost |
|---|---|---|---|---|
| IPsum (stamparm) | 30+ public lists merged; the level is how many lists include an IP | Daily (per its README) | Level 3: about 19,800 IPs | Free |
| FireHOL | Many public lists merged into tiered levels | Varies by level; both files dated October 23, 2026 | Level 1: about 4,600 entries; Level 3: about 11,900 entries | Free |
| AbuseIPDB | Community-reported IPs with an abuse confidence score | Reports arrive continuously | Depends on confidence threshold and plan | Free tier + paid API |
List Capacities on your own firewall. Entries past the limit are skipped. Compact lists like ThreatListPro (5.4M+ addresses in only a few thousand entries) and Spamhaus DROP (about 1,700 ranges) leave plenty of room.
Recommended EDL Stacking Strategy
A few complementary feeds usually work better than one giant list, because each covers a different slice of hostile traffic. Here is a practical three-tier approach:
Tier 1: Minimal
- ThreatListPro — VPN brute force protection
- Spamhaus DROP — Hijacked and criminal-run netblocks (low false-positive risk)
This two-feed stack covers VPN brute force sources and known-bad networks while using little EDL capacity. It is a reasonable starting point for most environments.
Tier 2: Balanced
- Everything in Tier 1, plus:
- abuse.ch Feodo Tracker — Botnet C2 servers (small; check the file date)
- IPsum Level 3 — IPs that appear on 3 or more public lists (about 19,800 IPs; budget the capacity)
- CrowdSec — Community signals (if you can deploy the agent)
Good for production networks running exposed services beyond VPN (web servers, mail, SSH).
Tier 3: Enterprise (High-Security)
- Everything in Tier 2, plus:
- Vendor-native intelligence (Palo Alto Unit 42, Cisco Talos Intelligence)
- GeoIP blocking (restrict to operating countries)
- SIEM-driven correlation with auto-tagging (Splunk, Sentinel, Cortex XSIAM)
Appropriate for organizations with a SOC, SIEM, and security automation stack.
Quick-Start EDL Configs by Firewall
Here are the essential commands or menu paths to add an EDL on the most common firewall platforms:
Palo Alto (PAN-OS)
FortiGate (FortiOS)
pfSense (pfBlockerNG)
Frequently Asked Questions
What format does an EDL need to be in?
An EDL is a plain-text file served over HTTPS or HTTP, with one entry per line and nothing else in the body, ideally sent as text/plain. On Palo Alto, an IP list entry can be an IPv4 or IPv6 address, a subnet, or a start-end range, optionally followed by a space and a comment. ThreatListPro serves its IPv4-only blocklist in this format.
How often should an External Dynamic List refresh?
PAN-OS offers five-minute, hourly, daily, weekly and monthly intervals, and FortiGate sets the refresh rate in minutes. For a VPN brute force list, hourly is a sensible choice. ThreatListPro is checked for new attackers every 6 hours, so hourly polling picks up each new version within an hour.
What is the maximum number of IPs an EDL can contain?
It depends on the firewall model and software version. On Palo Alto the limit is per firewall, shared by all IP lists used in policy: the PAN-OS 10.0 documentation lists 50,000 total IP addresses for most models and 150,000 for PA-5200 and PA-7000 Series, and List Capacities on the firewall shows yours. FortiOS 7.2 caps each threat feed at 10 MB or 131,072 entries; FortiOS 7.6.3 uses a device-wide limit of 300,000, 1,000,000 or 5,000,000 IP entries by model class. ThreatListPro covers 5.4M+ addresses in only a few thousand entries.
Can I use an EDL with firewalls other than Palo Alto?
Yes. Palo Alto Networks coined the term EDL, and other vendors offer the same idea under different names: Fortinet calls it an external threat feed, Cisco Secure Firewall uses Security Intelligence feeds, Check Point uses Network Feed objects, Sophos calls it a third-party threat feed, and pfSense and OPNsense use URL Table aliases. ThreatListPro works with all of these; Sophos uses a separate Sophos-format URL.
How long does it take to set up an EDL on a firewall?
Usually a few minutes. You create an EDL object on your firewall, paste the URL of the hosted list, set a refresh interval, reference the object in a deny rule, and commit. With a ready-made URL in the correct format, there is no scripting or formatting work.