<?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: Panorama managed template config in Cloud NGFW for Azure Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/556747#M14</link>
    <description>&lt;P&gt;Hi Jason,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your findings regarding the template stack naming are 100% accurate. This is how the plugin distinguishes between a VM-series device and a Cloud NGFW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding the management IP address you see in Panorama, this address is not reachable externally and is only used by the service control plane.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for the internal EDLs, are you using an internal FQDN to access them?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Sep 2023 12:59:12 GMT</pubDate>
    <dc:creator>abudilovskiy</dc:creator>
    <dc:date>2023-09-06T12:59:12Z</dc:date>
    <item>
      <title>Panorama managed template config</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/553125#M10</link>
      <description>&lt;P&gt;Does anyone have any information on what configurations are needed in the Template stack associated with the Cloud NGFW?&amp;nbsp; Specifically I am looking for what the interface and vrouter settings will likely need to be, such as ethernet1/1 and 1/2 set to DHCP, vrouter next hop of X, or if we need to allow for the Azure load-balancer probe monitoring like for VM-based deployment.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2023 18:30:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/553125#M10</guid>
      <dc:creator>jasonrakers</dc:creator>
      <dc:date>2023-08-09T18:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama managed template config</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/553300#M11</link>
      <description>&lt;P&gt;I did some testing.&amp;nbsp; The Azure plugin creates a special Cloud NGFW template/template stack (cngfw-az-_DEFAULT_TEMPLATE_).&amp;nbsp; You don't get to use an existing template, or add an existing base template into the special template stack.&amp;nbsp; In the special template, the only network options are security zones which are already pre-defined.&amp;nbsp; Interested to see how creating another Cloud NGFW works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am currently encountering issues with how the Cloud NGFW accesses External Dynamic Lists (internal to the org) and forwarding logs to a Log Collector.&amp;nbsp; It seems to give Panorama a "fake" management IP address, which complicates troubleshooting where management traffic for these services is coming from the Cloud NGFW.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But the policy administration is standard PAN, which is most appreciated, compared to Azure firewall.&amp;nbsp; The Cloud NGFW onboarding also appears to take care of all the dynamic updates being installed as well.&amp;nbsp; Looking forward to validating this solution.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 16:15:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/553300#M11</guid>
      <dc:creator>jasonrakers</dc:creator>
      <dc:date>2023-08-10T16:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama managed template config</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/556747#M14</link>
      <description>&lt;P&gt;Hi Jason,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your findings regarding the template stack naming are 100% accurate. This is how the plugin distinguishes between a VM-series device and a Cloud NGFW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding the management IP address you see in Panorama, this address is not reachable externally and is only used by the service control plane.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for the internal EDLs, are you using an internal FQDN to access them?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 12:59:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/556747#M14</guid>
      <dc:creator>abudilovskiy</dc:creator>
      <dc:date>2023-09-06T12:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama managed template config</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/557236#M15</link>
      <description>&lt;P&gt;internal IP host, no DNS involved, to get to the web server hosting the internal EDL&lt;/P&gt;</description>
      <pubDate>Sun, 10 Sep 2023 00:23:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/panorama-managed-template-config/m-p/557236#M15</guid>
      <dc:creator>jasonrakers</dc:creator>
      <dc:date>2023-09-10T00:23:39Z</dc:date>
    </item>
  </channel>
</rss>

