<?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 I think you are pretty much in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-dmz-best-practices/m-p/2655890#M197367</link>
    <description>&lt;P&gt;I think you are pretty much there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in terms of allowing access from your DMZ to INSIDE, limit it. legitimate traffic could be syslog, snmp to your management server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in terms of proxy. you don't necessarily have to stick ity in your DMZ as the outside would not attempt to connect to it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here is a good read about the concept:http://etherealmind.com/design-enterprise-dmz-firewall-clusters/&lt;/P&gt;</description>
    <pubDate>Wed, 04 Feb 2015 02:53:42 GMT</pubDate>
    <dc:creator>Dennis Mink</dc:creator>
    <dc:date>2015-02-04T02:53:42Z</dc:date>
    <item>
      <title>ASA DMZ best practices</title>
      <link>https://community.cisco.com/t5/network-security/asa-dmz-best-practices/m-p/2655889#M197366</link>
      <description>&lt;P&gt;I am looking for best practices for my DMZ zone on my ASA 5510 to my inside network. I have this currently setup, but would like to know if what I'm doing is best practice. I currently have a proxy server in the DMZ and I am using Nat from my one inside host that needs to access the proxy and not Nat exemption. My thoughts are this hides the internal network address, but is this really necessary? I also allow inside to DMZ, but obviously not DMZ to inside. Should I also only allow the one host and ports from the the inside to DMZ direction? Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:26:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dmz-best-practices/m-p/2655889#M197366</guid>
      <dc:creator>Phil Bradley</dc:creator>
      <dc:date>2019-03-12T05:26:40Z</dc:date>
    </item>
    <item>
      <title>I think you are pretty much</title>
      <link>https://community.cisco.com/t5/network-security/asa-dmz-best-practices/m-p/2655890#M197367</link>
      <description>&lt;P&gt;I think you are pretty much there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in terms of allowing access from your DMZ to INSIDE, limit it. legitimate traffic could be syslog, snmp to your management server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in terms of proxy. you don't necessarily have to stick ity in your DMZ as the outside would not attempt to connect to it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here is a good read about the concept:http://etherealmind.com/design-enterprise-dmz-firewall-clusters/&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2015 02:53:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dmz-best-practices/m-p/2655890#M197367</guid>
      <dc:creator>Dennis Mink</dc:creator>
      <dc:date>2015-02-04T02:53:42Z</dc:date>
    </item>
  </channel>
</rss>

