<?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: Prevent bypassing captive portal? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/862398#M5099</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Not sure on the answer, however the captive portal is used for User-ID to IP mapping. If the PAN already knows the mapping, it will not prompt the user for a captive portal.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I used to have an environment where I used USER-ID on all my policies, and if the users didnt have a mapping, they got a very restrictive URL filtering policy applied to them. This was done by security policies however.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Nov 2024 18:14:26 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2024-11-27T18:14:26Z</dc:date>
    <item>
      <title>Prevent bypassing captive portal?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/704644#M5089</link>
      <description>&lt;P&gt;We are in an environment where we have captive portal (with MS SSO) but users are able to get around the authentication redirects via VPN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We'd like to ensure that the only traffic that is allowed by unauthenticated users on this network is traffic that is redirected to captive portal and cannot be bypassed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would we just be looking at placing 2 rules higher up&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1 - Desired network + unknown user + web-browsing = allowed&lt;/P&gt;
&lt;P&gt;2 - Desired network + unknown user + all = block&lt;/P&gt;
&lt;P&gt;?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 22:14:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/704644#M5089</guid>
      <dc:creator>OGMaverick</dc:creator>
      <dc:date>2024-11-26T22:14:44Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent bypassing captive portal?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/862398#M5099</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Not sure on the answer, however the captive portal is used for User-ID to IP mapping. If the PAN already knows the mapping, it will not prompt the user for a captive portal.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I used to have an environment where I used USER-ID on all my policies, and if the users didnt have a mapping, they got a very restrictive URL filtering policy applied to them. This was done by security policies however.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 18:14:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/862398#M5099</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-11-27T18:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent bypassing captive portal?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/865526#M5101</link>
      <description>&lt;P&gt;Thanks, I do know that and it's only being applied to unknown users.&amp;nbsp; They do currently hit a restrictive URL policy as well when unknown, but this does not stop them from being able to bypass captive portal as that only applies to HTTP(S). Going to give the 2 rules a try to ensure only HTTP is allowed until the user is known, which should be enough to ensure only captive portal can trigger without other traffic.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 18:22:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/865526#M5101</guid>
      <dc:creator>OGMaverick</dc:creator>
      <dc:date>2024-11-27T18:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent bypassing captive portal?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/891492#M5102</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You could put in another policy that blocks traffic not related to http(s) and DNS since its required for those unknown users.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just a thought.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 19:16:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/prevent-bypassing-captive-portal/m-p/891492#M5102</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-11-27T19:16:26Z</dc:date>
    </item>
  </channel>
</rss>

