Next-Generation Firewall
TCP Ports and FQDNs Required for Strata Cloud Manager
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
TCP Ports and FQDNs Required for Strata Cloud Manager
Review the TCP ports and FQDNs required to managed Palo Alto Networks Next-Gen Firewalls
(NGFW) from Strata Cloud Manager.
Contact your account team to enable Cloud Management for NGFWs using Strata
Cloud Manager.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Review the TCP ports and Fully Qualified Domain Names (FQDN) that you must enable on your network
communication and between the Palo Alto Networks Next-Gen Firewall (NGFW) and Strata Cloud Manager. Communication on these TCP ports and FQDNs must allowed on your
network to successfully manage your firewalls from Strata Cloud Manager.
- Connections to Strata Cloud Manager
- Connections to Strata Logging Service
- Connections for Firewall Certificates
Connections to Strata Cloud Manager
You must allow the following app, FQDNs, and TCP ports on your network to enable connectivity
between the firewall and Strata Cloud Manager.
The Virtus service is a device connectivity service that facilitates the connection
between the firewall and Strata Cloud Manager. The FQDN and/or IP address for the
region where your Strata Cloud Manager tenant is deployed must be allowed on your
network for the firewall to successfully connect to Strata Cloud Manager. The
firewall cannot connect to Strata Cloud Manager if the FQDN or IP address is
blocked.
App-ID | TCP Port |
---|---|
panorama | 3978 |
Service
|
FQDN
|
IP Address
|
TCP Ports
|
---|---|---|---|
OCSP
|
|
N/A
|
80
|
Virtus
|
Australia—*.aus.ngfw.cloudmgmt.paloaltonetworks.com
|
34.151.118.202
|
3978
443
|
E.U—*.eu.ngfw.cloudmgmt.paloaltonetworks.com
|
35.246.199.57
| ||
India—*.in.ngfw.cloudmgmt.paloaltonetworks.com
|
35.200.223.12
| ||
Indonesia—*.id.ngfw.cloudmgmt.paloaltonetworks.com
|
34.101.126.22
| ||
Japan—*.jp.ngfw.cloudmgmt.paloaltonetworks.com
|
34.146.27.93
| ||
Qatar—*.qa.ngfw.cloudmgmt.paloaltonetworks.com
|
34.18.53.154
| ||
Singapore—*.sg.ngfw.cloudmgmt.paloaltonetworks.com
|
35.198.210.240
| ||
U.K—*.uk.ngfw.cloudmgmt.paloaltonetworks.com
|
35.246.86.14
| ||
U.S.A—*.us.ngfw.cloudmgmt.paloaltonetworks.com
|
34.31.195.141
| ||
Discovery Service
|
ds-cloudmgmt.paloaltonetworks.com
|
N/A
|
443
|
Connections to Strata Logging Service
You must allow the following apps, FQDNs, and TCP ports
on your network to forward logs from the managed firewall to Strata Logging Service (SLS). For more details, see the TCP Ports and FQDNs Required
for (SLS).
App-ID | TCP Port |
---|---|
| 444 3978 |
Required if you’re sending device telemetry
data to SLS.
| 443 5222-5224 5228 5229 |
Service | FQDN | TCP Ports |
---|---|---|
OCSP | 80 | |
SLS Certificates | 3978 | |
Prisma Access | *.gpcloudservice.com | 443 |
Connections for Firewall Certificates
You must allow the following FQDNs, and TCP ports on your network to enable your managed
firewalls to install the device certificates for Strata Cloud Manager.
Service | FQDN | TCP Ports |
---|---|---|
API | 443 | |
Device Certificates | 443 |