<?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 Zone Based Firewall bypass verification in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zone-based-firewall-bypass-verification/m-p/2298973#M311248</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;The best way to avoid inspection is using the "pass" action in the policy map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you way want to create 2 different class-maps. One matching the the traffic that you don't want to inspect and the other one with the traffic you wish to inspect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other thing to add is that when you use PASS you need to also allow the retrurn traffic. So you need a class map with a Pass action from Inside to Outisde and another one from Outside to Inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luis Silva &lt;BR /&gt; &lt;BR /&gt;"If you need PDI (Planning, Design, Implement) assistance feel free to reach us" &lt;BR /&gt; &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/web/partners/tools/pdihd.html"&gt;http://www.cisco.com/web/partners/tools/pdihd.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Oct 2013 23:32:45 GMT</pubDate>
    <dc:creator>Luis Silva Benavides</dc:creator>
    <dc:date>2013-10-10T23:32:45Z</dc:date>
    <item>
      <title>Zone Based Firewall bypass verification</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-bypass-verification/m-p/2298972#M311246</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am building a ZBF that will require certain networks to be allowed inbound and not inspected. MOST of the traffic will be from the INSIDE o the OUTSIDE but some management of INSIDE hosts will be required etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to verify that I can use an extended ACL to allow that traffic to the INSIDE zone hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(3)T1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 101 deny (don't inspect this OUTBOUND private network traffic addresses)&lt;/P&gt;&lt;P&gt;access-list 101 permit (do inspect this all of the rest OUTBOUND traffic addresses)&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list 102 permit (inbound don't inspect this INBOUND traffic addresses)&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;class-map type inspect match-all ALL-PRIVATE&lt;/P&gt;&lt;P&gt; match access-group 101&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map type inspect priv-pub-pmap&lt;/P&gt;&lt;P&gt; class type inspect ALL-PRIVATE&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect&lt;/P&gt;&lt;P&gt; class class-default&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;zone security INSIDE&lt;/P&gt;&lt;P&gt;description INSIDE interface PRIVATE network&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;zone security OUTSIDE&lt;/P&gt;&lt;P&gt; description OUTSIDE interface PUBLIC Internet and Corp connection&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;zone-pair security priv-pub source INSIDE destination OUTSIDE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt; service-policy type inspect priv-pub-pmap&lt;/P&gt;&lt;P&gt;! &lt;/P&gt;&lt;P&gt;interface multilink 1&lt;/P&gt;&lt;P&gt; ip address 67.x.x.x&lt;/P&gt;&lt;P&gt; zone-member security OUTSIDE&lt;/P&gt;&lt;P&gt; ip access-group 102 in&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface g0/0&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; ip address 192.168.x.x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt; zone-member security INSIDE&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface g0/1&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; ip address 67.x.x.x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt; zone-member security INSIDE&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:49:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-bypass-verification/m-p/2298972#M311246</guid>
      <dc:creator>ttoney</dc:creator>
      <dc:date>2019-03-12T02:49:32Z</dc:date>
    </item>
    <item>
      <title>Zone Based Firewall bypass verification</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-bypass-verification/m-p/2298973#M311248</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;The best way to avoid inspection is using the "pass" action in the policy map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you way want to create 2 different class-maps. One matching the the traffic that you don't want to inspect and the other one with the traffic you wish to inspect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other thing to add is that when you use PASS you need to also allow the retrurn traffic. So you need a class map with a Pass action from Inside to Outisde and another one from Outside to Inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luis Silva &lt;BR /&gt; &lt;BR /&gt;"If you need PDI (Planning, Design, Implement) assistance feel free to reach us" &lt;BR /&gt; &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/web/partners/tools/pdihd.html"&gt;http://www.cisco.com/web/partners/tools/pdihd.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Oct 2013 23:32:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-bypass-verification/m-p/2298973#M311248</guid>
      <dc:creator>Luis Silva Benavides</dc:creator>
      <dc:date>2013-10-10T23:32:45Z</dc:date>
    </item>
  </channel>
</rss>

