<?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 Security level on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304982#M858362</link>
    <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are multiple sub interfaces and vlans are created with different security levels&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will the traffic flows from high security level interface to low security level interface?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the case if we have the acls in place?&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;Regards,&lt;/P&gt;&lt;P&gt;Madan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 15:59:28 GMT</pubDate>
    <dc:creator>kr_madan</dc:creator>
    <dc:date>2019-03-11T15:59:28Z</dc:date>
    <item>
      <title>Security level on ASA</title>
      <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304982#M858362</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are multiple sub interfaces and vlans are created with different security levels&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will the traffic flows from high security level interface to low security level interface?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the case if we have the acls in place?&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;Regards,&lt;/P&gt;&lt;P&gt;Madan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:59:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304982#M858362</guid>
      <dc:creator>kr_madan</dc:creator>
      <dc:date>2019-03-11T15:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: Security level on ASA</title>
      <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304983#M858364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Madan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ASA always allows traffic from higher to lower by default. If you have ACLs in place, then you'll need to allow the traffic through. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you have an ACL applied to the inside interface and the inside interface has a security level of 100, then that ACL will need to allow what you want out. If you want users to be able to surf the web, but nothing else, your acl will allow port 80 out, but deny everything else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2009 15:15:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304983#M858364</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2009-07-27T15:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: Security level on ASA</title>
      <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304984#M858366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your valuable input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do we need Explicit deny statement in acl? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2009 16:00:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304984#M858366</guid>
      <dc:creator>kr_madan</dc:creator>
      <dc:date>2009-07-27T16:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: Security level on ASA</title>
      <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304985#M858367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on what you are trying to do with your acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an implicit deny at the end of an acl so anything not explicitly permitted or denied in your acl will be dropped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2009 16:06:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304985#M858367</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-07-27T16:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: Security level on ASA</title>
      <link>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304986#M858372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to what Jon said, if you use a permit any at the end of your acl and want to deny traffic, you'll need a deny line before the permit any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;deny ip 192.168.1.0 255.255.255.0 any eq 80&lt;/P&gt;&lt;P&gt;permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would deny 192.168.1.0 subnet from getting on the web, but it would allow them to go everywhere else like mail, etc. After the "permit ip any any" line is an "invisible" deny ip any any line. You can't see it but it's there. I normally put a deny ip any any at the end so I can see what I'm actually blocking hit-count wise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2009 16:11:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/security-level-on-asa/m-p/1304986#M858372</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2009-07-27T16:11:29Z</dc:date>
    </item>
  </channel>
</rss>

