Setup Access Services - Administrator Guide - Cortex XDR - Cortex - Security Operations

Cortex XDR Prevent Administrator Guide

Cortex XDR
Creation date
Last date published
Administrator Guide

Learn more about enabling access to Cortex XDR services.

After you receive your account details, enable and verify access to Cortex XDR.

  1. (Optional) If you are deploying the Broker VM as a proxy between Cortex XDR and the Cortex XDR agents, start by enabling the communication between them.

  2. In your firewall configuration, enable access to Cortex XDR communication servers, storage buckets, and resources.

    For the complete list of resources, refer to Resources Required to Enable Access to Cortex.

    With Palo Alto Networks firewalls, we recommend that you use the following App-IDs to allow communication between Cortex XDR agents and the Cortex XDR management console when you configure your security policy:

    • cortex-xdr—Requires PAN-OS Applications and Threats content update version 8279 or a later release.

    • traps-management-service—Requires PAN-OS Applications and Threats content update version 793 or a later release.

    If you use App-ID in your security policy, you must also allow access to additional resources that are not covered by the App-ID. If you do not use Palo Alto Networks firewalls with App-ID you must allow access to the full list of resources.

  3. Optional for endpoints running Cortex XDR agent 8.2 or earlier. To establish secure communication (TLS) to Cortex XDR, the endpoints, and any other devices that initiate a TLS connection with, you must have the following certificates installed on the operating system.

    For Cortex XDR agent 8.3 or later, with Certificate Enforcement enabled, this step is obsolete.



    GoDaddy Root Certificate Authority - G2 (Godaddy)

    • SHA1 Fingerprint—47 BE AB C9 22 EA E8 0E 78 78 34 62 A7 9F 45 C2 54 FD E6 8B

    • SHA256 Fingerprint—45 14 0B 32 47 EB 9C C8 C5 B4 F0 D7 B5 30 91 F7 32 92 08 9E 6E 5A 63 E2 74 9D D3 AC A9 19 8E DA

    GoDaddy Class 2 Root Certification Authority Certificate

    • SHA1 Fingerprint—27 96 BA E6 3F 18 01 E2 77 26 1B A0 D7 77 70 02 8F 20 EE E4

    • SHA256 Fingerprint—C3 84 6B F2 4B 9E 93 CA 64 27 4C 0E C6 7C 1E CC 5E 02 4F FC AC D2 D7 40 19 35 0E 81 FE 54 6A E4

    R1 GlobalSign Root Certificate (Google)

    • SHA1 Fingerprint—b1 bc 96 8b d4 f4 9d 62 2a a8 9a 81 f2 15 01 52 a4 1d 82 9c

    • SHA256 Fingerprint—eb d4 10 40 e4 3e c7 c9 e3 81 d3 1e f2 a4 1a 48 b6 68 5c 96 e7 ce f3 c1 df 6c d4 33 1c 99


    For the Cortex XDR agent 5.X release installed on endpoints running a Windows version that does not support SHA256 by default, you must install KB2868626 to establish a connection between Cortex XDR and the agent. This applies to Windows Server 2003 R2 (32-bit) (SP2 & later), Windows Server 2003 (32-bit) (SP2 & later), Windows XP (32-bit) (SP3 & later), Windows Server 2008 (all editions; FIPS Mode), and Windows Vista (SP1 & later; FIPS Mode).

  4. (Windows only) Enable access for Windows CRL checks.

    (Endpoints running the following or later releases: Traps 6.0.3, Traps 6.1.1, and Cortex XDR 7.0 and later) When the XDR agent examines portable executables (PEs) running on the endpoint as part of the enforced Malware Security Profile, the agent performs a certificate revocation (CRL) check. The CRL check ensures that the certificate used to sign a given PE is still considered valid by its Certificate Authority (CA), and has not been revoked. To validate the certificate, the XDR agent leverages Microsoft Windows APIs and triggers the operating system to fetch the specific Certificate Revocation List (CRL) from the internet. To complete the certificate revocation check, the endpoint needs HTTP access to a dynamic list of URLs, based on the PEs that are executed or scanned on the endpoint.Add a New Malware Security Profile

    1. If a system-wide proxy is defined for the endpoint (statically or using a PAC file), Microsoft Windows downloads the CRL lists through the proxy.

    2. If a specific proxy is defined for the Cortex XDR agent, and the endpoint has no access to the internet over HTTP, then Microsoft Windows will fail to download the CRL lists. As a result, the certificate revocation check will fail and the certificate will be considered valid by the Agent while creating a latency in executing PEs. If the XDR agent is running in an isolated environment that prohibits the successful completion of certificate revocation checks, the Palo Alto Networks Support team can provide a configuration file that will disable the revocation checks and avoid unnecessary latency in the execution time of PEs.

  5. Enable peer-to-peer (P2) content updates.

    By default, the Cortex XDR agent retrieves content updates from its peer Cortex XDR agents on the same subnet. To enable P2P, you must enable UDP and TCP over port 33221. You can change the port number or choose to download the content directly from the Cortex XDR sever in the Agent settings profile.

  6. Verify that you can access your Cortex XDR tenant.

    After you download and install the XDR agent software on your endpoints and configure your endpoint security policy, verify that the Cortex XDR agents can check in with Cortex XDR to receive the endpoint policy.

  7. If you use SSL decryption and experience difficulty in connecting the Cortex XDR agent to the server, we recommend that you add the FQDNs required for access to your SSL Decryption Exclusion list.

    With Cortex XDR agent 8.3 where Certificate Enforcement is enabled, you must add the the FQDNs required for access to your SSL Decryption Exclusion list.

    In PAN-OS 8.0 and later releases, you can configure the list in DeviceCertificate ManagementSSL Decryption Exclusion.