<?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 IPS/ACL/ZBF precedence on IOS router in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604525#M65841</link>
    <description>&lt;P&gt;I have a number of 891 routers deployed for VPN connectivity to a central site. The routers have an ACL as well as zone-based firewalling and IPS/IPS configured on their public interfaces. They are running IOS universal 15.1.1. They have been up for over six months.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Last week I started getting logs like this from the IPS instance:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jan 12 09:51:21 ss260 378: Jan 12 15:51:20.551: %IPS-4-SIGNATURE: Sig:3041 Subsig:0 Sev:100 TCP SYN/FIN Packet [Source-that I can't identify-IP:25 -&amp;gt; MY-ROUTER-IP:25] VRF:NONE RiskRating:100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that the interface ACL is processed before the ZBF. I've been assuming that IPS happens after the ACL as well, but this packet should never have gotten past my ACL. The ACL allows only ESP, IKE, SSH and pings, and then only if they come from about half a dozen source IPs. The source of the trigger packet is NOT among those allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because my ACL doesn't allow any un-encrypted traffic (other than some pings that I generate), I was not really expecting the IPS instance to see anything likely to trigger an alert, and up until last week, that was true.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So far all the logs are for the same SYN/FIN signature. Is this a special case type signature for some reason or can I expect to see alerts every time a packet that the ACL is going to block anyway, matches a signature?&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 12:14:00 GMT</pubDate>
    <dc:creator>darthnul</dc:creator>
    <dc:date>2019-03-10T12:14:00Z</dc:date>
    <item>
      <title>IPS/ACL/ZBF precedence on IOS router</title>
      <link>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604525#M65841</link>
      <description>&lt;P&gt;I have a number of 891 routers deployed for VPN connectivity to a central site. The routers have an ACL as well as zone-based firewalling and IPS/IPS configured on their public interfaces. They are running IOS universal 15.1.1. They have been up for over six months.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Last week I started getting logs like this from the IPS instance:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jan 12 09:51:21 ss260 378: Jan 12 15:51:20.551: %IPS-4-SIGNATURE: Sig:3041 Subsig:0 Sev:100 TCP SYN/FIN Packet [Source-that I can't identify-IP:25 -&amp;gt; MY-ROUTER-IP:25] VRF:NONE RiskRating:100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that the interface ACL is processed before the ZBF. I've been assuming that IPS happens after the ACL as well, but this packet should never have gotten past my ACL. The ACL allows only ESP, IKE, SSH and pings, and then only if they come from about half a dozen source IPs. The source of the trigger packet is NOT among those allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because my ACL doesn't allow any un-encrypted traffic (other than some pings that I generate), I was not really expecting the IPS instance to see anything likely to trigger an alert, and up until last week, that was true.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So far all the logs are for the same SYN/FIN signature. Is this a special case type signature for some reason or can I expect to see alerts every time a packet that the ACL is going to block anyway, matches a signature?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:14:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604525#M65841</guid>
      <dc:creator>darthnul</dc:creator>
      <dc:date>2019-03-10T12:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: IPS/ACL/ZBF precedence on IOS router</title>
      <link>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604526#M65842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of I noticed that the packets dropped by IPS have both source and destination port of 25 - odd &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're interested in order of operation with new CEF code you can check "show cef interface INTERFACE_NAME IFC_NUMBER" this is reliable and in the order they are done, but maybe in more detail than you'd need &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Router#sh cef interface fa0/0&lt;BR /&gt;FastEthernet0/0 is down (if_number 4)&lt;BR /&gt;&amp;nbsp; Corresponding hwidb fast_if_number 4&lt;BR /&gt;&amp;nbsp; Corresponding hwidb firstsw-&amp;gt;if_number 4&lt;BR /&gt;&amp;nbsp; Internet address is 10.1.1.1/24&lt;BR /&gt;&amp;nbsp; ICMP redirects are always sent&lt;BR /&gt;&amp;nbsp; Per packet load-sharing is disabled&lt;BR /&gt;&amp;nbsp; IP unicast RPF check is disabled&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; Input features: Access List&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; Output features: Firewall (NAT), Firewall (inspect)&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp; Inbound access list is 101&lt;BR /&gt;&amp;nbsp; Outbound access list is not set&lt;BR /&gt;&amp;nbsp; IP policy routing is disabled&lt;BR /&gt;&amp;nbsp; BGP based policy accounting on input is disabled&lt;BR /&gt;&amp;nbsp; BGP based policy accounting on output is disabled&lt;BR /&gt;&amp;nbsp; Hardware idb is FastEthernet0/0&lt;BR /&gt;&amp;nbsp; Fast switching type 1, interface type 18&lt;BR /&gt;&amp;nbsp; IP CEF switching enabled&lt;BR /&gt;&amp;nbsp; IP CEF switching turbo vector&lt;BR /&gt;&amp;nbsp; IP CEF turbo switching turbo vector&lt;BR /&gt;&amp;nbsp; IP prefix lookup IPv4 mtrie 8-8-8-8 optimized&lt;BR /&gt;&amp;nbsp; Input fast flags 0x1, Output fast flags 0x0&lt;BR /&gt;&amp;nbsp; ifindex 3(3)&lt;BR /&gt;&amp;nbsp; Slot&amp;nbsp; Slot unit 0 VC -1&lt;BR /&gt;&amp;nbsp; Transmit limit accumulator 0x0 (0x0)&lt;BR /&gt;&amp;nbsp; IP MTU 1500&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jan 2011 17:12:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604526#M65842</guid>
      <dc:creator>Marcin Latosiewicz</dc:creator>
      <dc:date>2011-01-14T17:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: IPS/ACL/ZBF precedence on IOS router</title>
      <link>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604527#M65843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Marcin!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran the command and it (unfortunately) shows that IPS is evaluated before the ACL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GigabitEthernet0 is up (if_number 12)&lt;BR /&gt;&amp;nbsp; Corresponding hwidb fast_if_number 12&lt;BR /&gt;&amp;nbsp; Corresponding hwidb firstsw-&amp;gt;if_number 12&lt;BR /&gt;&amp;nbsp; Internet address is 173.84.169.126/30&lt;BR /&gt;&amp;nbsp; ICMP redirects are never sent&lt;BR /&gt;&amp;nbsp; Per packet load-sharing is disabled&lt;BR /&gt;&amp;nbsp; IP unicast RPF check is disabled&lt;BR /&gt;&amp;nbsp; Input features: Stateless IN IPS (Atomic), Access List, IPSec input classification, Post Crypto IPS Atomic&lt;BR /&gt;&amp;nbsp; Output features: IPSec output classification, CCE Post NAT Classification, Firewall (firewall component), IPSec: to crypto engine, Post-encryption output features&lt;BR /&gt;&amp;nbsp; IP policy routing is disabled&lt;BR /&gt;&amp;nbsp; BGP based policy accounting on input is disabled&lt;BR /&gt;&amp;nbsp; BGP based policy accounting on output is disabled&lt;BR /&gt;&amp;nbsp; Hardware idb is GigabitEthernet0&lt;BR /&gt;&amp;nbsp; Fast switching type 1, interface type 27&lt;BR /&gt;&amp;nbsp; IP CEF switching enabled&lt;BR /&gt;&amp;nbsp; IP CEF switching turbo vector&lt;BR /&gt;&amp;nbsp; IP prefix lookup IPv4 mtrie 8-8-8-8 optimized&lt;BR /&gt;&amp;nbsp; Input fast flags 0xA1, Output fast flags 0x400&lt;BR /&gt;&amp;nbsp; ifindex 12(12)&lt;BR /&gt;&amp;nbsp; Slot&amp;nbsp; Slot unit 0 VC -1&lt;BR /&gt;&amp;nbsp; IP MTU 1452&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I really wish IPS happened AFTER the ACL because I get paged every time any router logs an IPS signature match.&lt;/P&gt;&lt;P&gt;&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; Thanks&amp;nbsp;&amp;nbsp; ...jgm&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jan 2011 17:38:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-acl-zbf-precedence-on-ios-router/m-p/1604527#M65843</guid>
      <dc:creator>darthnul</dc:creator>
      <dc:date>2011-01-14T17:38:47Z</dc:date>
    </item>
  </channel>
</rss>

