<?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: ASA Access-group in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402806#M723988</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mostly people only apply acl "IN" on an interface.&amp;nbsp; We have seen cases where people apply acl IN and OUT on the same interface by mistake.&lt;/P&gt;&lt;P&gt;In some cases there as been a requirement. Like for example you have inside, dmz and outside.&amp;nbsp; You manage inside and outside interface acl but another team manages the dmz acl.&amp;nbsp; They allow everything on their interface but, you want to control what leaves the outside interface so, you can apply an acl OUT on the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, it depeds on the requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jan 2010 16:55:53 GMT</pubDate>
    <dc:creator>Kureli Sankar</dc:creator>
    <dc:date>2010-01-20T16:55:53Z</dc:date>
    <item>
      <title>ASA Access-group</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402804#M723986</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For ASA, is there any standard or a need of having a in and out access-group for each inside or outside interface, or is it base on situation and requirement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lawrence&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:59:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402804#M723986</guid>
      <dc:creator>noobieee7</dc:creator>
      <dc:date>2019-03-11T16:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Access-group</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402805#M723987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;noobieee7 wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For ASA, is there any standard or a need of having a in and out access-group for each inside or outside interface, or is it base on situation and requirement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lawrence&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lawrence&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is based purely on situation and requirement. Inbound access-lists are by far the most commonly used but i have had situations in the past where an outbound acl has been very useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 16:54:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402805#M723987</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-01-20T16:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Access-group</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402806#M723988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mostly people only apply acl "IN" on an interface.&amp;nbsp; We have seen cases where people apply acl IN and OUT on the same interface by mistake.&lt;/P&gt;&lt;P&gt;In some cases there as been a requirement. Like for example you have inside, dmz and outside.&amp;nbsp; You manage inside and outside interface acl but another team manages the dmz acl.&amp;nbsp; They allow everything on their interface but, you want to control what leaves the outside interface so, you can apply an acl OUT on the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, it depeds on the requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 16:55:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402806#M723988</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-01-20T16:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Access-group</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402807#M723989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would agree with above replies. Just to add, I would like to mention that on an interface you can apply one ACL per direction. Also please keep in mind mMore the number of ACLs more the packet processing done at each ifc in ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vijaya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jan 2010 05:52:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402807#M723989</guid>
      <dc:creator>vilaxmi</dc:creator>
      <dc:date>2010-01-21T05:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Access-group</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402808#M723990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For
ASA, is there any standard or a need of having a in and out
access-group for each inside or outside interface, or is it base on
situation and requirement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lawrence&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Hi Lawrence,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Genrally it depends on the situation as good practices we used to do &lt;STRONG&gt;inbound acl&lt;/STRONG&gt; with traffic flow coming inside to device in &lt;STRONG&gt;in&lt;/STRONG&gt; direction.&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;Regards&lt;/P&gt;&lt;P&gt;Ganesh.H&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jan 2010 10:40:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group/m-p/1402808#M723990</guid>
      <dc:creator>Ganesh Hariharan</dc:creator>
      <dc:date>2010-01-21T10:40:18Z</dc:date>
    </item>
  </channel>
</rss>

