<?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: Disabling NAT CONTROL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/disabling-nat-control/m-p/2132040#M393944</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;In short, to my understanding, when NAT-CONTROL is enabled you will always need a NAT rule that applies to the traffic going through the firewall. If the traffic doesnt have any NAT rule configured it doesnt go through.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand if the NAT-CONTROL is DISABLED the traffic doesnt (necesarily) need a NAT rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-rules are best handled by using ACLs and not relying if NAT configuration exists or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also I have never relied on the interface security-levels to define what traffic is allowed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A small portion from a Cisco document for ASA 8.2 software level regarding "nat-control"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;H2&gt; Default Settings &lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1085922"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt; By default, NAT control is disabled; therefore, you do not need to&amp;nbsp; perform NAT on any networks unless you want to do so. If you upgraded&amp;nbsp; from an earlier version of software, however, NAT control might be&amp;nbsp; enabled on your system. Even with NAT control disabled, you need to&amp;nbsp; perform NAT on any addresses for which you configure dynamic NAT&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Dec 2012 22:14:51 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2012-12-18T22:14:51Z</dc:date>
    <item>
      <title>Disabling NAT CONTROL</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-control/m-p/2132039#M393941</link>
      <description>&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a ASA 5520 with nat Control enabled in my job. This firewall is very critical for bussiness process, so I'd like to confirm with you what happen if I disable this control. This command is an update legacy of the IOS version from a Cisco PIX to this ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read alot about it and for my perspective is not going to happen nothing if a disable this control of the ASA. The only thing is the security fails on the Acl's of the interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are your reviews and experience?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hector.-&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:38:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-control/m-p/2132039#M393941</guid>
      <dc:creator>javi_cesp</dc:creator>
      <dc:date>2019-03-12T00:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling NAT CONTROL</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-control/m-p/2132040#M393944</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;In short, to my understanding, when NAT-CONTROL is enabled you will always need a NAT rule that applies to the traffic going through the firewall. If the traffic doesnt have any NAT rule configured it doesnt go through.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand if the NAT-CONTROL is DISABLED the traffic doesnt (necesarily) need a NAT rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-rules are best handled by using ACLs and not relying if NAT configuration exists or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also I have never relied on the interface security-levels to define what traffic is allowed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A small portion from a Cisco document for ASA 8.2 software level regarding "nat-control"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;H2&gt; Default Settings &lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1085922"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt; By default, NAT control is disabled; therefore, you do not need to&amp;nbsp; perform NAT on any networks unless you want to do so. If you upgraded&amp;nbsp; from an earlier version of software, however, NAT control might be&amp;nbsp; enabled on your system. Even with NAT control disabled, you need to&amp;nbsp; perform NAT on any addresses for which you configure dynamic NAT&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Dec 2012 22:14:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-control/m-p/2132040#M393944</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-12-18T22:14:51Z</dc:date>
    </item>
  </channel>
</rss>

