<?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 Re: dmz design in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dmz-design/m-p/961057#M939289</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;#Allow outside to hit dmz server&lt;/P&gt;&lt;P&gt;static (srv,outside) MRI-Portal MRI-SRV netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;#Allow communication between inside and srv network&lt;/P&gt;&lt;P&gt;static (inside,srv) 172.18.1.0 172.18.1.0 netmask 255.255.224.0&lt;/P&gt;&lt;P&gt;#ACL for dmz interface&lt;/P&gt;&lt;P&gt;access-list dmz extended permit tcp host 10.10.2.x host &lt;INSIDE.HOST&gt; eq xxx&lt;/INSIDE.HOST&gt;&lt;/P&gt;&lt;P&gt;#Add additional permit statements here&lt;/P&gt;&lt;P&gt;#Now deny everything else to inside&lt;/P&gt;&lt;P&gt;access-list dmz extended deny ip any 172.18.1.0 255.255.224.0&lt;/P&gt;&lt;P&gt;#Now allow all other traffic outbound to internet from srv&lt;/P&gt;&lt;P&gt;access-list dmz extended permit ip any any&lt;/P&gt;&lt;P&gt;access-group dmz in interface srv&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Apr 2008 14:14:23 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2008-04-15T14:14:23Z</dc:date>
    <item>
      <title>dmz design</title>
      <link>https://community.cisco.com/t5/network-security/dmz-design/m-p/961056#M939287</link>
      <description>&lt;P&gt;here is my dilemma, we have a dmz setup on an asa5520 where we are going to have a public web server that needs to access a backend sql database on the internal network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to allow the server in the dmz to initiate with the internet as well as be accessible from the internet, and to be able to initiate with a few servers on the inside for backup processes.  I also want to be able to manage dmz servers from the inside, restricted to a few specific ip addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know how to create acls in the dmz to allow access back to the internal network, however when i do this i am unable to then connect to the internet from the webserver in the dmz.  right now i have taken out the specific acls and added one blanket acl to allow ip any any.  However this gives me complete access to the internal network, but it also gives me internet access?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is what kind of acls do i need to write to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. allow servers in the dmz to access the internet with its range of ip addresses. Some sort of Nat Statement?&lt;/P&gt;&lt;P&gt;2. allow servers in dmz to access specific internal servers&lt;/P&gt;&lt;P&gt;3. manage web servers in dmz from internal network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have taken out the static nat statement allowing the public ip of the web server in the dmz to be translated to the private ip. static (srv,outside) MRI-Portal MRI-SRV netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:31:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-design/m-p/961056#M939287</guid>
      <dc:creator>greg.blumberg</dc:creator>
      <dc:date>2019-03-11T12:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: dmz design</title>
      <link>https://community.cisco.com/t5/network-security/dmz-design/m-p/961057#M939289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;#Allow outside to hit dmz server&lt;/P&gt;&lt;P&gt;static (srv,outside) MRI-Portal MRI-SRV netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;#Allow communication between inside and srv network&lt;/P&gt;&lt;P&gt;static (inside,srv) 172.18.1.0 172.18.1.0 netmask 255.255.224.0&lt;/P&gt;&lt;P&gt;#ACL for dmz interface&lt;/P&gt;&lt;P&gt;access-list dmz extended permit tcp host 10.10.2.x host &lt;INSIDE.HOST&gt; eq xxx&lt;/INSIDE.HOST&gt;&lt;/P&gt;&lt;P&gt;#Add additional permit statements here&lt;/P&gt;&lt;P&gt;#Now deny everything else to inside&lt;/P&gt;&lt;P&gt;access-list dmz extended deny ip any 172.18.1.0 255.255.224.0&lt;/P&gt;&lt;P&gt;#Now allow all other traffic outbound to internet from srv&lt;/P&gt;&lt;P&gt;access-list dmz extended permit ip any any&lt;/P&gt;&lt;P&gt;access-group dmz in interface srv&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Apr 2008 14:14:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-design/m-p/961057#M939289</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-04-15T14:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: dmz design</title>
      <link>https://community.cisco.com/t5/network-security/dmz-design/m-p/961058#M939290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks, this did the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Apr 2008 17:12:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-design/m-p/961058#M939290</guid>
      <dc:creator>greg.blumberg</dc:creator>
      <dc:date>2008-04-15T17:12:39Z</dc:date>
    </item>
  </channel>
</rss>

