<?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: rule being matched incorrectly and allowed on ANY url in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/rule-being-matched-incorrectly-and-allowed-on-any-url/m-p/226275#M65147</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71756"&gt;@RobinClayton&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This rule that allows http and https to Sophos update urls actually allows traffic to any destination, but only until the point where the firewall would see the URL in a http-get or TLS Client Hello packet and if the firewall sees an URL does not match your custom URL category it reevaluates the policy and takes the action according the best match firewallrule. The two connections in your screenshot were sessions where there wasn't enough data for the firewall to identify anything, but as mentionned this rule will allow some bytes to be sent out anywhere. You could try to further restrict source and destination IPs to make sure that even this few bytes can only be sent out from systems thst really need these updates.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Aug 2018 12:36:15 GMT</pubDate>
    <dc:creator>Remo</dc:creator>
    <dc:date>2018-08-07T12:36:15Z</dc:date>
    <item>
      <title>rule being matched incorrectly and allowed on ANY url</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/rule-being-matched-incorrectly-and-allowed-on-any-url/m-p/226264#M65146</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is this traffic matching "RULE 108" when URL_Category is not matched?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fwfilter.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/16189iAC9510F245FB871B/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="fwfilter.png" alt="fwfilter.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Aug 2018 11:40:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/rule-being-matched-incorrectly-and-allowed-on-any-url/m-p/226264#M65146</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2018-08-07T11:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: rule being matched incorrectly and allowed on ANY url</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/rule-being-matched-incorrectly-and-allowed-on-any-url/m-p/226275#M65147</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71756"&gt;@RobinClayton&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This rule that allows http and https to Sophos update urls actually allows traffic to any destination, but only until the point where the firewall would see the URL in a http-get or TLS Client Hello packet and if the firewall sees an URL does not match your custom URL category it reevaluates the policy and takes the action according the best match firewallrule. The two connections in your screenshot were sessions where there wasn't enough data for the firewall to identify anything, but as mentionned this rule will allow some bytes to be sent out anywhere. You could try to further restrict source and destination IPs to make sure that even this few bytes can only be sent out from systems thst really need these updates.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Aug 2018 12:36:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/rule-being-matched-incorrectly-and-allowed-on-any-url/m-p/226275#M65147</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-07T12:36:15Z</dc:date>
    </item>
  </channel>
</rss>

