<?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: firewall object groupings in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268668#M818094</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Absolutely the firewall needs to parse through all of these lines. If there are huge number of ACE then, as soon as you load that config memory consumption will be high and in case of the FWSM there are a few known issues relating to CPU spikes due to acl compilation. It is always a good idea to have your highest hit ACE in the top of the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Sep 2009 01:51:08 GMT</pubDate>
    <dc:creator>Kureli Sankar</dc:creator>
    <dc:date>2009-09-15T01:51:08Z</dc:date>
    <item>
      <title>firewall object groupings</title>
      <link>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268667#M818093</link>
      <description>&lt;P&gt;Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concept of object grouping is used in firewall to have the group of host/services involved in logically single rules instead of varied lines.&lt;/P&gt;&lt;P&gt;Now it is seen that ACE uses only single line no. to define each object grouped rule until there is a change.&lt;/P&gt;&lt;P&gt;But even this way, the actual no. of lines would still be large enough degtermined by the no. of hosts or services in the object group.&lt;/P&gt;&lt;P&gt;Does this have any bearing on the extra lines firewall will have to parse thru.or is it simply for easier admin control.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:15:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268667#M818093</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T16:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: firewall object groupings</title>
      <link>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268668#M818094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Absolutely the firewall needs to parse through all of these lines. If there are huge number of ACE then, as soon as you load that config memory consumption will be high and in case of the FWSM there are a few known issues relating to CPU spikes due to acl compilation. It is always a good idea to have your highest hit ACE in the top of the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Sep 2009 01:51:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268668#M818094</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2009-09-15T01:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: firewall object groupings</title>
      <link>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268669#M818095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, grouping is more as a tool for easier admin control rather than reducing the line count of ACE on the firewall.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Sep 2009 05:03:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-object-groupings/m-p/1268669#M818095</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2009-09-15T05:03:07Z</dc:date>
    </item>
  </channel>
</rss>

