<?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: Stop web browsing to ssl in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/stop-web-browsing-to-ssl/m-p/195729#M58414</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37650"&gt;@Jordan_Roebuck&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I don't think there's an easy way to do this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could decrypt the traffic and do a pattern match on all the different User-Agent strings that you can find in the header information.&amp;nbsp; You can identify different browsers that way and block traffic accordingly ... but the list will be enormous and hard to keep updated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;An old example :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-Google-Chrome/ta-p/57997" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-Google-Chrome/ta-p/57997&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers !&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2018 13:18:31 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2018-01-18T13:18:31Z</dc:date>
    <item>
      <title>Stop web browsing to ssl</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/stop-web-browsing-to-ssl/m-p/195698#M58410</link>
      <description>&lt;P&gt;The external IP of our WiFi controller requires 443 to be open to the internet, so we have this open on our inbound rule&amp;gt;external IP of the controller.&amp;nbsp; 443 needs to be open but we don't want this to be accessible via a web browser - as currently this rule allows the external IP to be accessed via https. Is there a way of stopping this behavior? Many thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2018 11:53:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/stop-web-browsing-to-ssl/m-p/195698#M58410</guid>
      <dc:creator>Jordan_Roebuck</dc:creator>
      <dc:date>2018-01-18T11:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: Stop web browsing to ssl</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/stop-web-browsing-to-ssl/m-p/195729#M58414</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37650"&gt;@Jordan_Roebuck&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I don't think there's an easy way to do this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could decrypt the traffic and do a pattern match on all the different User-Agent strings that you can find in the header information.&amp;nbsp; You can identify different browsers that way and block traffic accordingly ... but the list will be enormous and hard to keep updated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;An old example :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-Google-Chrome/ta-p/57997" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-Google-Chrome/ta-p/57997&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers !&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2018 13:18:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/stop-web-browsing-to-ssl/m-p/195729#M58414</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2018-01-18T13:18:31Z</dc:date>
    </item>
  </channel>
</rss>

