<?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 Static NAT / ACL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-nat-acl/m-p/2743212#M178389</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have some static NATs configured with relevant ACL "Inbound" on the Outside Interface.&lt;/P&gt;&lt;P&gt;Simple Setup - I have inside and outside interface.&lt;/P&gt;&lt;P&gt;If someone from Outside initiates a connection to one of my servers on a Static NAT. Will the return traffic from the server be allowed back out If I have an ACL Inbound on the Inside Interface that potentially blocks the return traffic? Or is a state table checked first before the ACL to see if this is a known already established connections and then allow the traffic (ignoring my ACL on inside interface).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 06:40:09 GMT</pubDate>
    <dc:creator>GRANT3779</dc:creator>
    <dc:date>2019-03-12T06:40:09Z</dc:date>
    <item>
      <title>Static NAT / ACL</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-acl/m-p/2743212#M178389</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have some static NATs configured with relevant ACL "Inbound" on the Outside Interface.&lt;/P&gt;&lt;P&gt;Simple Setup - I have inside and outside interface.&lt;/P&gt;&lt;P&gt;If someone from Outside initiates a connection to one of my servers on a Static NAT. Will the return traffic from the server be allowed back out If I have an ACL Inbound on the Inside Interface that potentially blocks the return traffic? Or is a state table checked first before the ACL to see if this is a known already established connections and then allow the traffic (ignoring my ACL on inside interface).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:40:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-acl/m-p/2743212#M178389</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-03-12T06:40:09Z</dc:date>
    </item>
    <item>
      <title>Hi,The ASA checks the ACL</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-acl/m-p/2743213#M178390</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The ASA checks the ACL while creating the session and return traffic matches existing session and gets processed.&lt;/P&gt;&lt;P&gt;Hence the execution will occur in following manner: Evaluate ACL on ingress interface in inward direction &amp;gt;&amp;gt; ACL on the egress interface in outward direction (if this is present).&lt;/P&gt;&lt;P&gt;Return traffic for the same session will match the session and will get processed accordingly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps!!!&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;R.Seth&lt;/P&gt;&lt;P&gt;Mark the answer as correct if it helps in resolving your query!!!&lt;/P&gt;&lt;P&gt;!!!&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;R.Seth&lt;/P&gt;&lt;P&gt;Don't forget to mark the answer as correct if it helps in resolving your query!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2015 09:48:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-acl/m-p/2743213#M178390</guid>
      <dc:creator>Rishabh Seth</dc:creator>
      <dc:date>2015-09-30T09:48:12Z</dc:date>
    </item>
  </channel>
</rss>

