<?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 PIX NO-NAT-Control in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-no-nat-control/m-p/980974#M938274</link>
    <description>&lt;P&gt; have pix firewall 535 with IOS 7.x version. I have enable it with no-nat-control, to my understanding with this no-nat-control traffic from higher secuirty level to lower secuirty level allowed if there is no access-list. But from low to high still need of static and access-list. But in my case traffic from low to high is permitted without static. My outside network users are able to reach inside network without static. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please tell me why it is so, why low to high permitted without static or is it the normal behaviour. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 12:40:05 GMT</pubDate>
    <dc:creator>wasiimcisco</dc:creator>
    <dc:date>2019-03-11T12:40:05Z</dc:date>
    <item>
      <title>PIX NO-NAT-Control</title>
      <link>https://community.cisco.com/t5/network-security/pix-no-nat-control/m-p/980974#M938274</link>
      <description>&lt;P&gt; have pix firewall 535 with IOS 7.x version. I have enable it with no-nat-control, to my understanding with this no-nat-control traffic from higher secuirty level to lower secuirty level allowed if there is no access-list. But from low to high still need of static and access-list. But in my case traffic from low to high is permitted without static. My outside network users are able to reach inside network without static. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please tell me why it is so, why low to high permitted without static or is it the normal behaviour. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:40:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-no-nat-control/m-p/980974#M938274</guid>
      <dc:creator>wasiimcisco</dc:creator>
      <dc:date>2019-03-11T12:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NO-NAT-Control</title>
      <link>https://community.cisco.com/t5/network-security/pix-no-nat-control/m-p/980975#M938276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;with "no nat-control", IP addresses on a higher security level interface do not need any sort of nat translation to go to a lower security level interface.  This has nothing to do with ACL's (unless you're talking about policy NAT).  &lt;/P&gt;&lt;P&gt;IP's on a lower security level interface never need a NAT translation entry to go to a higher security level interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If "nat-conrol" is enabled, IP's on a higher security level interface need some sort of NAT statement when going to a lower security level interface.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Things get even fuzzier with regards to same security level interfaces.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 May 2008 12:13:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-no-nat-control/m-p/980975#M938276</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2008-05-05T12:13:44Z</dc:date>
    </item>
  </channel>
</rss>

