<?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 Firewall policy in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956161#M5063</link>
    <description>&lt;P&gt;I am trying to have an external user (outside the perimeter of my network) that needs to access a server in the data center. Would I need to create 2 policies for this? One fw policy when it comes into the border firewall and another at the data center firewall? Say for example they needed http and https access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any help!!&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:40:58 GMT</pubDate>
    <dc:creator>CiscoIPMAN</dc:creator>
    <dc:date>2020-02-21T17:40:58Z</dc:date>
    <item>
      <title>Firewall policy</title>
      <link>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956161#M5063</link>
      <description>&lt;P&gt;I am trying to have an external user (outside the perimeter of my network) that needs to access a server in the data center. Would I need to create 2 policies for this? One fw policy when it comes into the border firewall and another at the data center firewall? Say for example they needed http and https access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any help!!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:40:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956161#M5063</guid>
      <dc:creator>CiscoIPMAN</dc:creator>
      <dc:date>2020-02-21T17:40:58Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall policy</title>
      <link>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956179#M5065</link>
      <description>&lt;P&gt;here is the example guide - i am in impression both are ASA FW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this is the guide for external FW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/118996-config-asa-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/118996-config-asa-00.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Internal DC FW you do not require NAT. Hopefull in the normal environment Internal LAN IP address allowed to use DC HTTP / HTTPS port ( i am guessing you do not need any rules)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once you made changes external FW NAT and ACL allow incoming for the request, if working good, if not you need to have allowed ACL in the DC FW for the IP you doing NAT. (if you have different IP address range for DC application servers).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Nov 2019 20:25:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956179#M5065</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-11-09T20:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall policy</title>
      <link>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956371#M5066</link>
      <description>&lt;P&gt;I would rethink about your access-strategy. If it is an unknown external user, then terminate the session in a DMZ at a reverse proxy. If it is a known user that is somehow related to your company, let him VPN into your environment. In both cases you don't need to open your data-centre to the outside world.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 17:19:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-policy/m-p/3956371#M5066</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2019-11-10T17:19:53Z</dc:date>
    </item>
  </channel>
</rss>

