<?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 Zone Based Policy in PANOS SD-WAN (not PRISMA) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/zone-based-policy-in-panos-sd-wan-not-prisma/m-p/482762#M104312</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;In PANOS SD-WAN (not PRISMA), you must either use predefined zones (zone-to-branch, zone-to-hub, etc.), or you can map pre-existing zones to the predefined zones in Panorama.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before SD-WAN, using IPSEC tunnels, we could give each tunnel/branch its own zone and control access very easily.&amp;nbsp; Since SD-WAN requires use of predefined zones, it seems line zone-based policy is mostly useless when differentiating between sites, because from the hub's perspective in a hub/spoke topology, every spoke is in the zone-to-branch zone.&amp;nbsp; I could create all of my policies using address objects and apply them via subnet, but it seems weird that normally PA NGFWs are heavily zone-based, and implementing SD-WAN seems to remove zones from the equation almost fully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I missing something here?&lt;/P&gt;</description>
    <pubDate>Tue, 26 Apr 2022 20:37:35 GMT</pubDate>
    <dc:creator>JayGee</dc:creator>
    <dc:date>2022-04-26T20:37:35Z</dc:date>
    <item>
      <title>Zone Based Policy in PANOS SD-WAN (not PRISMA)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zone-based-policy-in-panos-sd-wan-not-prisma/m-p/482762#M104312</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;In PANOS SD-WAN (not PRISMA), you must either use predefined zones (zone-to-branch, zone-to-hub, etc.), or you can map pre-existing zones to the predefined zones in Panorama.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before SD-WAN, using IPSEC tunnels, we could give each tunnel/branch its own zone and control access very easily.&amp;nbsp; Since SD-WAN requires use of predefined zones, it seems line zone-based policy is mostly useless when differentiating between sites, because from the hub's perspective in a hub/spoke topology, every spoke is in the zone-to-branch zone.&amp;nbsp; I could create all of my policies using address objects and apply them via subnet, but it seems weird that normally PA NGFWs are heavily zone-based, and implementing SD-WAN seems to remove zones from the equation almost fully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I missing something here?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 20:37:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zone-based-policy-in-panos-sd-wan-not-prisma/m-p/482762#M104312</guid>
      <dc:creator>JayGee</dc:creator>
      <dc:date>2022-04-26T20:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Based Policy in PANOS SD-WAN (not PRISMA)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zone-based-policy-in-panos-sd-wan-not-prisma/m-p/482940#M104314</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/181180"&gt;@JayGee&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;At least from my understanding, you aren't missing anything. The feature, at least when I was looking into it, really seemed designed around branch offices that fit a cookie-cutter deployment. As an example, if you were a retail establishment and just had stores connecting to your datacenter. When you don't fit that model, the setup didn't really meet our needs for that.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 22:35:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zone-based-policy-in-panos-sd-wan-not-prisma/m-p/482940#M104314</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2022-04-26T22:35:05Z</dc:date>
    </item>
  </channel>
</rss>

