<?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 ASA IPS Access List in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438798#M45609</link>
    <description>&lt;P&gt;When configuring an ASA for IPS, does the IPS access list need to be the first access list in the configuration?&amp;nbsp; For example, in our environment, we want to have every packet go through the IPS.&amp;nbsp; So, if my current configuration is as follows, does the access list for the IPS traffic need to be first in the list of access lists or does it not matter?&lt;/P&gt;&lt;P&gt;Current configuration&lt;/P&gt;&lt;P&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;BR /&gt;&lt;BR /&gt;New Configuration&lt;/P&gt;&lt;P&gt;access-list traffic_for_ips extended permit ip any4 any4&amp;nbsp; &amp;lt;------------------------IPS access list on top&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;BR /&gt;access-list traffic_for_ips extended permit ip any4 any4&amp;nbsp; &amp;lt;------------------------IPS access list at bottom&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 13:11:13 GMT</pubDate>
    <dc:creator>routercpu</dc:creator>
    <dc:date>2019-03-10T13:11:13Z</dc:date>
    <item>
      <title>ASA IPS Access List</title>
      <link>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438798#M45609</link>
      <description>&lt;P&gt;When configuring an ASA for IPS, does the IPS access list need to be the first access list in the configuration?&amp;nbsp; For example, in our environment, we want to have every packet go through the IPS.&amp;nbsp; So, if my current configuration is as follows, does the access list for the IPS traffic need to be first in the list of access lists or does it not matter?&lt;/P&gt;&lt;P&gt;Current configuration&lt;/P&gt;&lt;P&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;BR /&gt;&lt;BR /&gt;New Configuration&lt;/P&gt;&lt;P&gt;access-list traffic_for_ips extended permit ip any4 any4&amp;nbsp; &amp;lt;------------------------IPS access list on top&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host y.y.y.y eq 9996&lt;BR /&gt;access-list acl_out extended permit udp host&amp;nbsp;x.x.x.x host&amp;nbsp;y.y.y.y eq 9996&lt;BR /&gt;access-list acl_in_out extended deny tcp any4 any4 eq netbios-ssn&lt;BR /&gt;access-list acl_in_out extended deny udp any4 any4 eq 139&lt;BR /&gt;access-list traffic_for_ips extended permit ip any4 any4&amp;nbsp; &amp;lt;------------------------IPS access list at bottom&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:11:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438798#M45609</guid>
      <dc:creator>routercpu</dc:creator>
      <dc:date>2019-03-10T13:11:13Z</dc:date>
    </item>
    <item>
      <title>It does not matter where this</title>
      <link>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438799#M45610</link>
      <description>&lt;P&gt;It does not matter where this ACL is placed ,as according to your ips acl any traffic that pass through the ASA must be inspected by IPS.&lt;/P&gt;&lt;P&gt;Therefore, to-be-inspected traffic can be anything that passes through the ASA, of course that traffic must me allowed by your interface ACL, NAT rules and ASA module inspections before passing through the ips module. see &lt;A href="http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113396-asa-packet-flow-00.html"&gt;Cisco ASA order of processing.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;"Please do rate helpful posts"&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 06:32:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438799#M45610</guid>
      <dc:creator>Poonam Garg</dc:creator>
      <dc:date>2014-04-22T06:32:30Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438800#M45611</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi routercpu&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the access-list will classify traffic that will later be used in a policy-map for inspection. So at the end it won't be tied to any interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The config would be something like this:&lt;/P&gt;

&lt;PRE style="font-size: 11px; overflow: auto; max-width: 650px; min-width: 400px; height: auto; color: rgb(0, 0, 0); line-height: normal; background-color: rgb(255, 255, 255);"&gt;
ciscoasa(config)#&lt;B&gt;access-list traffic_for_ips permit ip any any&lt;/B&gt;
ciscoasa(config)#&lt;B&gt;class-map ips_class_map&lt;/B&gt; 
ciscoasa(config-cmap)#&lt;B&gt;match access-list traffic_for_ips&lt;/B&gt;


&lt;/PRE&gt;

&lt;PRE style="font-size: 11px; overflow: auto; max-width: 650px; min-width: 400px; height: auto; color: rgb(0, 0, 0); line-height: normal; background-color: rgb(255, 255, 255);"&gt;
ciscoasa(config)#&lt;B&gt;policy-map global_policy&lt;/B&gt;&lt;/PRE&gt;

&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;It's a bit old but this is the guide that I'm referencing from:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/71204-traffic-asa-aip-ssm.html#c3"&gt;http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/71204-traffic-asa-aip-ssm.html#c3&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Antonio&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2014 05:13:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ips-access-list/m-p/2438800#M45611</guid>
      <dc:creator>ahurtadove</dc:creator>
      <dc:date>2014-05-09T05:13:30Z</dc:date>
    </item>
  </channel>
</rss>

