<?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 Re: How to block the user in global protect if you enter the wrong user several times in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591705#M5555</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/192671"&gt;@Alpalo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;What are you using as a user directory and how are you authenticating the user? If your using something like Active Directory via RADIUS, you could implement this via an account lock-out policy upon a specified number of failed login attempts. Just be mindful that someone could utilize your gateway to lock out users in your environment. You can specify a lock-out duration so that you don't need to manually unlock the account if you wish as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Likewise you could follow &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClJ2CAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClJ2CAK&lt;/A&gt; to setup automatic IP blocking for a specified duration as well whenever the firewall itself detects a brute force attack.&lt;/P&gt;
&lt;P&gt;I'm partial to using the API to analyze this sort of activity because it allows more flexibility and custom response handling (like cross-comparing information sources to verify whether or not it's actually a user who's simply forgot their credentials). This has the added benefit of being able to quarantine the endpoint itself so that it can't login regardless of the IP address that it's attempting to login from once you want to restrict it programmatically.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jul 2024 13:43:29 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-07-11T13:43:29Z</dc:date>
    <item>
      <title>How to block the user in global protect if you enter the wrong user several times</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591328#M5537</link>
      <description>&lt;P&gt;Hello everybody&lt;/P&gt;
&lt;P&gt;could someone help me with the following question&lt;/P&gt;
&lt;P&gt;How to block the user in global protect if you enter the wrong user several times?&lt;/P&gt;
&lt;P&gt;I would like to know if there is a way to block a user for a certain amount of time if you enter the wrong credentials, is it possible?&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 10:09:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591328#M5537</guid>
      <dc:creator>Alpalo</dc:creator>
      <dc:date>2024-07-11T10:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to block the user in global protect if you enter the wrong user several times</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591674#M5553</link>
      <description>&lt;P&gt;Hi team&lt;/P&gt;
&lt;P&gt;Any idea?&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 10:09:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591674#M5553</guid>
      <dc:creator>Alpalo</dc:creator>
      <dc:date>2024-07-11T10:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to block the user in global protect if you enter the wrong user several times</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591705#M5555</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/192671"&gt;@Alpalo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;What are you using as a user directory and how are you authenticating the user? If your using something like Active Directory via RADIUS, you could implement this via an account lock-out policy upon a specified number of failed login attempts. Just be mindful that someone could utilize your gateway to lock out users in your environment. You can specify a lock-out duration so that you don't need to manually unlock the account if you wish as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Likewise you could follow &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClJ2CAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClJ2CAK&lt;/A&gt; to setup automatic IP blocking for a specified duration as well whenever the firewall itself detects a brute force attack.&lt;/P&gt;
&lt;P&gt;I'm partial to using the API to analyze this sort of activity because it allows more flexibility and custom response handling (like cross-comparing information sources to verify whether or not it's actually a user who's simply forgot their credentials). This has the added benefit of being able to quarantine the endpoint itself so that it can't login regardless of the IP address that it's attempting to login from once you want to restrict it programmatically.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 13:43:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/how-to-block-the-user-in-global-protect-if-you-enter-the-wrong/m-p/591705#M5555</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-07-11T13:43:29Z</dc:date>
    </item>
  </channel>
</rss>

