<?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 Firewalling: Best Practise? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewalling-best-practise/m-p/1857255#M456254</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dmitry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That depends on you, you can disable nat control and use the public ip addresses, I would rather to use nat as it adds a little bit of security to your network as the outside users will not know witch is the private ip address of each internal server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will be able to accomplish all you are looking for, seems like the ASA is the firewall device that will implement all your needs on the best way!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Jan 2012 17:31:48 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-01-24T17:31:48Z</dc:date>
    <item>
      <title>Firewalling: Best Practise?</title>
      <link>https://community.cisco.com/t5/network-security/firewalling-best-practise/m-p/1857254#M456253</link>
      <description>&lt;P&gt;We have purchased a Cisco ASA 5505 to protect the servers behind it and I have a question on how to go about it. This is what we have:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- 5 servers with dedicated public IPs and some have more than one (web hosting)&lt;/P&gt;&lt;P&gt;- 2 switches, one for public network and one for internal netowkr (for backing up and faster access between the servers)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we want to achieve:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Place all the servers behind the firewall so we can control ports per server&lt;/P&gt;&lt;P&gt;- Have a site-to-site VPN so we can access the UC560 that is hosted at this site for our telephones at this office (already working)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestions/recommendations? Should be still have an private IP addressing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Dmitry&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:18:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewalling-best-practise/m-p/1857254#M456253</guid>
      <dc:creator>Dmitry Golovenkin</dc:creator>
      <dc:date>2019-03-11T22:18:47Z</dc:date>
    </item>
    <item>
      <title>Firewalling: Best Practise?</title>
      <link>https://community.cisco.com/t5/network-security/firewalling-best-practise/m-p/1857255#M456254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dmitry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That depends on you, you can disable nat control and use the public ip addresses, I would rather to use nat as it adds a little bit of security to your network as the outside users will not know witch is the private ip address of each internal server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will be able to accomplish all you are looking for, seems like the ASA is the firewall device that will implement all your needs on the best way!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jan 2012 17:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewalling-best-practise/m-p/1857255#M456254</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-01-24T17:31:48Z</dc:date>
    </item>
  </channel>
</rss>

