<?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: policy to only allow specific Host-ID auth thru GlobalProtect. in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/policy-to-only-allow-specific-host-id-auth-thru-globalprotect/m-p/537420#M3864</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/282912"&gt;@logmpang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The common solution to this issue is to deploy certificates to the hosts and require certificate AND username/password for GlobalProtect.&amp;nbsp; The GlobalProtect client will check for the certificate 1st.&amp;nbsp; If it does not exist, an error will be displayed instead of the username/password prompt.&amp;nbsp; You can use the same certificate for each client or a unique certificate for each client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Make sure that you configure "No (User Credentials AND Client Certificate Required)" under the client authentication entry on the portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Mon, 03 Apr 2023 10:47:16 GMT</pubDate>
    <dc:creator>TomYoung</dc:creator>
    <dc:date>2023-04-03T10:47:16Z</dc:date>
    <item>
      <title>policy to only allow specific Host-ID auth thru GlobalProtect.</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/policy-to-only-allow-specific-host-id-auth-thru-globalprotect/m-p/537192#M3856</link>
      <description>&lt;P&gt;i'm seeing bad guys trying to bruteforce my GlobalProtect VPN and I want to stop that.&lt;/P&gt;
&lt;P&gt;I want to achieve only specific laptop Host-ID can go thru GlobalProtect authentication and bad guys when they trying to auth with wrong account/pwd should not able to or&amp;nbsp;GlobalProtect shall not prompt 'wrong account/password'.&lt;/P&gt;
&lt;P&gt;Can I do this via policy?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2023 05:33:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/policy-to-only-allow-specific-host-id-auth-thru-globalprotect/m-p/537192#M3856</guid>
      <dc:creator>logmpang</dc:creator>
      <dc:date>2023-03-31T05:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: policy to only allow specific Host-ID auth thru GlobalProtect.</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/policy-to-only-allow-specific-host-id-auth-thru-globalprotect/m-p/537420#M3864</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/282912"&gt;@logmpang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The common solution to this issue is to deploy certificates to the hosts and require certificate AND username/password for GlobalProtect.&amp;nbsp; The GlobalProtect client will check for the certificate 1st.&amp;nbsp; If it does not exist, an error will be displayed instead of the username/password prompt.&amp;nbsp; You can use the same certificate for each client or a unique certificate for each client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Make sure that you configure "No (User Credentials AND Client Certificate Required)" under the client authentication entry on the portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 10:47:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/policy-to-only-allow-specific-host-id-auth-thru-globalprotect/m-p/537420#M3864</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2023-04-03T10:47:16Z</dc:date>
    </item>
  </channel>
</rss>

