GlobalProtect Brute Force: Stop Authentication Attempts

Start with Palo Alto Networks' own controls. Then deny IPs already attacking VPN portals with an External Dynamic List above the GlobalProtect allow rule.

Start a 14-day free trialOr test 200 entries first: free, no signup
5.4M+
IPv4 Addresses Blocked
6h
New-Attacker Checks
$19.99
Per Month, No Card for the Trial
By CalMax Systems Security Research, founder · Last updated: October 28, 2026 · Checked against Palo Alto Networks documentation (sources below)

How do I stop GlobalProtect brute force? Require MFA or client certificates, disable the browser login page if users do not need it, tune the failed-logon signature, and apply Block IP carefully. Then deny known attacker sources with an IP External Dynamic List, set to check for updates hourly, above the portal and gateway allow rule. Keep PAN-OS and threat content on supported updates.

Free test list (200 entries, no signup): https://raw.githubusercontent.com/pcchiu2023/threatlistpro-blocklist/main/data/sample/blocklist.txt · GitHub repository

GlobalProtect Authentication Brute Force Attempt: What It Means

The Threat log alert commonly searched as Palo Alto Networks GlobalProtect Authentication Brute Force Attempt is Threat ID 40017. It is a parent signature. Child 32256 detects individual GlobalProtect authentication requests, whether they succeed or fail. The parent alerts after 10 matches from the same source to the same destination in 60 seconds by default.

That is different from failed-login detection. Threat ID 40169 aggregates child 96010, Palo Alto Networks GlobalProtect Authentication Failure Detection. Its documented default is 60 failures in 5 seconds, medium severity, with action alert. Use 40169 when your goal is specifically to act on failed portal or gateway logons.

A source IP can represent many users behind NAT. Blocking by source can therefore cut off legitimate users who share that address. Start with alerting, watch your own traffic, exempt trusted networks, and tune the threshold before you enable Block IP.

Palo Alto Networks' Own Fixes (Do These First)

These controls are native to GlobalProtect and PAN-OS. Each solves a different part of the problem. Keep PAN-OS patched as well: an exploited management-interface flaw lets an attacker with admin credentials run code as root, so check which PAN-OS versions fix CVE-2026-0322.

Control What it does Limit
MFA or client-certificate authentication Requires more than a password and can restrict access to endpoints with valid certificates Does not stop requests from reaching the portal
Disable the browser login page
Network > GlobalProtect > Portals > portal > General > Appearance
Returns 404 to browser access while GlobalProtect apps can still reach the portal May not help with getconfig.esp attempts
Authentication Profile lockout
Device > Authentication Profile > profile > Advanced
Locks an account after configured failed attempts Not available for SAML; defaults are 0 in normal mode, so configure both fields deliberately. An attacker who knows a username can lock that user out
Threat ID 40169 with Block IP Can block a source after the failed-logon threshold Acts only after the threshold and can affect users behind a shared source IP
Auto-tagging and a Dynamic Address Group Tags a source from a matching Threat log and puts it into a deny rule for a set timeout Reactive; it needs a generated Threat log and a higher-priority deny rule
Supported PAN-OS and threat-content updates Keeps the platform and its delivered signatures on supported fixes and content Requires routine change control and testing

Set Block IP on the failed-logon signature

For the PAN-OS 11.1 through 12.1 interfaces documented here, go to Objects > Security Profiles > Vulnerability Protection. Add or edit a profile, open Exceptions, and select Show all signatures. Find 40169, the failed-logon parent. Parent 40017 also accepts an exception, but it counts successful as well as failed authentication requests, so Block IP on 40017 can cut off legitimate users who share a source address. Enable the exception, select Block IP, set a duration from 1 to 3,600 seconds, and track by source or source-and-destination. Attach the profile under Policies > Security > rule > Actions > Profile Setting, then commit.

Optional: auto-tag the source into a Dynamic Address Group

Create a tag named gp-brute-force under Objects > Tags and a dynamic group under Objects > Address Groups whose match criteria is that tag. Under Objects > Log Forwarding, add a Threat-log match for (threatid eq 40169). Add a built-in Tagging action: target Source Address, action Add Tag, registration Local User-ID, and a tested timeout in minutes. Use the group as the source of a deny rule above the GlobalProtect allow rule, then attach the Log Forwarding profile to the inspected rule. Verify runtime mappings with:

show object registered-ip all
show log iptag tag_name equal gp-brute-force

Why a GlobalProtect Brute Force IP Blacklisting Policy Helps

Signature blocking and auto-tagging are reactive. The source must first generate enough matching events on your firewall. An IP EDL can deny sources that were already observed attacking other VPN portals before they make an authentication attempt on yours.

ThreatListPro covers 5.4M+ IPv4 addresses. It is built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and is checked for new attackers every 6 hours. The feed is plain text with one IPv4 address or CIDR per line; single IPs are written as /32. It occupies a few thousand entries. Check the Palo Alto EDL limits by model before deployment.

Block GlobalProtect Brute Force with an EDL

The GUI labels below follow the PAN-OS 11.1 through 12.1 documentation. The CLI examples are for a locally managed firewall; on Panorama, create the object in the applicable device group.

01

Get a feed URL

Use the free 200-entry sample with no signup (https://raw.githubusercontent.com/pcchiu2023/threatlistpro-blocklist/main/data/sample/blocklist.txt), or the subscription URL from your welcome email: https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt.

02

Create the IP External Dynamic List

Go to Objects > External Dynamic Lists, add ThreatListPro-VPN, select IP List, enter the feed URL, and set Check for updates to Hourly. On a firewall, select Test Source URL.

configure
set external-list ThreatListPro-VPN type ip url https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt
set external-list ThreatListPro-VPN type ip recurring hourly
commit
03

Check trusted source networks

Compare your users' successful GlobalProtect source IPs with the list. Place a narrow allow rule for trusted networks above the deny rule before enforcing it.

04

Create the deny rule

Go to Policies > Security and create a rule from the internet-facing zone to the zone of the portal or gateway interface. Use ThreatListPro-VPN as the source, the portal or gateway interface IP as the destination, and Deny as the action. Put it above the GlobalProtect allow rule.

When the GlobalProtect interface itself is in untrust, both source and destination zones are untrust. Traffic to that dataplane service otherwise reaches the default same-zone rule, and intrazone-default permits same-zone traffic. Match the interface IP so the rule does not block unrelated untrust traffic. Set Service to application-default and leave the other options at their defaults (Application any), as Palo Alto Networks' EDL procedure does. Do not narrow the deny rule to the GlobalProtect App-IDs.

05

Commit and verify

Commit, then run request system external-list show type ip name ThreatListPro-VPN. Confirm that the list is valid and populated, and check Monitor > Logs > Traffic for sessions denied by the EDL rule.

request system external-list show type ip name ThreatListPro-VPN
request system external-list list-capacities
request system external-list refresh type ip name ThreatListPro-VPN

Signature Block vs. EDL Block

The controls act at different points. Use them together with MFA, supported PAN-OS and threat-content updates, and normal account protections.

Question Vulnerability signature + Block IP IP External Dynamic List
What triggers it? A local parent signature reaches its threshold. By default, 40017 requires 10 authentication requests from the same source to the same destination in 60 seconds; 40169 requires 60 failed-logon child events in 5 seconds. A source address matches an entry already imported from the external list and reaches the EDL deny rule.
How long does it last? The Block IP duration in a Vulnerability Protection exception is 1 to 3,600 seconds. For a longer local response, auto-tag the source into a denied Dynamic Address Group; the tag timeout range is 0 to 43,200 minutes. The deny rule continues to match while the address remains in the imported list and the rule is active. PAN-OS imports changes at the configured retrieval interval without another commit.
What can it miss? Attempts that stay below the configured threshold, including low-and-slow traffic, and spraying distributed across enough source addresses. New or unlisted sources. Our list is IPv4-only, so it does not cover an IPv6 listener.
Where is it configured? Objects > Security Profiles > Vulnerability Protection > Exceptions, then attach the profile to the applicable Security policy rule. Objects > External Dynamic Lists, then use the EDL as the source in a higher-priority deny Security policy rule.

Verify the signature and active IP block

Open Monitor > Logs > Threat and use the filter builder to select Threat ID 40017 or 40169. Inspect the source, destination, matched rule, and action. For an active Block IP entry, open Monitor > Block IP List (documented for PA-3200, PA-5200, and PA-7000 Series firewalls) or run:

show dos-block-table all

debug dataplane show dos block-table

The first command is the documented operational view. Palo Alto Networks also documents the debug command for inspecting the dataplane block table created by a threat-protection Block IP action.

What a Block List Can't Do

Which Fix Stops What

Control Stolen password Repeated failures from one IP Known listed IP before login New IP's first attempt
MFA or client certificate Limits access Does not stop requests No Still arrives
40169 + Block IP No After threshold Only after local failures Still arrives
DAG auto-tagging No After matching log Only after local event Still arrives
ThreatListPro EDL No For listed IPs Yes Still arrives if not listed

Frequently Asked Questions

What is the Palo Alto Networks GlobalProtect Authentication Brute Force Attempt alert?

Threat ID 40017 is a medium-severity parent signature with a default action of alert. It fires after child signature 32256 detects 10 GlobalProtect authentication requests from the same source to the same destination in 60 seconds. It counts authentication requests regardless of success, so it is not a failed-login-only counter.

Which Palo Alto brute force signature tracks failed GlobalProtect logins?

Threat ID 40169 is the failed-logon-only parent signature for the GlobalProtect portal and gateway. Its child, 96010, detects an authentication failure. The documented default is 60 child events in 5 seconds, medium severity, and alert. Tune the threshold for your environment before changing the action to Block IP.

Can Palo Alto block a source IP after GlobalProtect brute force?

Yes. Under Objects > Security Profiles > Vulnerability Protection, create an exception for the parent signature, select Block IP, set a duration, and track by source or source-and-destination. Attach the profile to the Security policy rule for the portal or gateway. A shared NAT address can represent legitimate users too, so test thresholds and exempt trusted source networks.

How do I block GlobalProtect brute force longer than 3,600 seconds?

The Block IP action in a Vulnerability Protection exception accepts 1 to 3,600 seconds. For a longer local block, use a Threat-log auto-tagging action to add the source to a Dynamic Address Group used by a deny rule. The tag timeout can be 0–43,200 minutes; 0 requires explicit removal.

How do I add an External Dynamic List for GlobalProtect?

In PAN-OS, go to Objects > External Dynamic Lists, add an IP List, enter the HTTPS feed URL, and choose Hourly under Check for updates. Use Test Source URL, commit, then place a deny Security policy rule using that EDL as the source above the GlobalProtect allow rule.

Why is a GlobalProtect block rule untrust to untrust?

When the portal or gateway is hosted on a dataplane interface in the untrust zone, Palo Alto Networks documents the matching Security policy as untrust to untrust. Without a more specific rule, PAN-OS permits same-zone traffic through intrazone-default. Match the portal interface IP and place the EDL deny rule above the allow or default rule.

How often should PAN-OS refresh the GlobalProtect block list?

Choose Hourly. ThreatListPro is checked for new attackers every 6 hours. The feed covers 5.4M+ IPv4 addresses in a few thousand entries. Check your model's capacity before deployment.

Sources

Block IPs Already Attacking VPN Portals

Monthly is $19.99 with a 14-day free trial and no card needed. Yearly is $200. Enterprise is $99.99 per month. All paid plans have a 14-day money-back guarantee.

Start 14-Day Free Trial (No Card)Or test 200 entries first: free, no signup

Firewall Guides

ThreatListPro provides a standard IP blocklist feed compatible with any firewall that supports external lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

See related guides for IP blocklists, VPN brute force, and firewall limits.

GlobalProtect Hardening Checklist Password Spraying on VPNs: Detect and Stop It VPN Brute Force Attacks Explained What Is an External Dynamic List (EDL)? IPv6 VPN Brute Force: The Emerging Blind Spot Blocklist vs geo-blocking for VPN attacks Stop Account Lockouts from Brute Force Best IP Blocklist Stack 2026 Best VPN Brute Force Protection 2026 Palo Alto EDL Limits by Model Palo Alto EDL Not Working? Fix Errors Free EDL List URLs for Palo Alto (Tested) All Firewall Setup Guides