<?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: If the PAN's in HA are perimeter FW's and IPS's how do you configure for Internal IPS Monitoring? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/if-the-pan-s-in-ha-are-perimeter-fw-s-and-ips-s-how-do-you/m-p/3174#M2369</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Personally I would suggest to use one set of hardware as outer firewalls/protection and another set of hardware as inner firewalls/protection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simply because if you get a DDoS on the outer firewalls the DMZ's connect there will basically go offline and with another hardware set as internal firewalls your internal network will continue to work even if the external firewalls are flooded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will also take in account regarding misconfigurations or for that matter hardware failure all together (where HA doesnt help).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But given that you cant afford to get a dedicated HA pair as internal firewalls a workaround can be to setup a different VSYS on your already existing set of PA HA pair.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is VSYS1 is ExternalFW and VSYS2 is InternalFW. This will also make life easier the day you can afford a dedicated set of internal firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now back to the VSYS... how you setup VSYS2 is up to you - simpliest way is to make it VWIRE and connect this between your internal router and the switch(es) your servers are connected to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is also how an IPS usually is setup as.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if you want to make it an internal firewall (and not just IPS) I would configure it with L3-interfaces so you get a design such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internet&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;ExternalFW - Internet-DMZ&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;Router - Clients&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;InternalFW&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;Server-DMZ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Mar 2013 23:08:29 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2013-03-29T23:08:29Z</dc:date>
    <item>
      <title>If the PAN's in HA are perimeter FW's and IPS's how do you configure for Internal IPS Monitoring?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/if-the-pan-s-in-ha-are-perimeter-fw-s-and-ips-s-how-do-you/m-p/3173#M2368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the PAN's in HA are perimeter FW's and IPS's how do you configure for Internal IPS Monitoring?&lt;/P&gt;&lt;P&gt;We'd like to be able to see internal IPS threats to our server farms sourced from workstations on the LAN's.&lt;/P&gt;&lt;P&gt;Is this scenario achievable with two HA PAN's?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;PotStirrer.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 21:37:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/if-the-pan-s-in-ha-are-perimeter-fw-s-and-ips-s-how-do-you/m-p/3173#M2368</guid>
      <dc:creator>PotStirrer</dc:creator>
      <dc:date>2013-03-29T21:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: If the PAN's in HA are perimeter FW's and IPS's how do you configure for Internal IPS Monitoring?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/if-the-pan-s-in-ha-are-perimeter-fw-s-and-ips-s-how-do-you/m-p/3174#M2369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Personally I would suggest to use one set of hardware as outer firewalls/protection and another set of hardware as inner firewalls/protection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simply because if you get a DDoS on the outer firewalls the DMZ's connect there will basically go offline and with another hardware set as internal firewalls your internal network will continue to work even if the external firewalls are flooded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will also take in account regarding misconfigurations or for that matter hardware failure all together (where HA doesnt help).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But given that you cant afford to get a dedicated HA pair as internal firewalls a workaround can be to setup a different VSYS on your already existing set of PA HA pair.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is VSYS1 is ExternalFW and VSYS2 is InternalFW. This will also make life easier the day you can afford a dedicated set of internal firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now back to the VSYS... how you setup VSYS2 is up to you - simpliest way is to make it VWIRE and connect this between your internal router and the switch(es) your servers are connected to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is also how an IPS usually is setup as.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if you want to make it an internal firewall (and not just IPS) I would configure it with L3-interfaces so you get a design such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internet&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;ExternalFW - Internet-DMZ&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;Router - Clients&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;InternalFW&lt;/P&gt;&lt;P&gt;|&lt;/P&gt;&lt;P&gt;Server-DMZ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 23:08:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/if-the-pan-s-in-ha-are-perimeter-fw-s-and-ips-s-how-do-you/m-p/3174#M2369</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-03-29T23:08:29Z</dc:date>
    </item>
  </channel>
</rss>

