Learn more about enabling network access to the Cortex XDR resources.
After you receive your account details, enable and verify access to Cortex XDR communication servers, storage buckets, and various resources in your firewall configuration. Some of the IP addresses required for access are registered in the United States. As a result, some GeoIP databases do not correctly pinpoint the location where IP addresses are used. All customer data is stored in your deployment region, regardless of the IP address registration, and data transmission is restricted through any infrastructure to that region.
Before configuring your firewall, review these guidelines:
Palo Alto Networks App-IDs (firewall policy): If you are using a Palo Alto Networks Firewall, you can simplify your configuration by using App-IDs. If you add the specific App-IDs (for example,
cortex-xdr,traps-management-service) to your firewall security policy, you do not need to allow specific IP addresses listed below manuallyApp-ID limitations: A dash (—) indicates there is no App-ID coverage for a specific resource. For these rows, you must configure your firewall to allow access based on the IP address and port.
Rule direction: Enable access from the Cortex XDR Agent to the tenant (outbound); this traffic does not need to be bidirectional.
Google Cloud Platform (GCP): For resources listing IP ranges in the GCP, go to the official JSON feeds for the specific IP addresses required for your deployment:
Global subnets: https://www.gstatic.com/ipranges/goog.json
Regional ranges: https://www.gstatic.com/ipranges/cloud.json
SSL decryption: If you use SSL decryption and experience difficulty connecting the Cortex XDR agent to the server, we recommend that you add the FQDNs required for access to your SSL Decryption Exclusion list in → → .
Note
refers to the selected subdomain of your Cortex XDR tenant, and <tenant-name> is the region in which your tenant is deployed. For more information, see Cortex XDR supported regions.<region>
The following table lists the required resources by region, including FQDNs, IP addresses, ports, and App-ID coverage for your deployment:
FQDN | IP Addresses and Port | App-ID Coverage |
|---|---|---|
Egress | ||
Used to connect to the Cortex XDR tenant. | IP address by region:
|
|
Used for the first request in registration flow where the agent passes the distribution id and obtains the |
|
|
Used in live terminal flow. | IP address by region:
|
|
Used to download installers for upgrade actions from the server. This storage bucket is used for all regions. |
|
|
Used to download the executable for the live terminal for XDR agents earlier than version 7.1.0. This storage bucket is used for all regions. |
|
|
Used to download content updates. |
|
|
Used to download extended verdict request results in scanning. |
|
|
Used to download the Kubernetes image from the registry for Kubernetes agents installation. NoteRefer to Regional Docker registry mapping for your specific tenant location and corresponding Docker registry URL. |
| |
Regional Docker registry mapping | ||
Tenant location | GCP region | Registry URL |
UK Netherlands (EU) United States (US) Canada (CA) South Korea (KR) Singapore (SG) Australia (AU) Japan (JP) India (IN) Germany (DE) France (FR) | europe-west2 europe-west4 us-central1 northamerica-northeast1 asia-northeast3 asia-southeast1 australia-southeast1 asia-northeast1 asia-south1 europe-west3 europe-west9 | europe-west2-docker.pkg.dev europe-west4-docker.pkg.dev us-central1-docker.pkg.dev northamerica-northeast1-docker.pkg.dev asia-northeast3-docker.pkg.dev asia-southeast1-docker.pkg.dev australia-southeast1-docker.pkg.dev asia-northeast1-docker.pkg.dev asia-south1-docker.pkg.dev europe-west3-docker.pkg.dev europe-west9-docker.pkg.dev |
Used for EDR data upload. | IP address by region:
|
|
Used for all other requests between the agent and its tenant server, including heartbeat, uploads, action results, and scan reports. | IP address by region:
|
|
Used for API requests and responses and to connect to an engine. | IP address by region:
| — |
Used for get-verdict requests. NoteFor agents on endpoints, you must allow the IP address for the closest region to ensure connectivity. Endpoints use latency-based routing. An agent that belongs to a US tenant, for example, but that is physically located in Singapore, routes to Singapore to get the verdict. | IP address by region:
|
|
Broker VM Resources Required for deployments that use Broker VM features | ||
xdr-ova-installers-prod-us.storage.googleapis.com Used to download Broker VM images from the server. This storage bucket is used for all regions. |
|
|
| IP address by region:
| — |
|
|
|
| UDP port: 123 | — |
App Login and Authentication | ||
identity.paloaltonetworks.com (SSO) |
| — |
login.paloaltonetworks.com (SSO) |
| — |
In-App Help Center and Notifications | ||
data.pendo.io | Port: 443 | — |
pendo-static-5664029141630976.storage.googleapis.com | Port: 443 | — |
Email Notifications | ||
— | IP address for all regions: 159.183.150.248 | — |
Ingress These IPs are used for communication between Cortex XDR and your resources. Use them when sending data out from your tenant. | ||
|
| |
Outbound IPs for engines | ||
IP addresses by region
| — | |
Collect third-party data from your SaaS and Cloud resources | ||
— | IP address by region.
|
|
Log Forwarding to a Syslog Receiver | ||
FedRAMP and US Federal Government required resources
The following table lists the required resources for the federal government of the United States, including FQDNs, IP addresses, ports, and App-ID coverage for your deployment:
FQDN | IP Addresses and Port | App-ID Coverage |
|---|---|---|
Egress | ||
FedRAMP Moderate
FedRAMP High
| ||
Outbound IPs for Engines | ||
FedRAMP Moderate
FedRAMP High
| ||
Used for the first request in registration flow where the agent passes the distribution ID and obtains the |
|
|
Used in live terminal flow. |
|
|
Used to download installers for upgrade actions from the server. |
|
|
Used to download the executable for the live terminal for Cortex XDR agents earlier than version 7.1.0. |
|
|
Used to download content updates. |
|
|
Used to download extended verdict request results in scanning. |
|
|
|
| — |
Used for EDR data upload. |
|
|
Used for all other requests between the agent and its tenant server including heartbeat, uploads, action results, and scan reports. |
|
|
Used for API requests and responses. |
| — |
Used for get-verdict requests. |
|
|
Broker VM resources Required for deployments that use Broker VM features | ||
|
| — |
|
| — |
|
|
|
UDP port: 123 | — | |
App login and authentication | ||
identity.paloaltonetworks.com (SSO) |
| — |
login.paloaltonetworks.com (SSO) |
| — |
Collect third-party data from your SaaS and Cloud resources | ||
— | IP addresses
|
|
Log Forwarding to a Syslog Receiver | ||