<?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 ASA Interface Security Level in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797360#M533757</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm building a new ASA configuration with a dmz interaface and an inside interface.&lt;/P&gt;&lt;P&gt;dmz security-level 20&lt;/P&gt;&lt;P&gt;inside security-level 100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA ver 8.2(1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found that I can pass traffic from hosts off the dmz to hosts on the inside without having to define a static or identy-nat rule.&lt;/P&gt;&lt;P&gt;I've always thought that in order to get traffic to flow from a lower-level security interface to a high-level security interface you have to explicitly allow it.&lt;/P&gt;&lt;P&gt;Is that no longer the case?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:10:30 GMT</pubDate>
    <dc:creator>aeryilmaz</dc:creator>
    <dc:date>2019-03-11T21:10:30Z</dc:date>
    <item>
      <title>ASA Interface Security Level</title>
      <link>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797360#M533757</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm building a new ASA configuration with a dmz interaface and an inside interface.&lt;/P&gt;&lt;P&gt;dmz security-level 20&lt;/P&gt;&lt;P&gt;inside security-level 100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA ver 8.2(1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found that I can pass traffic from hosts off the dmz to hosts on the inside without having to define a static or identy-nat rule.&lt;/P&gt;&lt;P&gt;I've always thought that in order to get traffic to flow from a lower-level security interface to a high-level security interface you have to explicitly allow it.&lt;/P&gt;&lt;P&gt;Is that no longer the case?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:10:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797360#M533757</guid>
      <dc:creator>aeryilmaz</dc:creator>
      <dc:date>2019-03-11T21:10:30Z</dc:date>
    </item>
    <item>
      <title>ASA Interface Security Level</title>
      <link>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797361#M533759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need an acl to allow the traffic from the dmz to the inside hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for NAT you can disable NAT using "no nat-control" which then means you do need static NAT rules as you would have done on older versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Aug 2011 22:19:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797361#M533759</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-08-11T22:19:03Z</dc:date>
    </item>
    <item>
      <title>ASA Interface Security Level</title>
      <link>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797362#M533762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the info, Jon. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did some futher testing and found that with nat-control Enabled, I need a static NAT to permit traffic to flow from "inside" to "dmz." With it disabled, traffic will flow from higher to lower without an interface ACL or NAT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also with nat-control disabled, I still need an ACL to allow traffic from dmz to inside but as you mention no NAT rules required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;P&gt;I was baffeled by the change in logic with security-levels.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 14:21:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797362#M533762</guid>
      <dc:creator>aeryilmaz</dc:creator>
      <dc:date>2011-08-12T14:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Interface Security Level</title>
      <link>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797363#M533765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No problem, glad to have helped and thanks for the rating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I remember the first time i came across this issue, it confused me as well. I was so used to having to setup static NATs from lower to higher i actually thought it was bug in the firewall at first &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 14:27:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-interface-security-level/m-p/1797363#M533765</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-08-12T14:27:00Z</dc:date>
    </item>
  </channel>
</rss>

