<?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 So your rule basically means in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078018#M147117</link>
    <description>&lt;P&gt;So your rule basically means that if the DMZ interface sees any packet INBOUND with source as DMZ-network and destination as 'any', it will allow it to hit the ASA. This allows the DMZ-network to send traffic to any destination (internet). This is correct. Setting the destination to 'Outside' interface says that the DMZ-network is allowed to talk to the outside interface.&lt;/P&gt;
&lt;P&gt;If you want to block access from 'Internet' to 'DMZ', this is done by default as the ASA does not allow traffic from a lower to higher security level without adding an ACL specifically.&lt;/P&gt;</description>
    <pubDate>Tue, 31 Jan 2017 13:30:59 GMT</pubDate>
    <dc:creator>Rahul Govindan</dc:creator>
    <dc:date>2017-01-31T13:30:59Z</dc:date>
    <item>
      <title>Cisco ASA firewall policy from DMZ to Outside interface not working</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078017#M147116</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I'm new to ASA firewall's and would appreciate if someone can point me in the right direction with a firewall rule.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I've configured a firewall policy to allow the DMZ network access to the internet.&lt;/P&gt;
&lt;P&gt;However, I can only get this policy to permit traffic destined to the internet from a host in the DMZ if I set the Destination to 'any' in the rules. It does not work when I change the&amp;nbsp;&lt;SPAN&gt;Destination to 'Outbound' interface,&amp;nbsp;and I don't understand why it won't work.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please see attachment.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I don't want to leave the&amp;nbsp;&lt;SPAN&gt;Destination to 'any' because I only want the DMZ network to access the internet, hence I want to set the&amp;nbsp;Destination to 'Outbound' interface somehow, or look for a work around.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Note: Disregard rule 1&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:51:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078017#M147116</guid>
      <dc:creator>Roger De Couto</dc:creator>
      <dc:date>2019-03-12T08:51:30Z</dc:date>
    </item>
    <item>
      <title>So your rule basically means</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078018#M147117</link>
      <description>&lt;P&gt;So your rule basically means that if the DMZ interface sees any packet INBOUND with source as DMZ-network and destination as 'any', it will allow it to hit the ASA. This allows the DMZ-network to send traffic to any destination (internet). This is correct. Setting the destination to 'Outside' interface says that the DMZ-network is allowed to talk to the outside interface.&lt;/P&gt;
&lt;P&gt;If you want to block access from 'Internet' to 'DMZ', this is done by default as the ASA does not allow traffic from a lower to higher security level without adding an ACL specifically.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 13:30:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078018#M147117</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2017-01-31T13:30:59Z</dc:date>
    </item>
    <item>
      <title>I think you might be</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078019#M147118</link>
      <description>&lt;P&gt;I think you might be confusing access-list rules with NAT rules. &amp;nbsp;The access rule spesifies which source IP the ASA should expect to see on the interface the the ACL is assigned to, while destination specifies which IP that source address is allowed to talk to, and the then again the port is which port the source is allowed to talk to the destination on. &amp;nbsp;So setting the destination in the ACL rule to Any is a requirement to allow for internet access.&lt;/P&gt;
&lt;P&gt;In the NAT rule you can specify that a given subnet or IP will be translated to the outside interface IP so to hide the real IP behind the ASA. &amp;nbsp;Depending on how you have configured your ASA, traffic will by default be denied on the outside interface unless explicitly permitted.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 18:12:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-policy-from-dmz-to-outside-interface-not/m-p/3078019#M147118</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2017-01-31T18:12:36Z</dc:date>
    </item>
  </channel>
</rss>

