<?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 ACL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dmz-acl/m-p/1336915#M827012</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can use the masks. You can also group the networks together using an object group to make it even cleaner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group network BLOCK_RFC_1918&lt;/P&gt;&lt;P&gt; network-object 10.0.0.0 255.0.0.0&lt;/P&gt;&lt;P&gt; network-object 192.168.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt; network-object 172.16.0.0 255.240.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DMZ extended deny ip any object-group BLOCK_RFC_1918&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>Tue, 08 Sep 2009 19:48:48 GMT</pubDate>
    <dc:creator>Collin Clark</dc:creator>
    <dc:date>2009-09-08T19:48:48Z</dc:date>
    <item>
      <title>DMZ ACL</title>
      <link>https://community.cisco.com/t5/network-security/dmz-acl/m-p/1336914#M826995</link>
      <description>&lt;P&gt;Setting up a new DMZ on my ASA 5520 running 7.2(3). I want to allow by exception into the internal network, but allow everything out to the external network. I'm only using private addresses on the internal network. If I simply have a few permit statements in the acl, followed by deny to 10./8, 172.16/12, 192.168./16, that should cover all of the internal networks that I'm using (subnetted 172.16. &amp;amp; 10. networks), right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At first I was trying to do a deny statement for each internal network, but that's going to be a pain to implement and maintain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:13:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-acl/m-p/1336914#M826995</guid>
      <dc:creator>jcw009</dc:creator>
      <dc:date>2019-03-11T16:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: DMZ ACL</title>
      <link>https://community.cisco.com/t5/network-security/dmz-acl/m-p/1336915#M827012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can use the masks. You can also group the networks together using an object group to make it even cleaner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group network BLOCK_RFC_1918&lt;/P&gt;&lt;P&gt; network-object 10.0.0.0 255.0.0.0&lt;/P&gt;&lt;P&gt; network-object 192.168.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt; network-object 172.16.0.0 255.240.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DMZ extended deny ip any object-group BLOCK_RFC_1918&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>Tue, 08 Sep 2009 19:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-acl/m-p/1336915#M827012</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-09-08T19:48:48Z</dc:date>
    </item>
  </channel>
</rss>

