<?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: Block from old Browser Version in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-from-old-browser-version/m-p/437694#M97473</link>
    <description>&lt;P&gt;Thank you for posting question&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/182013"&gt;@holmegan&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you would like to address an issue with different version of browsers and you are managing those clients, then there might be more elegant solution. For example to use an end point management to address this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are going to leverage Firewall for this task, then closest match I can think of for your requirement is to create a Custom Application or Vulnerability Signature, then match version in HTTP header, then link it to a policy to block it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below are examples by using Custom Application as well as Vulnerability Signature:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEdCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEdCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSOCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSOCA0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: In either case, you will have to enable decryption to get visibility into HTTPS traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Sep 2021 13:03:12 GMT</pubDate>
    <dc:creator>PavelK</dc:creator>
    <dc:date>2021-09-30T13:03:12Z</dc:date>
    <item>
      <title>Block from old Browser Version</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-from-old-browser-version/m-p/437274#M97472</link>
      <description>&lt;P&gt;Hi Community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I work to create a role that should block old browser versions. But I have not found out this special point how you can say from a certain version that these are blocked and only allowed from the safe status.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a solution?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks for your help&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 08:14:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-from-old-browser-version/m-p/437274#M97472</guid>
      <dc:creator>holmegan</dc:creator>
      <dc:date>2021-09-29T08:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: Block from old Browser Version</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-from-old-browser-version/m-p/437694#M97473</link>
      <description>&lt;P&gt;Thank you for posting question&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/182013"&gt;@holmegan&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you would like to address an issue with different version of browsers and you are managing those clients, then there might be more elegant solution. For example to use an end point management to address this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are going to leverage Firewall for this task, then closest match I can think of for your requirement is to create a Custom Application or Vulnerability Signature, then match version in HTTP header, then link it to a policy to block it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below are examples by using Custom Application as well as Vulnerability Signature:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEdCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEdCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSOCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSOCA0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: In either case, you will have to enable decryption to get visibility into HTTPS traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Sep 2021 13:03:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-from-old-browser-version/m-p/437694#M97473</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2021-09-30T13:03:12Z</dc:date>
    </item>
  </channel>
</rss>

