<?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 Remote site management to be managed with Panorama? in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/remote-site-management-to-be-managed-with-panorama/m-p/551879#M1680</link>
    <description>&lt;P&gt;I'm looking at deploying some PAN-440 firewalls and wanted to get some advice as this is one of the first remote sites I've done with Palo.&amp;nbsp; My intention was to build an IPSEC bridge between the remote site and our on-prem firewalls in order to pipe all of the remote site's traffic to us.&amp;nbsp; That would allow us to control internet access and use our on-prem subscriptions for cybersecurity as well as enable the remote site to access our wireless controller, VoIP system, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at deployment options, it seems like ZTP might be good for this so I'm reading up on that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My question: I'm assuming the management that ZTP sets up would NOT go across the IPSEC tunnel and that it would be best practice to leave it that way?&amp;nbsp; Theoretically, if we create firewall policy that only allows the static IPs on each side to communicate with each other then this would allow troubleshooting if the tunnel fails for some reason.&amp;nbsp; I must admit that I'm a little hesitant to create an inbound NAT and security policy pointing to Panorama for security but, again, this could be mitigated by only allowing the remote static IP and it appears to be necessary for ZTP setup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 21:16:32 GMT</pubDate>
    <dc:creator>jsalmans</dc:creator>
    <dc:date>2023-07-31T21:16:32Z</dc:date>
    <item>
      <title>Remote site management to be managed with Panorama?</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/remote-site-management-to-be-managed-with-panorama/m-p/551879#M1680</link>
      <description>&lt;P&gt;I'm looking at deploying some PAN-440 firewalls and wanted to get some advice as this is one of the first remote sites I've done with Palo.&amp;nbsp; My intention was to build an IPSEC bridge between the remote site and our on-prem firewalls in order to pipe all of the remote site's traffic to us.&amp;nbsp; That would allow us to control internet access and use our on-prem subscriptions for cybersecurity as well as enable the remote site to access our wireless controller, VoIP system, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at deployment options, it seems like ZTP might be good for this so I'm reading up on that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My question: I'm assuming the management that ZTP sets up would NOT go across the IPSEC tunnel and that it would be best practice to leave it that way?&amp;nbsp; Theoretically, if we create firewall policy that only allows the static IPs on each side to communicate with each other then this would allow troubleshooting if the tunnel fails for some reason.&amp;nbsp; I must admit that I'm a little hesitant to create an inbound NAT and security policy pointing to Panorama for security but, again, this could be mitigated by only allowing the remote static IP and it appears to be necessary for ZTP setup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 21:16:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/remote-site-management-to-be-managed-with-panorama/m-p/551879#M1680</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2023-07-31T21:16:32Z</dc:date>
    </item>
  </channel>
</rss>

