<?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 Cisco ASA Public Servers in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659064#M560542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The purpose of the "Public Servers" feature is:&lt;/P&gt;&lt;P&gt;- A single point of configuration to configure: static NAT, access-list, and applying it to the correct interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not have to separately configure static NAT, then the firewall rules for any inbound traffic like previously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's introduced to provide the firewall admin a convenient way of configuring inbound access which before needs to be configured separately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Jun 2011 05:43:54 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2011-06-17T05:43:54Z</dc:date>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659063#M560541</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have question about purpose of this one feature:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa83/asdm63/configuration_guide/public_servers.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa83/asdm63/configuration_guide/public_servers.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the difference between, this page and following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I make static NAT, and then on outside interface inbound ACL I allow requested ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this one, is some kind of summary, I wonder why there is only something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case I have about 20 static NATs with allowed ports and this page show slightly half of them (yes all, of them have at least one port exposed to the world).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, please give me some reasonable explanation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:46:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659063#M560541</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2019-03-11T20:46:09Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659064#M560542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The purpose of the "Public Servers" feature is:&lt;/P&gt;&lt;P&gt;- A single point of configuration to configure: static NAT, access-list, and applying it to the correct interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not have to separately configure static NAT, then the firewall rules for any inbound traffic like previously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's introduced to provide the firewall admin a convenient way of configuring inbound access which before needs to be configured separately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 05:43:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659064#M560542</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-06-17T05:43:54Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659065#M560543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All right, I was guessing about this purpose.&lt;/P&gt;&lt;P&gt;But there is second part of my question:&lt;/P&gt;&lt;P&gt;- why is there only part of configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember, I have never configured anything through this menu, so it must be some kind of import. But import which is useless :-((.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 07:38:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659065#M560543</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2011-06-17T07:38:58Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659066#M560544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah, I agree with you (the import is kind of useless if you have configured it the other way round).&lt;/P&gt;&lt;P&gt;It is more useful for admin who is not used to the old method and configuring the access via the "Public Servers" way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 08:03:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659066#M560544</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-06-17T08:03:31Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659067#M560545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What makes mi confused, is that there is something.&lt;/P&gt;&lt;P&gt;I have never configured anything that way.&lt;/P&gt;&lt;P&gt;So, where it goes from?&lt;/P&gt;&lt;P&gt;And why there are all pieces of config?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;:-(((&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 08:28:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659067#M560545</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2011-06-17T08:28:23Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA Public Servers</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659068#M560546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And why there are not all pieces of config?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 08:28:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-public-servers/m-p/1659068#M560546</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2011-06-17T08:28:44Z</dc:date>
    </item>
  </channel>
</rss>

