<?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: Using Palo Alto firewall as a proxy (anonymous browsing + URL filtering in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/351420#M87066</link>
    <description>&lt;P&gt;could you elaborate on what you're looking for with 'leakage of internal IP space' ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as soon as you apply NAT on the Palo Alto, the internal IP is replaced by the public IP, x-forward-for headers are only added by proxies, so removing the proxy will also take care of that issue&lt;/P&gt;&lt;P&gt;lastly, if there is apotential for private IPs to somehow show up in http payload, you could create a custom threat to block packets/sessions containing private IP addresses&lt;/P&gt;</description>
    <pubDate>Wed, 23 Sep 2020 12:18:09 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2020-09-23T12:18:09Z</dc:date>
    <item>
      <title>Using Palo Alto firewall as a proxy (anonymous browsing + URL filtering)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/350991#M87025</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We currently have a setup using a Forcepoint Content Gateway for proxy server with an external facing Palo Alto 850. The main we reason with use the Forcepoint appliance is for:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. "Anonymous browsing" (no leakage of internal IP spaces)&lt;/P&gt;&lt;P&gt;2. DLP&lt;/P&gt;&lt;P&gt;3. URL Filtering&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, I would like to remove this appliance to simplify our setup and I understand that our PAs can easily handle 2. and 3.&amp;nbsp; However, is there way to configure the PA for 1? Or do I still need some an inline proxy for this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your time and advice!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gregory&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2020 09:21:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/350991#M87025</guid>
      <dc:creator>Gregoryp</dc:creator>
      <dc:date>2020-09-22T09:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: Using Palo Alto firewall as a proxy (anonymous browsing + URL filtering</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/351420#M87066</link>
      <description>&lt;P&gt;could you elaborate on what you're looking for with 'leakage of internal IP space' ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as soon as you apply NAT on the Palo Alto, the internal IP is replaced by the public IP, x-forward-for headers are only added by proxies, so removing the proxy will also take care of that issue&lt;/P&gt;&lt;P&gt;lastly, if there is apotential for private IPs to somehow show up in http payload, you could create a custom threat to block packets/sessions containing private IP addresses&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 12:18:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/351420#M87066</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-09-23T12:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: Using Palo Alto firewall as a proxy (anonymous browsing + URL filtering</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/355654#M87568</link>
      <description>&lt;P&gt;Many thanks for your reply, Tom.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Your question prompted me into looking at our NAT settings and it looks like we are all set. Removing the proxy would only mean that whoever can administer the PA, can see what our users our browsing but this is not of concern for us.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 01:34:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-palo-alto-firewall-as-a-proxy-anonymous-browsing-url/m-p/355654#M87568</guid>
      <dc:creator>Gregoryp</dc:creator>
      <dc:date>2020-10-12T01:34:10Z</dc:date>
    </item>
  </channel>
</rss>

