<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic GP and auth fails in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-and-auth-fails/m-p/1235233#M6940</link>
    <description>&lt;P&gt;Good afternoon!&lt;/P&gt;
&lt;P&gt;My Global Protect has 2FA set up so I'm only somewhat concerned about the number of fake connections I'm getting in the auth logs. They're all being routed to the identity provider and are getting squashed. However, I'd like very much to stomp these connections earlier in the chain and save myself some bandwidth. I've noted that these bogies are often trying multiple usernames from the same IP address.&lt;/P&gt;
&lt;P&gt;Is there a way to put these IPs on a timeout and silently drop any connection attempts for, say, a day or a week?&lt;/P&gt;
&lt;P&gt;Thanks to all for looking!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 01 Aug 2025 20:01:20 GMT</pubDate>
    <dc:creator>ghughes</dc:creator>
    <dc:date>2025-08-01T20:01:20Z</dc:date>
    <item>
      <title>GP and auth fails</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-and-auth-fails/m-p/1235233#M6940</link>
      <description>&lt;P&gt;Good afternoon!&lt;/P&gt;
&lt;P&gt;My Global Protect has 2FA set up so I'm only somewhat concerned about the number of fake connections I'm getting in the auth logs. They're all being routed to the identity provider and are getting squashed. However, I'd like very much to stomp these connections earlier in the chain and save myself some bandwidth. I've noted that these bogies are often trying multiple usernames from the same IP address.&lt;/P&gt;
&lt;P&gt;Is there a way to put these IPs on a timeout and silently drop any connection attempts for, say, a day or a week?&lt;/P&gt;
&lt;P&gt;Thanks to all for looking!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 20:01:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-and-auth-fails/m-p/1235233#M6940</guid>
      <dc:creator>ghughes</dc:creator>
      <dc:date>2025-08-01T20:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: GP and auth fails</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-and-auth-fails/m-p/1235252#M6943</link>
      <description>&lt;P&gt;The best way to block GlobalProtect brute-force attempts at the firewall is to use a Vulnerability Protection Profile.&lt;/P&gt;
&lt;OL start="1"&gt;
&lt;LI&gt;
&lt;P&gt;Create a Vulnerability Protection Profile: Go to Objects &amp;gt; Security Profiles &amp;gt; Vulnerability Protection.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Add a &lt;CODE&gt;block-ip&lt;/CODE&gt; exception: Edit the profile and add an exception for signature ID 40017 ("Palo Alto Networks GlobalProtect Authentication Brute Force Attempt").&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Configure the block: Set the action to &lt;CODE&gt;block-ip&lt;/CODE&gt; and define the number of failed attempts, the time window, and the block duration (e.g., 604800 seconds for a week).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Apply the profile: Apply this new profile to the security policy that allows traffic to your GlobalProtect portal.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;This will automatically and silently drop connections from a source IP after a set number of failed attempts, preventing them from ever reaching your identity provider.&lt;/P&gt;</description>
      <pubDate>Sun, 03 Aug 2025 17:20:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-and-auth-fails/m-p/1235252#M6943</guid>
      <dc:creator>Mudhireddy</dc:creator>
      <dc:date>2025-08-03T17:20:44Z</dc:date>
    </item>
  </channel>
</rss>

