<?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 how to organize access-list in ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-organize-access-list-in-asa/m-p/1404409#M743439</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need some help about access list. I understand is being read from top to down but&lt;/P&gt;&lt;P&gt;I would like to confirm if someone have a reference or knowledge on how to organize&lt;/P&gt;&lt;P&gt;access list w/ different protocols. what i meant is from top to down w/c protocols should be&lt;/P&gt;&lt;P&gt;at the top (example&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit tcp.....&amp;nbsp;&amp;nbsp;&amp;nbsp; ) and how about the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit ICMP....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit udp....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;source ip addresseses, is it from broad( top) going to specific ip(down).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 17:10:51 GMT</pubDate>
    <dc:creator>dantebarlizo</dc:creator>
    <dc:date>2019-03-11T17:10:51Z</dc:date>
    <item>
      <title>how to organize access-list in ASA</title>
      <link>https://community.cisco.com/t5/network-security/how-to-organize-access-list-in-asa/m-p/1404409#M743439</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need some help about access list. I understand is being read from top to down but&lt;/P&gt;&lt;P&gt;I would like to confirm if someone have a reference or knowledge on how to organize&lt;/P&gt;&lt;P&gt;access list w/ different protocols. what i meant is from top to down w/c protocols should be&lt;/P&gt;&lt;P&gt;at the top (example&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit tcp.....&amp;nbsp;&amp;nbsp;&amp;nbsp; ) and how about the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit ICMP....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access-list inside line 1 permit udp....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;source ip addresseses, is it from broad( top) going to specific ip(down).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:10:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-organize-access-list-in-asa/m-p/1404409#M743439</guid>
      <dc:creator>dantebarlizo</dc:creator>
      <dc:date>2019-03-11T17:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: how to organize access-list in ASA</title>
      <link>https://community.cisco.com/t5/network-security/how-to-organize-access-list-in-asa/m-p/1404410#M743445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since ACLs work on a first match basis you will want your more specific lines at the top of the list regardless of protocol. Avoid using broad ranges at the top of the list which could lead to more specific network ranges being ignored as in the example below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 1.1.1.1 any eq 80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second entry would not be effective here because the first match is hit allowing all traffic through. Here is another example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 1.1.1.1 any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host 2.2.2.2 eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any&amp;nbsp; host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host 2.2.2.2 eq 443&lt;/P&gt;&lt;P&gt;access-list acl_outside permit udp any host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 7.7.7.7 host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 1.1.1.1 host 2.2.2.2 eq 443&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any any eq 389&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above ACL woul better be optimized by making the most specific entries at the top of the list ensuring that specifc deny statements are not trumped by permit statements and each entry performs its desired function. Grouping similar entries together if possible can help to keep some sanity when looking at large lists also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 1.1.1.1 any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host 2.2.2.2 eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any any eq 80&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 1.1.1.1 host 2.2.2.2 eq 443&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host 2.2.2.2 eq 443&lt;/P&gt;&lt;P&gt;access-list acl_outside permit udp any host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside deny tcp host 7.7.7.7 host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any&amp;nbsp; host 2.2.2.3 eq 53&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any any eq 389&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Mar 2010 21:37:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-organize-access-list-in-asa/m-p/1404410#M743445</guid>
      <dc:creator>Joe B Danford</dc:creator>
      <dc:date>2010-03-01T21:37:24Z</dc:date>
    </item>
  </channel>
</rss>

