<?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: ZBF: Protocol Inspection/Access List Combo in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517964#M618603</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am afraid you need to split it up.&lt;/P&gt;&lt;P&gt;You need a class that only matches on the interesting ftp traffic and also matches on protocol ftp, and then inspects. &lt;/P&gt;&lt;P&gt;So make sure the ftp traffic does not match your current ACL. And after that and before the default you inspect the only ftp class-map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Nov 2010 20:20:51 GMT</pubDate>
    <dc:creator>Panos Kampanakis</dc:creator>
    <dc:date>2010-11-04T20:20:51Z</dc:date>
    <item>
      <title>ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517961#M618584</link>
      <description>&lt;P&gt;So here is the deal, normally I have a pretty simple ZBF outbound configuration. Basically it's below without the bold italics. If traffic is http and the source ip isn't on a specific BYPASS-FILTER acl it gets filtered, otherwise it gets inspected and allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I have a customer who has an incredibly large list of acl requirements and his default position on outbound traffic is deny. We have created an ACL that replicates this called inside_access_in and i have successfully applied it and have it working using the bold italics added below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is it once the ACL has allowed/denied the traffic it does not appear to be inspecting it further, this really affects FTP traffic as without inspection the connections don't always work properly.&amp;nbsp; Is there a better way to do this? I don't have the full ACL below but a good example portion of it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;class-map type inspect match-any INSIDE_ACCESS_IN&lt;BR /&gt; match access-group name inside_access_in&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;class-map type inspect match-any DEFAULT-TRAFFIC&lt;/P&gt;&lt;P&gt; match protocol tcp&lt;BR /&gt; match protocol udp&lt;BR /&gt; match protocol ftp&lt;BR /&gt; match protocol sip&lt;BR /&gt; match protocol rtsp&lt;BR /&gt; match protocol tftp&lt;BR /&gt; match protocol icmp&lt;BR /&gt; match protocol skinny&lt;BR /&gt;class-map type inspect match-all NO-URL-FILTER&lt;BR /&gt; match protocol http&lt;BR /&gt; match access-group name BYPASS-FILTER&lt;BR /&gt;class-map type inspect match-all INTERNET-INBOUND&lt;BR /&gt; match access-group name PERMIT-INTERNET&lt;BR /&gt;class-map type inspect match-any URL-FILTER&lt;BR /&gt; match protocol http&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect PRIVATE-TO-PUBLIC&lt;BR /&gt; class type inspect NO-URL-FILTER&lt;BR /&gt;&amp;nbsp; inspect&lt;BR /&gt; class type inspect URL-FILTER&lt;BR /&gt;&amp;nbsp; inspect&lt;BR /&gt;&amp;nbsp; urlfilter SMARTFILTER&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt; class type inspect INSIDE_ACCESS_IN&lt;BR /&gt;&amp;nbsp;&amp;nbsp; inspect&lt;BR /&gt;&lt;/STRONG&gt;&lt;/EM&gt; class type inspect DEFAULT-TRAFFIC&lt;BR /&gt;&amp;nbsp; inspect&lt;BR /&gt; class class-default&lt;BR /&gt;&amp;nbsp; drop&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;ip access-list extended inside_access_in&lt;BR /&gt; permit ip object-group XXX_Servers any&lt;BR /&gt; permit ip object-group XXX_NETWORK_3 any&lt;BR /&gt; permit ip any object-group XXX_NETWORK_4&lt;BR /&gt; deny&amp;nbsp;&amp;nbsp; ip any object-group RFC1918&lt;BR /&gt; remark Internet Access&lt;BR /&gt; permit tcp object-group WWWAccess any eq www 443&lt;BR /&gt; remark Secure http access only&lt;BR /&gt; permit tcp object-group SecureWWW any eq 443&lt;BR /&gt; remark FTP Access&lt;BR /&gt; permit object-group FTP object-group FTPAccess any&lt;BR /&gt; remark FTP access for all users to these FTP sites&lt;BR /&gt; permit object-group FTP any object-group FTPSites&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;deny ip any any&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:04:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517961#M618584</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2019-03-11T19:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517962#M618588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is normal to do the action in a class if you match the class and not move to the next action for the next class afterwards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But from what I am seeing. your ACL matches on FTP traffic so, it is matched it should be inspected.&lt;/P&gt;&lt;P&gt;Let us know if there is confusion on the symptom.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 18:19:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517962#M618588</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-11-04T18:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517963#M618598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK Makes, senses, here is where the problem occurs, if somebody is in the top level allow anything line of the acl. At that point I am only matching presumably on basic tcp/udp inspection and when you do that ftp doesn't always work unless you also enable ftp inspection like I do in my DEFAULT-TRAFFIC class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So how do I get around that with my acl? I can add a tcp rule for the allow anything group with eq ftp but will that trigger the proper inspection? Would I do the same thing I end up doing for ftp for any other protocols like SIP, etc that need more than base tcp/udp inspection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;-Matthew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 19:48:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517963#M618598</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2010-11-04T19:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517964#M618603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am afraid you need to split it up.&lt;/P&gt;&lt;P&gt;You need a class that only matches on the interesting ftp traffic and also matches on protocol ftp, and then inspects. &lt;/P&gt;&lt;P&gt;So make sure the ftp traffic does not match your current ACL. And after that and before the default you inspect the only ftp class-map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 20:20:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517964#M618603</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-11-04T20:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517965#M618611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;makes sense so I need to for any sensitive protocols that require inspection (FTP, SIP, etc) have a separate acl for each and separate class map, etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luckily for this customer that's just FTP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 20:30:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517965#M618611</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2010-11-04T20:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517966#M618618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please mark this as answered if it is for other people's future benefit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck with the config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take care,&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 20:49:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517966#M618618</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-11-04T20:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF: Protocol Inspection/Access List Combo</title>
      <link>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517967#M618624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Done. Thanks for the assistance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Nov 2010 12:51:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-protocol-inspection-access-list-combo/m-p/1517967#M618624</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2010-11-05T12:51:53Z</dc:date>
    </item>
  </channel>
</rss>

