<?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 PIX/ASA Rule Analysis in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-asa-rule-analysis/m-p/1592703#M592021</link>
    <description>&lt;P&gt;As part of a Security audit project for a big firm we are doing a review of the rules on the firewalls.&lt;/P&gt;&lt;P&gt;During this exercise we came across many rules with keyword "any" in either source ip, destination ip or destination ports which per policy need to be locked down to specifics.&lt;/P&gt;&lt;P&gt;what would be the best way to find out whats flowing through ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 scenarios&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a)for a small site - logging/capture packets ??any tool to simplify logs and packet capture data and put it into a more understandable format ?&lt;/P&gt;&lt;P&gt;b)for a datacenter firewall which receives close to a million hits a day for just a single rule any suggestions on what tool can be employed to capture destination port information ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again whole idea is to find out if there any tool/system to capture whats flowing through the firewall without reaching out to the it folks for documents:)&lt;/P&gt;&lt;P&gt;Also if logging is enabled would it increase the traffic flow/cpu utilization ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Harsha&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 19:48:54 GMT</pubDate>
    <dc:creator>harshavardhanhr-hr</dc:creator>
    <dc:date>2019-03-11T19:48:54Z</dc:date>
    <item>
      <title>PIX/ASA Rule Analysis</title>
      <link>https://community.cisco.com/t5/network-security/pix-asa-rule-analysis/m-p/1592703#M592021</link>
      <description>&lt;P&gt;As part of a Security audit project for a big firm we are doing a review of the rules on the firewalls.&lt;/P&gt;&lt;P&gt;During this exercise we came across many rules with keyword "any" in either source ip, destination ip or destination ports which per policy need to be locked down to specifics.&lt;/P&gt;&lt;P&gt;what would be the best way to find out whats flowing through ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 scenarios&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a)for a small site - logging/capture packets ??any tool to simplify logs and packet capture data and put it into a more understandable format ?&lt;/P&gt;&lt;P&gt;b)for a datacenter firewall which receives close to a million hits a day for just a single rule any suggestions on what tool can be employed to capture destination port information ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again whole idea is to find out if there any tool/system to capture whats flowing through the firewall without reaching out to the it folks for documents:)&lt;/P&gt;&lt;P&gt;Also if logging is enabled would it increase the traffic flow/cpu utilization ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Harsha&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:48:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-asa-rule-analysis/m-p/1592703#M592021</guid>
      <dc:creator>harshavardhanhr-hr</dc:creator>
      <dc:date>2019-03-11T19:48:54Z</dc:date>
    </item>
    <item>
      <title>Re: PIX/ASA Rule Analysis</title>
      <link>https://community.cisco.com/t5/network-security/pix-asa-rule-analysis/m-p/1592704#M592022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in case you want to use the packet capture here is a document that shows how to use it:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/partner/products/ps6120/products_tech_note09186a0080a9edd6.shtml"&gt;http://www.cisco.com/en/US/partner/products/ps6120/products_tech_note09186a0080a9edd6.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just in case. If you want to find the internal subnets you can check if there are routes on the ASA going to an inside router. You can replace the ANY on the ACLs for those subnets as the source address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Feb 2011 19:54:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-asa-rule-analysis/m-p/1592704#M592022</guid>
      <dc:creator>PAUL GILBERT ARIAS</dc:creator>
      <dc:date>2011-02-10T19:54:33Z</dc:date>
    </item>
  </channel>
</rss>

