<?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: User-ID and Internal Gateway in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616889#M6103</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/270478"&gt;@seag&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The connection method is setup on the portal and not the gateway, so that becomes a bit more convoluted. If using an MDM you can kind of work around that by modifying registry keys conditionally, but not something I would really recommend. Either option that &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt; mentioned would be workable solutions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would &lt;EM&gt;&lt;STRONG&gt;highly&lt;/STRONG&gt;&lt;/EM&gt; recommend at this point that you just enforce a VPN connection at all times on issued devices and just not allow someone to disable the agent. I've rarely come across valid use cases for being allowed to disable the VPN on an issued device when out of the office.&lt;/P&gt;
&lt;P&gt;If this is a BYOD environment then you could easily just do the first option that &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt; brought up. There's some aspects that you'd have to think about when it comes to your DHCP lease times and User-ID timeout values, but that would effectively allow what you want.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Nov 2024 22:12:40 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-11-11T22:12:40Z</dc:date>
    <item>
      <title>User-ID and Internal Gateway</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616444#M6092</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I want to implement GlobalProtect with Internal and External Gateway. Internal gateway will be used for User-ID and External Gateway for Remote Access.&lt;/P&gt;
&lt;P&gt;Is there a way to prevent users from disconnecting GP when inside corporate network and allow them to disconnect when outside corporate network ?&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;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 16:59:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616444#M6092</guid>
      <dc:creator>seag</dc:creator>
      <dc:date>2024-11-08T16:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: User-ID and Internal Gateway</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616464#M6100</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I can think of several things:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Configure your policies with user-id's and active directory groups. That way if they disable it and try to get to internal resources, etc, they are limited to what they can get to.&lt;/LI&gt;
&lt;LI&gt;Force everyone to VPN in, a step closer to zero trust. I wrote and article on it.
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://skrzsecurity.net/zero-trust" target="_blank"&gt;https://skrzsecurity.net/zero-trust&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;I'm sure there are other options.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 21:42:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616464#M6100</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-11-08T21:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: User-ID and Internal Gateway</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616889#M6103</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/270478"&gt;@seag&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The connection method is setup on the portal and not the gateway, so that becomes a bit more convoluted. If using an MDM you can kind of work around that by modifying registry keys conditionally, but not something I would really recommend. Either option that &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt; mentioned would be workable solutions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would &lt;EM&gt;&lt;STRONG&gt;highly&lt;/STRONG&gt;&lt;/EM&gt; recommend at this point that you just enforce a VPN connection at all times on issued devices and just not allow someone to disable the agent. I've rarely come across valid use cases for being allowed to disable the VPN on an issued device when out of the office.&lt;/P&gt;
&lt;P&gt;If this is a BYOD environment then you could easily just do the first option that &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt; brought up. There's some aspects that you'd have to think about when it comes to your DHCP lease times and User-ID timeout values, but that would effectively allow what you want.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2024 22:12:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/616889#M6103</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-11-11T22:12:40Z</dc:date>
    </item>
    <item>
      <title>Re: User-ID and Internal Gateway</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/617126#M6106</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Indeed...That will "force" them to connect.&lt;/P&gt;
&lt;P&gt;Good article by the way !&lt;/P&gt;
&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, you configure the connection method on the portal. I was thinking about creating another "Agent Config" on the portal with a different "Config Selection ". But you cannot choose a source IP or Network as criteria.&lt;/P&gt;
&lt;P&gt;Your recommendation to always enforce VPN connection at all times when it is not a BYOD environment makes sense.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you guys !&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 12:46:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/user-id-and-internal-gateway/m-p/617126#M6106</guid>
      <dc:creator>seag</dc:creator>
      <dc:date>2024-11-12T12:46:26Z</dc:date>
    </item>
  </channel>
</rss>

