|
| 1 | +--- |
| 2 | +title: 'Install Palo Alto Networks Cloud NGFW in a Virtual WAN hub' |
| 3 | +titleSuffix: Azure Virtual WAN |
| 4 | +description: Learn how to configure Palo Alto Networks Cloud NGFW in a Virtual WAN hub. |
| 5 | +services: virtual-wan |
| 6 | +author: wtnlee |
| 7 | + |
| 8 | +ms.service: virtual-wan |
| 9 | +ms.topic: how-to |
| 10 | +ms.date: 05/02/2023 |
| 11 | +ms.author: wellee |
| 12 | +ms.custom : references_regions |
| 13 | + |
| 14 | +--- |
| 15 | +# Configure Palo Alto Networks Cloud NGFW in Virtual WAN (preview) |
| 16 | + |
| 17 | +> [!IMPORTANT] |
| 18 | +> Palo Alto Cloud NGFW for Virtual WAN is currently in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. |
| 19 | +
|
| 20 | +[Palo Alto Networks Cloud Next Generation Firewall (NGFW)](https://aka.ms/pancloudngfwdocs) is a cloud-native software-as-a-service (SaaS) security offering that can be deployed into the Virtual WAN hub as a bump-in-the-wire solution to inspect network traffic. The following document describes some of the key features, critical use cases and how-to associated with using Palo Alto Networks Cloud NGFW in Virtual WAN. |
| 21 | + |
| 22 | +## Background |
| 23 | + |
| 24 | +Palo Alto Networks Cloud NGFW integration with Virtual WAN provides the following benefits to customers: |
| 25 | + |
| 26 | +* **Protect critical workloads** using a highly scalable SaaS security offering that can be injected as a bump-in-the-wire solution in Virtual WAN. |
| 27 | +* **Fully managed infrastructure and software lifecycle** under software-as-a-service model. |
| 28 | +* **Consumption-based pay-as-you-go** billing. |
| 29 | +* **Cloud-native experience** that has a tight integration with Azure to provide end-to-end Firewall management using Azure portal or Azure APIs. Rule and policy management is also optionally configurable through Palo Alto Network management solution Panorama. |
| 30 | +* **Dedicated and streamlined support channel** between Azure and Palo Alto Networks to troubleshoot issues. |
| 31 | +* **One-click routing** to configure Virtual WAN to inspect on-premises, Virtual Network and Internet-outbound traffic using Palo Alto Networks Cloud NGFW. |
| 32 | + |
| 33 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/deployment-topology.png" alt-text="Screenshot showing hub sample Virtual WAN topology with Cloud NGFW." lightbox="./media/how-to-palo-alto-cloudngfw/deployment-topology.png"::: |
| 34 | + |
| 35 | +## Use cases |
| 36 | + |
| 37 | +The following section describes the common security use cases for Palo Alto Networks Cloud NGFW in Virtual WAN. |
| 38 | + |
| 39 | +### Private (on-premises and virtual network) traffic |
| 40 | + |
| 41 | +>[!NOTE] |
| 42 | +> Traffic between connections to Virtual Hubs in **different** Azure regions will be dropped. Support for inter-region traffic flows is coming soon and are delineated with dotted lines. |
| 43 | + |
| 44 | +#### East-west traffic inspection |
| 45 | + |
| 46 | +Virtual WAN routes traffic from Virtual Networks to Virtual Network or from on-premises (Site-to-site VPN, ExpressRoute, Point-to-site VPN) to on-premises to Cloud NGFW deployed in the hub for inspection. |
| 47 | + |
| 48 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/east-west-cloud-ngfw.png" alt-text="Screenshot showing east-west traffic flows with Cloud NGFW." lightbox="./media/how-to-palo-alto-cloudngfw/east-west-cloud-ngfw.png"::: |
| 49 | + |
| 50 | +#### North-south traffic inspection |
| 51 | + |
| 52 | +Virtual WAN also routes traffic between Virtual Networks and on-premises (Site-to-site VPN, ExpressRoute, Point-to-site VPN) to on-premises to Cloud NGFW deployed in the hub for inspection. |
| 53 | + |
| 54 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/north-south-cloud-ngfw.png" alt-text="Screenshot showing north-south traffic flows with Cloud NGFW." lightbox="./media/how-to-palo-alto-cloudngfw/north-south-cloud-ngfw.png"::: |
| 55 | + |
| 56 | +### Internet edge |
| 57 | + |
| 58 | +>[!NOTE] |
| 59 | +> The 0.0.0.0/0 default route does not propagate across hubs. On-premises and Virtual Networks can only use local Cloud NGFW resources to access the Internet. Additionally, for Destination NAT use cases, Cloud NGFW can only forward incoming traffic to local Virtual Networks and on-premises. |
| 60 | +
|
| 61 | +#### Internet egress |
| 62 | + |
| 63 | +Virtual WAN can be configured to route internet-bound traffic from Virtual Networks or on-premises to Cloud NGFW for inspection and internet breakout. You can selectively choose which Virtual Network(s) or on-premise(s) learn the default route (0.0.0.0/0) and use Palo Alto Cloud NGFW for internet egress. In this use case, Azure automatically NATs the source IP of your internet-bound packet to the public IPs associated with the Cloud NGFW. |
| 64 | + |
| 65 | +For more information on internet-outbound capabilities and available settings, see [Palo Alto Networks documentation](https://aka.ms/pancloudngfwdocs). |
| 66 | + |
| 67 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/internet-outbound-cloud-ngfw.png" alt-text="Screenshot showing internet-outbound traffic flows with Cloud NGFW." lightbox="./media/how-to-palo-alto-cloudngfw/internet-outbound-cloud-ngfw.png"::: |
| 68 | + |
| 69 | +#### Internet ingress (DNAT) |
| 70 | +You can also configure Palo Alto Networks for Destination-NAT (DNAT). Destination NAT allows a user to access and communicate with an application hosted on-premises or in an Azure Virtual Network via the public IPs associated with the Cloud NGFW. |
| 71 | + |
| 72 | +For more information on internet-inbound (DNAT) capabilities and available settings, see [Palo Alto Networks documentation](https://aka.ms/pancloudngfwdocs). |
| 73 | + |
| 74 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/internet-inbound-cloud-ngfw.png" alt-text="Screenshot showing internet-inbound traffic flows with Cloud NGFW." lightbox="./media/how-to-palo-alto-cloudngfw/internet-inbound-cloud-ngfw.png"::: |
| 75 | + |
| 76 | +## Before you begin |
| 77 | + |
| 78 | +The steps in this article assume you have already created a Virtual WAN. |
| 79 | + |
| 80 | +To create a new virtual WAN, use the steps in the following article: |
| 81 | + |
| 82 | +* [Create a Virtual WAN](virtual-wan-site-to-site-portal.md#openvwan) |
| 83 | + |
| 84 | +## Known limitations |
| 85 | + |
| 86 | +* Palo Alto Networks Cloud NGFW is only available in the following Azure regions: Central US, East US, East US 2, West Europe and Australia East. Other Azure regions are on the roadmap. |
| 87 | +* Palo Alto Networks Cloud NGFW can only be deployed in new Virtual WAN hubs deployed with Azure resource tag **"hubSaaSPreview : true"**. Using existing Virtual Hubs with Palo Alto Networks Cloud NGFW is on the roadmap. |
| 88 | +* Palo Alto Networks Cloud NGFW can't be deployed with Network Virtual Appliances in the Virtual WAN hub. |
| 89 | +* For routing between Virtual WAN and Palo Alto Networks Cloud NGFW to work properly, your entire network (on-premises and Virtual Networks) must be within RFC-1918 (subnets within 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12). For example, you may not use a subnet such as 40.0.0.0/24 within your Virtual Network or on-premises. Traffic to 40.0.0.0/24 may not be routed properly. |
| 90 | +* All other limitations in the [Routing Intent and Routing policies documentation limitations section](how-to-routing-policies.md) apply to Palo Alto Networks Cloud NGFW deployments in Virtual WAN. |
| 91 | + |
| 92 | +## Register resource provider |
| 93 | + |
| 94 | +To you Palo Alto Networks Cloud NGFW, you must register the **PaloAltoNetworks.Cloudngfw** resource provider to your subscription with an API version that is at minimum **2022-08-29-preview**. |
| 95 | + |
| 96 | +For more information on how to register a Resource Provider to an Azure subscription, see [Azure resource providers and types documentation](../azure-resource-manager/management/resource-providers-and-types.md). |
| 97 | +## Deploy virtual hub |
| 98 | +The following steps describe how to deploy a Virtual Hub that can be used with Palo Alto Networks Cloud NGFW. |
| 99 | + |
| 100 | +1. Navigate to your Virtual WAN resource. |
| 101 | +1. On the left hand menu, select **Hubs** under **Connectivity**. |
| 102 | +1. Click on **New Hub**. |
| 103 | +1. Under **Basics** specify a region for your Virtual Hub. Make sure the region is Central US, East US, East US 2, West Europe or Australia East. Additionally, specify a name, address space, Virtual hub capacity and Hub routing preference for your hub. |
| 104 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/create-hub.png" alt-text="Screenshot showing hub creation page. Region selector box is highlighted." lightbox="./media/how-to-palo-alto-cloudngfw/create-hub.png"::: |
| 105 | +1. Select and configure the Gateways (Site-to-site VPN, Point-to-site VPN, ExpressRoute) you want to deploy in the Virtual Hub. You can deploy Gateways later if you wish. |
| 106 | +1. Apply an Azure Resource tag to your Virtual Hub **"hubSaaSPreview":"true"**. This tag must be specified at hub deployment time to use Palo Alto Networks Cloud NGFW. |
| 107 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/apply-tags.png" alt-text="Screenshot showing hub tag creation page." lightbox="./media/how-to-palo-alto-cloudngfw/apply-tags.png"::: |
| 108 | +1. Click **Review + create**. |
| 109 | +1. Click **Create** |
| 110 | +1. Navigate to your newly created hub and wait for the **Routing Status** to be **Provisioned**. This step can take up to 30 minutes. |
| 111 | + |
| 112 | +## Deploy Palo Alto Networks Cloud NGFW |
| 113 | + |
| 114 | +>[!NOTE] |
| 115 | +> You must wait for the routing status of the hub to be "Provisioned" before deploying Cloud NGFW. |
| 116 | + |
| 117 | +1. Navigate to your Virtual Hub and click on **SaaS solutions** under **Third-party providers**. |
| 118 | +1. Click **Create SaaS** and select **Palo Alto Networks Cloud NGFW (preview)**. |
| 119 | +1. Click **Create**. |
| 120 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/create-saas.png" alt-text="Screenshot showing SaaS creation page." lightbox="./media/how-to-palo-alto-cloudngfw/create-saas.png"::: |
| 121 | +1. Provide a name for your Firewall. Make sure the region of the Firewall is the same as the region of your Virtual Hub. For more information on the available configuration options for Palo Alto Networks Cloud NGFW, see [Palo Alto Networks documentation for Cloud NGFW](https://aka.ms/pancloudngfwdocs). |
| 122 | + |
| 123 | +## Configure Routing |
| 124 | + |
| 125 | +>[!NOTE] |
| 126 | +> You can't configure routing intent until the Cloud NGFW is successfully provisioned. |
| 127 | +
|
| 128 | +1. Navigate to your Virtual Hub and click on **Routing intent and policies** under **Routing** |
| 129 | +1. If you want to use Palo Alto Networks Cloud NGFW to inspect outbound Internet traffic (traffic between Virtual Networks or on-premises and the Internet), under **Internet traffic** select **SaaS solution**. For the **Next Hop resource**, select your Cloud NGFW resource. |
| 130 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/internet-routing-policy.png" alt-text="Screenshot showing internet routing policy creation." lightbox="./media/how-to-palo-alto-cloudngfw/internet-routing-policy.png"::: |
| 131 | +1. If you want to use Palo Alto Networks Cloud NGFW to inspect private traffic (traffic between all Virtual Networks and on-premises in your Virtual WAN), under **Private traffic** select **SaaS solution**. For the **Next Hop resource**, select your Cloud NGFW resource. |
| 132 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/private-routing-policy.png" alt-text="Screenshot showing private routing policy creation." lightbox="./media/how-to-palo-alto-cloudngfw/private-routing-policy.png"::: |
| 133 | + |
| 134 | +## Manage Palo Alto Networks Cloud NGFW |
| 135 | + |
| 136 | +The following section describes how you can manage your Palo Alto Networks Cloud NGFW (rules, IP addresses, security configurations etc.) |
| 137 | + |
| 138 | +1. Navigate to your Virtual Hub and click on **SaaS solutions**. |
| 139 | +1. Click on **Click here** under **Manage SaaS**. |
| 140 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/manage-saas.png" alt-text="Screenshot showing how to manage your SaaS solution." lightbox="./media/how-to-palo-alto-cloudngfw/manage-saas.png"::: |
| 141 | +1. For more information on the available configuration options for Palo Alto Networks Cloud NGFW, see [Palo Alto Networks documentation for Cloud NGFW](https://aka.ms/pancloudngfwdocs). |
| 142 | + |
| 143 | +## Delete Palo Alto Networks Cloud NGFW |
| 144 | + |
| 145 | +>[!NOTE] |
| 146 | +> You can't delete your Virtual Hub until both the Cloud NGFW and Virtual WAN SaaS solution are deleted. |
| 147 | +
|
| 148 | +The following steps describe how to delete a Cloud NGFW offer: |
| 149 | + |
| 150 | +1. Navigate to your Virtual Hub and click on **SaaS solutions**. |
| 151 | +1. Click on **Click here** under **Manage SaaS**. |
| 152 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/manage-saas.png" alt-text="Screenshot showing how to manage your SaaS solution." lightbox="./media/how-to-palo-alto-cloudngfw/manage-saas.png"::: |
| 153 | +1. Click on **Delete** in the upper left-hand corner of the page. |
| 154 | + :::image type="content" source="./media/how-to-palo-alto-cloudngfw/delete-ngfw.png" alt-text="Screenshot showing delete Cloud NGFW options." lightbox="./media/how-to-palo-alto-cloudngfw/delete-ngfw.png"::: |
| 155 | +1. After the delete operation is successful, navigate back to your Virtual Hub's **SaaS solutions** page. |
| 156 | +1. Click on the line that corresponds to your Cloud NGFW and click **Delete SaaS** on the upper left-hand corner of the page. This option won't be available until Step 3 runs to completion. |
| 157 | +:::image type="content" source="./media/how-to-palo-alto-cloudngfw/delete-saas.png" alt-text="Screenshot showing how to delete your SaaS solution." lightbox="./media/how-to-palo-alto-cloudngfw/delete-saas.png"::: |
| 158 | + |
| 159 | +## Troubleshooting |
| 160 | + |
| 161 | +The following section describes common issues seen when using Palo Alto Networks Cloud NGFW in Virtual WAN. |
| 162 | + |
| 163 | +### Troubleshooting Cloud NGFW creation |
| 164 | + |
| 165 | +* Ensure your Virtual Hubs are deployed in one of the following regions: Central US, East US, East US 2, West Europe or Australia East. Cloud NGFW deployment fails in other regions. |
| 166 | +* Ensure your Virtual Hub was created with the Azure Resource Tag **"hubSaaSPreview" : "true"**. Hubs created without this tag aren't eligible to be used with Cloud NGFW. These tags must be specified at hub creation time and can't be provided after hub deployment. To use Cloud NGFW, you need to create a new Virtual Hub. |
| 167 | +* Ensure the Routing status of the Virtual Hub is "Provisioned." Attempts to create Cloud NGFW prior to routing being provisioned will fail. |
| 168 | +* Ensure registration to the **PaloAltoNetworks.Cloudngfw** resource provider is successful. |
| 169 | + |
| 170 | +### Troubleshooting deletion |
| 171 | + |
| 172 | +* A SaaS solution can't be deleted until the linked Cloud NGFW resource is deleted. Therefore, delete the Cloud NGFW resource before deleting the SaaS solution resource. |
| 173 | +* A SaaS solution resource that is currently the next hop resource for routing intent can't be deleted. Routing intent must be deleted before the SaaS solution resource can be deleted. |
| 174 | +* Similarly, a Virtual Hub resource that has a SaaS solution can't be deleted. The SaaS solution must be deleted before the Virtual Hub is deleted. |
| 175 | + |
| 176 | +### Troubleshooting Routing intent and policies |
| 177 | + |
| 178 | +* Ensure Cloud NGFW deployment is completed successfully before attempting to configure Routing Intent. |
| 179 | +* For more information about troubleshooting routing intent, see [Routing Intent documentation](how-to-routing-policies.md). This document describes pre-requisites, common errors associated with configuring routing intent and troubleshooting tips. |
| 180 | + |
| 181 | +### Troubleshooting Palo Alto Networks Cloud NGFW configuration |
| 182 | + |
| 183 | +* Reference [Palo Alto Networks documentation](https://aka.ms/pancloudngfwdocs). |
| 184 | + |
| 185 | +## Next steps |
| 186 | + |
| 187 | +* For more information about Virtual WAN, see the [FAQ](virtual-wan-faq.md). |
| 188 | +* For more information about routing intent, see the [Routing Intent documentation](how-to-routing-policies.md). |
| 189 | +* For more information about Palo Alto Networks Cloud NGFW, see [Palo Alto Networks Cloud NGFW documentation](https://aka.ms/pancloudngfwdocs). |
0 commit comments