Onboard a Google Cloud Platform Virtual Private Cloud
Onboard an Google Cloud Platform VPC to Prisma Access and secure access to it for mobile users and remote networks.
You can secure resources in a Google Cloud Platform (GCP) virtual private cloud (VPC) seamlessly using Prisma Access by onboarding the VPC as a remote network connection. Prisma Access establishes an industry-standard IPSec tunnel between Prisma Access and the GCP virtual network to provide connectivity to resources in GCP. After you onboard the virtual network, you can define security and access controls by configuring security policies for the remote network, which provides consistent policy management and control for all of your Prisma Access remote networks.
Currently, GCP does not support creating two VPN tunnels within the same Cloud VPN gateway to the same Prisma Access instance; therefore, high availability using primary and secondary tunnels is not available with GCP. However, the GCP incorporates high availability by providing a service level agreement (SLA) of 99.9% cloud VPN service availability. If the GCP cloud VPN goes down, it restarts automatically. If an entire virtual VPN device fails, the cloud VPN automatically instantiates a new one with the same configuration. The new gateway and tunnel connect automatically. For more information about High Availability and Classic VPNs, see the Google Cloud document Redundant and High-throughput VPNs.
Use the following workflow to secure a GCP VPC with Prisma Access.
- Create IKE and IPSec profiles and onboard the GCP VPC in Prisma Access.To begin the configuration of the GCP VPN connection, create IKE and IPSec security profiles and policies, then create a remote network connection in Prisma Access to onboard the GCP VPC.
- In Panorama, selectRemote_Network_Templatefrom theTemplatedrop-down.
- SelectandNetworkNetwork ProfilesIKE CryptoAddan IKE crypto profile for the gateway.Make a note of these settings; the IKE crypto settings you specify here must match the settings that you specify on GCP when you configure the IPSec tunnel in GPC. For a list of IKE cyphers that GCP supports, see the Google Cloud document Supported IKE Cyphers. For more information about configuring the IKE the IPSec settings on GCP, see the Google Cloud document Configuring the On-premises VPN Gateway.We recommend the following settings:
- DH Group:group14
- Key Lifetime:8 Hours
- SelectandNetworkNetwork ProfilesIPSec CryptoAddan IPSec crypto profile for the IPSec tunnel.The IPSec crypto settings you specify here must match the settings you specify on GCP. The screenshot in the following figure uses the following settings:
- IPSec Protocol:ESP
- DH Group:group14
- Lifetime:3 Hours
- Authentication:NoneIf you select an AES-GCM algorithm for encryption, you must select theAuthenticationsettingnoneor the commit will fail. The hash is automatically selected based on the DH Group selected. DH Group 19 and below uses sha256; DH Group 20 uses sha384.
- SelectandNetworkNetwork ProfilesIKE GatewaysAddan IKE gateway.Use the following IKE gateway parameters:
- ForPeer IP Address Type, selectIP.
- Enter any IP address (for example, 188.8.131.52) in thePeer Addressfield.This setting is temporary; you add an IP address in after you retrieve the peer address from GCP in a later step.
- Configure aPre-shared key.
- SelectAdvanced Optionsand specify the IKE crypto profile that you created in a previous step.
- SelectandNetworkIPSec TunnelsAddan IPSec tunnel for the GCP VPC, specifying theIKE gatewayandIPSec Crypto Profilethat you created earlier in this task.
- Create a remote network connection for the GCP VPC.
- SelectandPanoramaCloud ServicesConfigurationRemote NetworksAddthe GCP VPC as a remote network.Use the following choices:
- Select aLocationthat is closest to your GCP VPC.
- Select anIPSec Termination Node.An IPSec termination node can provide you with a maximum of 500 Mbps of bandwidth; however, total bandwidth would depend on how much bandwidth you allocated to the compute location to which the IPSec Termination Node belongs. Use a bandwidth based on the amount of traffic that Prisma Access can receive from the GCP VPC and the licensed bandwidth for Prisma Access.
- Specify the IPSec primary tunnel that you just created in theIPSec Tunnelfield.
- Specify either static or dynamic (BGP) routing.
- (Deployments Using Static Routes Only) SelectStatic Routes, then enterBranch IP Subnetsthat will correspond to the specific or summary subnets of your VPC.This subnet is a placeholder; you specify the correct subnet when you configure the VPN connection on GCP.
- (Deployments Using BGP Routing Only) SelectBGP,EnableBGP networking, and enter thePeer AS, which is the autonomous system number (ASN) to which the firewall, virtual router, or BGP router at your remote network belongs.Make a note of the ASN; you specify the same ASN when you configure dynamic (BGP) routing in GCP.For a description of the additional fields you can configure for BGP routing, see Configure Prisma Access for Networks in the Prisma Access Administrator’s Guide (Panorama Managed).
- CommitandPushyour configuration.
- After the onboarding process completes, selectand make a note of the value in thePanoramaCloud ServiceStatusNetwork DetailsRemote NetworksService IP Addressfield.You use this address as theRemote peer IP addresswhen you configure the VPN connection on GCP.
- Create and configure the VPN Connection in GCP.GCP uses a VPN connection to let you securely connect to Prisma Access. For more information about GCP interoperability, refer to the Google Cloud list of VPN Interoperability Guides.
- Log in to GCP.
- Begin the VPN connection and add an IP address to it by enteringvpninto the search box; then selectingHybrid Connectivity.The GCP screens in this document might not reflect the latest version of the GCP user interface (UI).
- ClickCreate VPN connection.
- In theGoogle Compute Engine VPN Gatewayfield, enter the following values:
GCP reserves the publicIP addressfor the VPN connection.Make a note of theIP addressthat GCP assigned; you enter this in Prisma Access in the IKE gatewayPeer Addressfield in a later step.
- Enter aNamefor the connection.
- (Optional) Enter aDescriptionof the connection.
- Enter theNetworkto use with the VPN connection.Specify the network you created on GCP that you want to secure with Prisma Access.
- Enter aRegionfor the VPN connection.
- In theIP addressfield, selectCreate IP address, provide aNameandDescriptionfor the static IP address; then, clickReserve.
- In theTunnelsarea, enter the following values:If you have an existing VPN Gateway, selectAdd VPN Tunnelin theVPN tunnelsarea.
- Enter aNamefor the tunnel.
- (Optional) Enter aDescriptionof the tunnel.
- Enter aRemote peer IP address, using theService IP Addressfrom the remote network in Prisma Access ().PanoramaCloud ServiceStatusNetwork DetailsRemote Networks
- Enter theIKE versionof the tunnel.This value must match the IKE version you specified in Prisma Access.
- Enter aShared secretthat matches thePre-shared Keythat you configured for the IKE gateway in Prisma Access.
- In theRouting optionsfield, select one of the following options:
- (Deployments Using Static Routes Only) To set up a static connection between GCP and Prisma Access, selectRoute-based
- (Deployments Using BGP Routing Only) To set up a dynamic (BGP) connection between GCP and Prisma Access, selectDynamic (BGP).
- (Deployments Using Static Routes Only) Enter one or moreRemote network IP ranges.Use theStatic SubnetIP addresses for the service connections and remote networks of Prisma Access (andPanoramaCloud ServiceStatusNetwork DetailsService Connection).PanoramaCloud ServiceStatusNetwork DetailsRemote Networks
- (Deployments Using BGP Routing Only)Create BGP Session.
For more information about configuring BGP routing in GCP, refer to the GCP documentation.
- Enter aNamefor the BGP session.
- Enter thePeer ASN.Specify the same ASN you gave for the Prisma Access ASN.
- Create aCloud Router BGP IPaddress andBGP Peer IPaddress.You must use a link local IP address (the IP address taken from the address block 169.254.0.0/16), and the Cloud Router BGP address and the BGP peer address must be in the same /30 subnet.
- Save and Continueto save your changes and return to the BGP screen.
- (Deployments Using Static Routes Only) Complete the VPN connection in Prisma Access.If you are using static routes for your remote network connection, complete the GCP VPN connection by adding the Peer Address to the Prisma Access remote network configuration.
- In Panorama, select.NetworkNetwork ProfilesIKE Gateways
- Select the IKE Gateway that you created in an earlier step.
- Enter thePeer Address.Find this address on GCP, in theIP addressfield for the VPN connection, in theGoogle Compute Engine VPN Gatewayarea.
- CommitandPushyour configuration.
- Verify remote network connectivity from GCP and from Prisma Access.
- From the GCP console, find the tunnel and check itsStatus. It should showEstablished.Note that theGoogle IP addressis the same as thePeer Addressthat is used in Prisma Access in the IKE gateway.
- To verify that there is connectivity between GCP and Prisma Access, complete the following steps.
- In Panorama, select.PanoramaCloud ServicesStatusMonitorRemote NetworksStatusTheConfig Statusshould beIn Syncand theTunnel Statusshould beOK.
- From the GCP console, selectand verify that the static routes have been populated in the GCP routing table.NetworkRoutesNote that this route list includes an all-zeros (default) route. A default route is required to secure all traffic to and from the GCP VPC. You secure internet-bound traffic with Prisma Access by creating a default route on GCP as shown in the next step.
- Secure internet-bound traffic with Prisma Access.To secure all traffic to and from GCP, you must allow all traffic including internet traffic to pass through Prisma Access. Because there is no default route, GCP routes internet-bound traffic from virtual machines over the GCP backbone instead of the VPN tunnel, which means that internet-bound traffic is not secured with Prisma Access. To direct all traffic to Prisma Access, either configure all internet-bound routes with static routes to Prisma Access or create a default route on GCP with or without instance tags.Using the VPN tunnel as the default route may result in a loss of connectivity to virtual network instances over the internet. Make sure that you use another connection method (for example, a bastion host) to connect to instances over the internet.To configure a default route between GCP and Prisma Access, create a new route with or without instance tags to which the route will be applied. The following example adds a default route for the Prisma Access network which is applied to theprivate-networktag. After you add this default route, all instances with theprivate-networktag in the VPC will use the VPN connection between GCP and Prisma Access as the default route.
Troubleshoot the IPSec Tunnel
To troubleshoot the site-to-site connection in Prisma Access, log in to Panorama and select
, then enter
(subtype eq vpn)in the
Filterfield to view messages related to VPN tunnel creation.
Recommended For You
Recommended videos not found.