By CalMax Systems Security Research, founder · Published February 27, 2026 · Updated October 23, 2026
Short answer: blocking VPN brute force IPs by hand is a reactive loop: an attack shows up in your logs, you add deny rules, and the attacker returns from new addresses. An automated EDL blocklist replaces that loop with one firewall rule pointing at one URL, checked for new attackers every 6 hours.
ThreatListPro's list is built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US, so IPs already seen attacking those portals can be blocked before they reach yours. It covers 5.4M+ IPv4 addresses.
The Cost Calculator
Add up the hours your team spends on manual IP blocking during an active VPN brute force campaign. Enter your own numbers below; the defaults are only an example.
Manual IP Blocking: Monthly Cost
ThreatListPro: Monthly Cost
Side-by-Side Comparison
Manual blocking costs admin time on every campaign. An EDL blocklist costs a subscription and a one-time setup.
| Metric | Manual Blocking | ThreatListPro |
|---|---|---|
| Setup Time | Ongoing (never finished) | A few minutes |
| Ongoing Work | Repeats with every campaign | No rule changes after setup |
| When IPs Are Blocked | After they attack you | Before they reach you, if already seen attacking our portals |
| Consistency | Depends on who is on shift | Checked for new attackers every 6 hours |
| Multiple Firewalls | Rules added on each firewall | Same EDL URL on every firewall |
| Knowledge Required | Log analysis, reputation checks, rule changes | Paste a URL, bind a deny rule |
| Monthly Cost | Example: ~$780 in labor (3 hrs/week at $60/hour) | $19.99 |
| Source of Attacker IPs | Your own logs only | Real attacks on live production Palo Alto GlobalProtect VPN portals in the US |
Workflow 1: Blocking IPs by Hand
Every pass through the manual workflow starts after the attack has already reached your VPN portal:
- Notice the attack. Lockout tickets or failed-login alerts arrive. During campaigns we have seen 50+ account lockouts per day on our own portals (see account lockout prevention).
- Find the source IPs. Pull failed authentications from the VPN logs and count them by source address.
- Check each one. Look it up in WHOIS or a reputation service so you do not block a real user.
- Add deny rules. Create address objects, add them to a block rule, commit, and repeat on every firewall.
- Document the change for audits and change control.
VPN portal
lock out
tickets pile up
logs
on firewall
new IP
The loop does not end, because attackers pause and return from new IPs. Three problems grow over time:
- Coverage gaps. Blocking happens only when someone is looking. An attack that starts on a Saturday night runs until someone checks the logs.
- Rule sprawl. Hundreds of single-IP entries make the policy harder to read and audit.
- Only your own data. Your logs show an IP only after it has attacked you. On our own portals, attempts rose 300% from Q1 2024 to Q1 2026, so the volume to review keeps growing.
Scripts that parse logs and push rules through the firewall API cut the typing, but they are still reactive, need maintenance, and can block a legitimate user who mistyped a password.
Workflow 2: Automated EDL Blocklist
With an External Dynamic List (EDL), the firewall fetches the blocklist itself. You set it up once:
- Copy your ThreatListPro EDL URL.
- Add it to the firewall as an external IP list (EDL, threat feed or dynamic address object, depending on the platform; see the setup guides).
- Bind it to a deny rule in front of your VPN portal.
- Set the refresh interval. The list republishes every 6 hours.
After that:
- No ongoing rule work. When new attackers are seen, they are added at the next 6-hour check, and your firewall picks them up on its next refresh.
- One rule instead of hundreds. The policy has one EDL object and one deny rule, which keeps audits simple.
- Same effort on every firewall. Each firewall uses the same URL. Monthly and Yearly plans cover up to 2 firewalls; Enterprise covers up to 50.
- Blocked before login. Connections from listed IPs are dropped at the firewall before they reach the VPN login page.
Keep watching your own logs: an IP that attacks you but is not on the list yet still shows up there. The blocklist removes the repeat work, not the need for monitoring. To see whether an address from your logs is already listed, use the IP check tool; for the attack pattern behind most of these logins, see password spraying against VPNs.
Frequently Asked Questions
How much time does manual IP blocking take per week?
As an example, consider a team that spends 3 hours a week on manual IP blocking during an active VPN brute force campaign: reviewing logs, checking IP reputation, adding firewall rules, documenting changes and handling lockout tickets. At $60/hour, that is about $780/month in labor. Use your own hours and rate.
What is the difference between reactive and proactive IP blocking?
Reactive blocking means you block an IP after it has already attacked you, so the lockouts and log noise have already happened. Proactive blocking means you block known attacker IPs before they reach your network. ThreatListPro builds its list from real attacks on live production Palo Alto GlobalProtect VPN portals in the US, so an IP already seen attacking those portals can be blocked at your firewall before it reaches your VPN portal.
Can I automate manual IP blocking with scripts instead of buying a blocklist?
Partly. Scripts can parse authentication logs, extract failed-login source IPs and push them to your firewall through its API. That is still reactive, it needs ongoing maintenance, and it can block a legitimate user who mistyped a password. ThreatListPro costs $19.99/month, needs no scripting, and blocks IPs already seen attacking our own production VPN portals.