<?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 FMC 6.2 Access Rule Empty Object Group in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-6-2-access-rule-empty-object-group/m-p/3225276#M1013838</link>
    <description>&lt;P&gt;I am wondering how ASA/Firepower handles empty object groups in a rule.&amp;nbsp; For example, I have a rule with an object group for destination; all working fine.&amp;nbsp; I then have to make changes to the object group, and it turns out all IPs get removed from the object...so basically the object group is empty.&amp;nbsp; If I did not have a chance to update the rule or rules using that object group, how does the FW handle the processing of that "empty" object group. &amp;nbsp; Does it default to "any".&amp;nbsp; Does it treat the rule as a "no -match" when processing and move on to the next rule.&lt;/P&gt;
&lt;P&gt;I understand, ideally, I should remove the empty object group, but sometimes when dealing with many firewalls at once, it can briefly get overlooked and I am just concerned how a FW may react to this situation.&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;</description>
    <pubDate>Fri, 21 Feb 2020 14:52:45 GMT</pubDate>
    <dc:creator>nevin.maurice1</dc:creator>
    <dc:date>2020-02-21T14:52:45Z</dc:date>
    <item>
      <title>FMC 6.2 Access Rule Empty Object Group</title>
      <link>https://community.cisco.com/t5/network-security/fmc-6-2-access-rule-empty-object-group/m-p/3225276#M1013838</link>
      <description>&lt;P&gt;I am wondering how ASA/Firepower handles empty object groups in a rule.&amp;nbsp; For example, I have a rule with an object group for destination; all working fine.&amp;nbsp; I then have to make changes to the object group, and it turns out all IPs get removed from the object...so basically the object group is empty.&amp;nbsp; If I did not have a chance to update the rule or rules using that object group, how does the FW handle the processing of that "empty" object group. &amp;nbsp; Does it default to "any".&amp;nbsp; Does it treat the rule as a "no -match" when processing and move on to the next rule.&lt;/P&gt;
&lt;P&gt;I understand, ideally, I should remove the empty object group, but sometimes when dealing with many firewalls at once, it can briefly get overlooked and I am just concerned how a FW may react to this situation.&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;</description>
      <pubDate>Fri, 21 Feb 2020 14:52:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-6-2-access-rule-empty-object-group/m-p/3225276#M1013838</guid>
      <dc:creator>nevin.maurice1</dc:creator>
      <dc:date>2020-02-21T14:52:45Z</dc:date>
    </item>
  </channel>
</rss>

