Use Groups in Network Policy Rules
Focus
Focus
Prisma SD-WAN

Use Groups in Network Policy Rules

Table of Contents

Use Groups in Network Policy Rules

Learn to define service endpoint groups for each group which have one or more Prisma SD-WAN data centers or standard service endpoints.
Where Can I Use This?What Do I Need?
  • Prisma Access CloudBlade (Panorama Managed)
  • Prisma Access CloudBlade (Cloud Managed)
  • Prisma SD-WAN License.
  • Prisma Access for Networks Subscription.
  • Supported Cloud plugin Versions.
  • Prisma Access CloudBlade (Cloud Managed) version 3.x.x and later
  • Prisma Access CloudBlade (Panorama Managed) versions 3.x.x and 4.x.x.
Before you can use a Standard VPN in a policy rule, you need to have defined service endpoint groups. Each group can have one or more Prisma SD-WAN data centers or standard service endpoints. A group will be used in policy rules. The domain that defines the mappings for endpoints to groups must be assigned to a site for the policy rules using the group to be effective. For more information, refer to Managing Services and Data Center Groups. There can be four combinations of Active/Backup groups that can be used in Policies. You can select just one Prisma SD-WAN group or one non-Prisma SD-WAN group as an active or backup path in policies. For example:
Active GroupBackup GroupExample
StandardPrisma SD-WANInternet-bound SSL traffic from a branch site will transit through the Cloud Security Service. In the event all standard VPN paths to any of the endpoints in the Primary Cloud Security Service group are not available, internet-bound SSL traffic will transit through one of the Prisma SD-WAN data center endpoints assigned to that group through the Prisma SD-WAN VPN.
Prisma SD-WANStandardInternet-bound SSL traffic from a branch site will transit through one of the Prisma SD-WAN data center endpoints assigned to that group via the Prisma SD-WAN VPNs. In the event all Prisma SD-WAN VPNs to all of the Data Center endpoints in that group are unavailable, internet-bound SSL traffic will transit through the Cloud Security Service via one of the standard VPN paths to any of the endpoints in the standard group.
StandardStandardInternet-bound SSL traffic from a branch site will transit through the primary cloud security service via one of the standard VPN paths to any of the endpoints in the primary cloud security service group. In the event all standard VPNs are down to all endpoints in the primary group, the Internet bound SSL traffic will transit through the backup cloud security service via one of the standard VPN paths to the endpoints that are part of the backup group.
Prisma SD-WANPrisma SD-WANInternet-bound SSL traffic from a branch site will transit through one of the Prisma SD-WAN data center endpoints assigned to the active group via the Prisma SD-WAN VPNs. In the event all Prisma SD-WAN VPNs to all of those endpoints are down, internet-bound SSL traffic will transit through one of the Prisma SD-WAN data center endpoints assigned to the backup group via the Prisma SD-WAN VPNs.
  1. Navigate to ManagePrisma SD-WANPolicies.
  2. Select PathPath Sets.
  3. Select a Path Policy Set and an appropriate Path Policy rule.
    From the Path drop-down, select Standard VPN as either an Active or Backup path.
    You can mix Standard VPN with other available paths; private, public, direct or VPNs.
  4. Navigate to Service & DC Groups. Choose a group from either the Active or Backup drop-down lists.
    If standard VPN is used in a network policy, then you must have a standard Services & DC Group defined in the policy for the traffic to transit through that group. If not, traffic will be black-holed. If required is selected, traffic will always transit through the Services & DC Group. If not selected, traffic may or may not transit through the Services & DC Group per policy.