Next-Generation Firewall
Cheat Sheet: GlobalProtect for Cloud Management of NGFWs
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
Cloud Management of NGFWs
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
-
-
- Configure a Filter Access List
- Configure a Filter Prefix List
- Configure a Filter Community List
- Configure a BGP Filter Route Map
- Configure a Filter Route Maps Redistribution List
- Configure a Filter AS Path Access List
- Configure an Address Family Profile
- Configure a BGP Authentication Profile
- Configure a BGP Redistribution Profile
- Configure a BGP Filtering Profile
- Configure an OSPF Authentication Profile
- Configure a Logical Router
- Configure a Static Route
- Configure OSPF
- Configure BGP
- Configure an IPSec Tunnel
- Web Proxy
- Cheat Sheet: GlobalProtect for Cloud Management of NGFWs
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.2
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
Cheat Sheet: GlobalProtect for Cloud Management of NGFWs
Enable your cloud-managed NGFWs to work as GlobalProtect portals and gateways, to
provide flexible, secure remote access to users everywhere.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
GlobalProtect with cloud-managed NGFWs offers a comprehensive infrastructure for
securing your mobile workforce. You can use Strata Cloud Manager to centrally
manage GlobalProtect and your cloud-managed NGFWs. Enable your cloud-managed NGFWs
as GlobalProtect gateways and portals, to provide flexible, secure remote access to
users everywhere. This infrastructure includes the following components:
- GlobalProtect portal—The GlobalProtect portal provides the management functions for your GlobalProtect infrastructure. Every endpoint that participates in the GlobalProtect network receives configuration information from the portal, including information about available gateways as well as any client certificates that are required to connect to one or more GlobalProtect gateways. You can set up access to the GlobalProtect portal on an interface on the cloud-managed NGFWs.
- GlobalProtect gateways—The GlobalProtect gateways provide security enforcement for traffic originating from GlobalProtect applications. You can configure the NGFWs as external gateways by referencing the NGFWs' GlobalProtect gateway IP addresses, eliminating manual configuration and reducing the risk of configuration errors.
Get Started
- Ensure you have completed the following prerequisites:
- Created interfaces and zones for each firewall hosting a portal and/or a gateway. For gateways that require tunnel connections, configure both the physical and virtual tunnel interfaces.
- Set up the portal server certificate, gateway server certificate, SSL/TLS service profile, and optionally deploy any client certificates to enable SSL/TLS connections for GlobalProtect services.
- Created the authentication profiles and certificate profiles that the portals and gateways can utilize to authenticate GlobalProtect users.
- Established a fully qualified domain name (FQDN) alias for the interface where you plan to configure the gateway. For example, paloaltonetworks.com. Utilizing FQDN simplifies management as DNS resolves to the IP addresses automatically, eliminating the need for manual updates when IP addresses change.
- Select ManageConfigurationNGFW and Prisma AccessDevice SettingsGlobalProtect.
- Choose the Configuration Scope where you want to configure cloud-managed NGFWs to work as GlobalProtect.Select Global to apply configuration settings across all your NGFWs. Alternatively, you can choose a specific folder or firewall from your Folders or a Snippet to apply configuration to a group of objects associated with a folder.For example, you might create a folder named California and put 60 firewalls in it and then create another folder named Hawaii and put 15 firewalls in that. You then create a snippet called CA-HI and apply it to the California and Hawaii folders. When you want to import configuration settings only to firewalls in California, you set the scope as Folder and select the California folder. If you want to import the configuration settings to both California and Hawaii, set the scope as Snippet and select the CA-HI snippet.
- Define the GlobalProtect Agent Settings.Customize the Agent App Settings.Explore all GlobalProtect agent app settings available to you.
- Select Agent SettingsAdd Agent App Settings.
- Enter a Name for the agent app setting.
- Define the Match Criteria to specify the users, devices, or systems that should receive the settings.
- Specify the external gateways to which users with this configuration can connect. You can configure the firewall gateways as external gateways only; not as internal gateways.
- Add the External Gateway to which users can connect.
- Enter a descriptive Name for the gateway. Ensure that the name matches the one defined during the gateway configuration to provide clarity for users regarding the gateway's location.
- Select either the FQDN or
IP address of the interface where
the gateway is configured.
- For IP address, choose the Device and Gateway configured on that device, along with the IPv4 address of the interface, instead of manually entering them.
- Add one or more source regions for the gateway, or select Any to make the gateway available to all regions. GlobalProtect recognizes the region when users connect and restricts access to gateways configured for that region. The source region is considered first for gateway selection, followed by gateway priority.
- Set the Priority of the gateway by
clicking the field and selecting one of the following
values:
- If you have only one external gateway, leave the value set to Highest (the default).
- If you have multiple external gateways, adjust the priority values (ranging from Highest to Lowest) to indicate a preference for the specific user group. For example, if you prefer that the user group connects to a local gateway, set the priority higher than that of more geographically distant gateways.
- If you prefer applications not to automatically establish connections with the gateway, select Manual only. This setting is useful in testing environments.
- Select Manual to allow users to manually switch to the gateway.
- Save your changes.
Customize the Agent Tunnel Settings.Customize the settings for the VPN tunnel the GlobalProtect establishes to connect to the firewall. Explore all GlobalProtect agent tunnel settings available to you.- Select Agent SettingsAdd Agent Tunnel Settings.
- Enter a Name and define the Match Criteria to specify the users, devices, or systems that should receive the settings. For example, you could indicate that a tunnel settings rule applies to all instances of the GlobalProtect app in a specific region.
- Exclude Traffic to not send video streaming traffic from the listed applications to the firewall. Specify traffic to exclude from firewall policy inspection and enforcement based on application, domain, and route.
- Define how the GlobalProtect portals and gateways authenticate users using Profiles.Configure GP Authentication Profiles.Explore all GlobalProtect agent tunnel settings available to you.
- Select ProfilesGP Authentication ProfilesAdd Profile. You can configure the GlobalProtect portal to authenticate users through a local user database or an external authentication service, such as LDAP, Kerberos, TACACS+, SAML, RADIUS (including OTP), or Cloud Identity Engine (CIE).
- Enter a Name to identify the client authentication configuration.
- Specify the endpoints to which you want to deploy this configuration. To apply this configuration to all endpoints, accept the default OS of Any.
- To enable users to authenticate to the portal or gateway using their user credentials, select or add an Authentication Profile.
Configure Portal Agent Profiles.- Select ProfilesPortal Agent ProfilesAdd Profile
- Enter a portal agent profile Name.
- Select the agent app setting you created instep 3and Save the portal agent profile.
Configure Gateway Agent Profiles.- Select ProfilesGateway Agent ProfilesAdd Profile.
- Enter a gateway agent profile Name.
- Select the agent tunnel setting you created instep 3step 3and Save the gateway agent profile.
- Attach the profiles created to the GlobalProtect Portals and Gateways.Attach the authentication profile to a portal.
- Select Portals and GatewaysPortalsAdd Portal.
- Name the portal.
- Specify the network settings such as interface and IP address type to enable the GlobalProtect app to communicate with the portal.
- Specify how the portal authenticates users by adding the SSL/TLS Service Profile and certificate profile that you configured for the portal.
- Save the portal configuration.
Attach the authentication profile to a gateway.- Select Portals and GatewaysGatewaysAdd Gateway.
- Name the gateway.
- Specify the network settings such as interface and IP address type that enables endpoints to connect to the gateway.
- Specify how the gateway authenticates users by adding the SSL/TLS Service Profile and certificate profile that you configured for the gateway.
- Save the gateway configuration.
- Push ConfigPush to push configuration changes to your NGFWs.