<?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 Rule Enrichment on rules with Negate in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/rule-enrichment-on-rules-with-negate/m-p/224478#M329</link>
    <description>&lt;P&gt;So, I am doing a rule enrichment on a project. The rule I am enriching is very open, but utilizes negate objects in source/dest. I just noticed that the rules I generated in Expedition via rule enrichment contained the two group-objects I am negating, plus all the specific IPs and ranges, but the whole new rules were set to negate by default. Basically, I went in and manually un-negated them, and removed the two original groups that were the negated objects of the original rule. But it seems like the learning/rule enrichment logic might be flawed when it comes to negates. Setting the new, enriched rules to negate would then be really bad, as it would allow anything BUT the sources/destinations you wanted to let through.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tim&lt;/P&gt;</description>
    <pubDate>Wed, 01 Aug 2018 19:57:04 GMT</pubDate>
    <dc:creator>Tim_Grossner</dc:creator>
    <dc:date>2018-08-01T19:57:04Z</dc:date>
    <item>
      <title>Rule Enrichment on rules with Negate</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/rule-enrichment-on-rules-with-negate/m-p/224478#M329</link>
      <description>&lt;P&gt;So, I am doing a rule enrichment on a project. The rule I am enriching is very open, but utilizes negate objects in source/dest. I just noticed that the rules I generated in Expedition via rule enrichment contained the two group-objects I am negating, plus all the specific IPs and ranges, but the whole new rules were set to negate by default. Basically, I went in and manually un-negated them, and removed the two original groups that were the negated objects of the original rule. But it seems like the learning/rule enrichment logic might be flawed when it comes to negates. Setting the new, enriched rules to negate would then be really bad, as it would allow anything BUT the sources/destinations you wanted to let through.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Wed, 01 Aug 2018 19:57:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/rule-enrichment-on-rules-with-negate/m-p/224478#M329</guid>
      <dc:creator>Tim_Grossner</dc:creator>
      <dc:date>2018-08-01T19:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: Rule Enrichment on rules with Negate</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/rule-enrichment-on-rules-with-negate/m-p/224571#M335</link>
      <description>Good catch.&lt;BR /&gt;We will have to enhance this case.&lt;BR /&gt;If the original file was negated, we can't just include the new seen IP addresses.</description>
      <pubDate>Thu, 02 Aug 2018 13:30:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/rule-enrichment-on-rules-with-negate/m-p/224571#M335</guid>
      <dc:creator>dgildelaig</dc:creator>
      <dc:date>2018-08-02T13:30:35Z</dc:date>
    </item>
  </channel>
</rss>

