<?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 Applying ACL on outside interface of ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210442#M347076</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally you allow and/or restrict user traffic in the interface ACL closest to the user. In your case it would be interface X's ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the user attempts the connection to the site, the first thing that will be checked is the interface X ACL if there is one that is attached to the &lt;STRONG&gt;"in"&lt;/STRONG&gt; direction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I would imagine that there is no need to configure a new ACL for this purpose. Just use the existing ACL on the interface X to allow what traffic you need since it will be the first one checked and there isnt really need to do it twice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Jul 2013 21:29:10 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-07-03T21:29:10Z</dc:date>
    <item>
      <title>Applying ACL on outside interface of ASA</title>
      <link>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210440#M347072</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say we have ASA&amp;nbsp; with many interfaces.&lt;/P&gt;&lt;P&gt;Users are on interface x&amp;nbsp; .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface x has ACL&amp;nbsp; that allows access to certain IP address only and it has deny ip any any at the end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now user needs access to some website on specfic port only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i make ACL&amp;nbsp; on outside interface of ASA allowing access to that website on specfic port&amp;nbsp; direction outwards from source any&amp;nbsp; it should work right ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:06:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210440#M347072</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T02:06:46Z</dc:date>
    </item>
    <item>
      <title>Applying ACL on outside interface of ASA</title>
      <link>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210441#M347074</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;It should,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;make sure the Permit statement is before the deny one&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember to rate all of the helpful posts. &lt;BR /&gt; &lt;BR /&gt;For this community that's as important as a thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2013 21:23:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210441#M347074</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-07-03T21:23:19Z</dc:date>
    </item>
    <item>
      <title>Applying ACL on outside interface of ASA</title>
      <link>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210442#M347076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally you allow and/or restrict user traffic in the interface ACL closest to the user. In your case it would be interface X's ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the user attempts the connection to the site, the first thing that will be checked is the interface X ACL if there is one that is attached to the &lt;STRONG&gt;"in"&lt;/STRONG&gt; direction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I would imagine that there is no need to configure a new ACL for this purpose. Just use the existing ACL on the interface X to allow what traffic you need since it will be the first one checked and there isnt really need to do it twice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2013 21:29:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210442#M347076</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-03T21:29:10Z</dc:date>
    </item>
    <item>
      <title>Applying ACL on outside interface of ASA</title>
      <link>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210443#M347077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agreee what you say as extended ACL are applied close to source.&lt;/P&gt;&lt;P&gt;But current design here&amp;nbsp; allows&amp;nbsp; outbound interface&amp;nbsp; as traffic leaves the ASA&amp;nbsp; to allow certain websites .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jul 2013 17:26:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/applying-acl-on-outside-interface-of-asa/m-p/2210443#M347077</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-07-04T17:26:33Z</dc:date>
    </item>
  </channel>
</rss>

