<?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 - DMZ access outside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090944#M395468</link>
    <description>&lt;P&gt;Hi I need some help here I have an ASA 5505 with the security bundle, latest ASA software 9.0(1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 3 DMZs. I initially allowed them access to the internet using e.g.:&lt;/P&gt;&lt;P&gt;object network obj_dmz1 &lt;/P&gt;&lt;P&gt;subnet 192.168.1.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;nat (dmz1,outside) dynamic interface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was fine, except when I then created a rule to allow the DMZ to the internal network on one IP and port, they could no longer access the outside network at all. &lt;/P&gt;&lt;P&gt;I can add an access rule to allow access to any, but that is hardly what I want - that gives full access to the internal network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I presume the issue is because the implicit rule allowing any to a less secure network no longer applies now that I have created a NAT rule. So, how can I allow the hosts in the DMZ to access the internet again?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks ﻿ ﻿ ﻿ ﻿&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 00:24:38 GMT</pubDate>
    <dc:creator>Hal Sclater</dc:creator>
    <dc:date>2019-03-12T00:24:38Z</dc:date>
    <item>
      <title>Cisco ASA - DMZ access outside</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090944#M395468</link>
      <description>&lt;P&gt;Hi I need some help here I have an ASA 5505 with the security bundle, latest ASA software 9.0(1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 3 DMZs. I initially allowed them access to the internet using e.g.:&lt;/P&gt;&lt;P&gt;object network obj_dmz1 &lt;/P&gt;&lt;P&gt;subnet 192.168.1.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;nat (dmz1,outside) dynamic interface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was fine, except when I then created a rule to allow the DMZ to the internal network on one IP and port, they could no longer access the outside network at all. &lt;/P&gt;&lt;P&gt;I can add an access rule to allow access to any, but that is hardly what I want - that gives full access to the internal network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I presume the issue is because the implicit rule allowing any to a less secure network no longer applies now that I have created a NAT rule. So, how can I allow the hosts in the DMZ to access the internet again?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks ﻿ ﻿ ﻿ ﻿&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:24:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090944#M395468</guid>
      <dc:creator>Hal Sclater</dc:creator>
      <dc:date>2019-03-12T00:24:38Z</dc:date>
    </item>
    <item>
      <title>Cisco ASA - DMZ access outside</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090945#M395469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Before the "permit any" you mentioned, add a "Deny all RFC 1918" (after the permit you already mentioned).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karsten I. has a nice post &lt;A _jive_internal="true" href="https://community.cisco.com/message/3737141#3737141"&gt;here&lt;/A&gt; that explains this approach in more detail.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2012 04:43:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090945#M395469</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-11-17T04:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA - DMZ access outside</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090946#M395470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, that is exactly what I needed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I eneded up with this, which lets the DMZHOST get to anywhere apart from the internal subnets:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;P&gt;access-list dmz2_access_in extended permit tcp object DMZHOST object MAILSERVER eq smtp &lt;/P&gt;&lt;P&gt;access-list dmz2_access_in extended deny ip any object-group RFC1918 &lt;/P&gt;&lt;P&gt;access-list dmz2_access_in extended permit ip object DMZHOST object obj_any &lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;P&gt;Works a treat, now the DMZHOST can access the Mailserver but nothing else internally, and go wherever it wants outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2012 11:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-dmz-access-outside/m-p/2090946#M395470</guid>
      <dc:creator>Hal Sclater</dc:creator>
      <dc:date>2012-11-17T11:18:10Z</dc:date>
    </item>
  </channel>
</rss>

