<?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 Angelo, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040035#M146307</link>
    <description>&lt;P&gt;Angelo,&lt;/P&gt;
&lt;P&gt;Assuming that with "reserve nat" you're referring to the NAT control feature then that's correct, the use of this feature was deprecated since the introduction of code 8.3.&lt;/P&gt;
&lt;P&gt;The best practice for traffic access control is the use of security levels and access-lists.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Pablo&lt;/P&gt;</description>
    <pubDate>Thu, 23 Feb 2017 02:22:43 GMT</pubDate>
    <dc:creator>Pablo</dc:creator>
    <dc:date>2017-02-23T02:22:43Z</dc:date>
    <item>
      <title>ASA reverse nat</title>
      <link>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040034#M146305</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Iìd like to understand if applying reverse nat on ASA firewall is a good practice or is deprecated due ASA's security logic of inside and outside inteface concept.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you in advance for any kind reply.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;angelo&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:58:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040034#M146305</guid>
      <dc:creator>ANGELO DE MASI</dc:creator>
      <dc:date>2019-03-12T08:58:13Z</dc:date>
    </item>
    <item>
      <title>Angelo,</title>
      <link>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040035#M146307</link>
      <description>&lt;P&gt;Angelo,&lt;/P&gt;
&lt;P&gt;Assuming that with "reserve nat" you're referring to the NAT control feature then that's correct, the use of this feature was deprecated since the introduction of code 8.3.&lt;/P&gt;
&lt;P&gt;The best practice for traffic access control is the use of security levels and access-lists.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Pablo&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 02:22:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040035#M146307</guid>
      <dc:creator>Pablo</dc:creator>
      <dc:date>2017-02-23T02:22:43Z</dc:date>
    </item>
    <item>
      <title>Hi pablo, i am referring to</title>
      <link>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040036#M146309</link>
      <description>&lt;P&gt;Hi pablo, i am referring to configuration of ASA pre-8.3 with nat-control enabled and with reverse nat i mean the configuration of natting from outside to inside which is in my mind in contraddiction respect normal ASA behaviour. is that also depreated or it is an accepted configuration as natting from inside to outside?&lt;/P&gt;
&lt;P&gt;Thank you for your reply&lt;/P&gt;
&lt;P&gt;Angelo&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 05:33:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-reverse-nat/m-p/3040036#M146309</guid>
      <dc:creator>ANGELO DE MASI</dc:creator>
      <dc:date>2017-02-23T05:33:49Z</dc:date>
    </item>
  </channel>
</rss>

