<?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 Tricky ACL issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910281#M458773</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I understannd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server---------ASA-------------Internet-------------------user&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have NAT-control enabled on the ASA it needs a NAT configured for the inside server to be accessible from outside.&lt;/P&gt;&lt;P&gt;if the private ip is 1.1.1.1 and public ip is 10.10.10.10 and you have the following configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;statis (inside,outside) 10.10.10.10 1.1.1.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;access-list outside permit ip any host 10.10.10.10&lt;/P&gt;&lt;P&gt;access-group outside in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the above configuration users can access the server only on the public ip address on outside and will not be able to access the private ip address at all. This is the default behavior of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not need any other outbound ACL on the outside interface &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Mar 2012 08:26:42 GMT</pubDate>
    <dc:creator>svaish</dc:creator>
    <dc:date>2012-03-07T08:26:42Z</dc:date>
    <item>
      <title>Tricky ACL issue</title>
      <link>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910280#M458772</link>
      <description>&lt;P&gt;Hi Guys, &lt;/P&gt;&lt;P&gt;facing an issue here and need some expert knowhow....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have several interfaces on my ASA&amp;nbsp; that is also connected with S2S&amp;nbsp; to the HQ office...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have 3 /24 subnets heavily subneted inbetween interfaces and have a collapsed core as well so anything other than playing with ACLs is out of the question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so&amp;nbsp; subnet in question&amp;nbsp; attached to one of ASAs interfaces (nameif:public_NAT) and has&amp;nbsp; a 10.y.x.z/29&amp;nbsp; address&amp;nbsp; (private)&amp;nbsp; i have 3 servers on it.&amp;nbsp; I use static 1-1 NAT&amp;nbsp; to each server from the&amp;nbsp; external range that i have with my ISP (cant route it in as ISP is being ...@#$@D#F).&lt;/P&gt;&lt;P&gt;now the requirement i have is to allow&amp;nbsp; access to all 3 servers but only by using their external globally routed NATs. and block any access to their private IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;question is:&amp;nbsp; can i use&amp;nbsp; an "outbound" ACL&amp;nbsp; on the&amp;nbsp; public_NAT&amp;nbsp; interface&amp;nbsp; saying - deny ip&amp;nbsp; any&amp;nbsp; to private ip addresses of the servers inside that subnet.&lt;/P&gt;&lt;P&gt;and then allow&amp;nbsp; on other interfaces to the external IPs residing on the WAN interface of the firewall ?&lt;/P&gt;&lt;P&gt;also&amp;nbsp; with S2S if that&amp;nbsp; subnet is a part of larger encryption domain&amp;nbsp; is my only choice will be to remove that /29 subnet from the encr. domain ACL ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:35:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910280#M458772</guid>
      <dc:creator>Leon Khanan</dc:creator>
      <dc:date>2019-03-11T22:35:41Z</dc:date>
    </item>
    <item>
      <title>Tricky ACL issue</title>
      <link>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910281#M458773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I understannd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server---------ASA-------------Internet-------------------user&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have NAT-control enabled on the ASA it needs a NAT configured for the inside server to be accessible from outside.&lt;/P&gt;&lt;P&gt;if the private ip is 1.1.1.1 and public ip is 10.10.10.10 and you have the following configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;statis (inside,outside) 10.10.10.10 1.1.1.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;access-list outside permit ip any host 10.10.10.10&lt;/P&gt;&lt;P&gt;access-group outside in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the above configuration users can access the server only on the public ip address on outside and will not be able to access the private ip address at all. This is the default behavior of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not need any other outbound ACL on the outside interface &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2012 08:26:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910281#M458773</guid>
      <dc:creator>svaish</dc:creator>
      <dc:date>2012-03-07T08:26:42Z</dc:date>
    </item>
    <item>
      <title>Tricky ACL issue</title>
      <link>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910282#M458777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hmm i thought on new ASAs above 8.3 NAT comes first... and if so then the ACL on the outside wont see the external IP...&lt;/P&gt;&lt;P&gt;also how will that make my LAN users use the external IP addresses and not just intervlan ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2012 15:32:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tricky-acl-issue/m-p/1910282#M458777</guid>
      <dc:creator>Leon Khanan</dc:creator>
      <dc:date>2012-03-07T15:32:53Z</dc:date>
    </item>
  </channel>
</rss>

