GlobalProtect (Palo Alto) Integration

GlobalProtect (Palo Alto) Integration


This page explains how to forward traffic from your Palo Alto gateways to Lumia. If you're looking for instructions on installing the Lumia Agent together with GlobalProtect on the same endpoint, see here.
Configuring your Palo Alto VPN to work with Lumia is simple. Follow the steps below, and feel free to contact us at support@lumia.security if you have any questions.

Prerequisites:

  1. Palo Alto VPN is managed by Panorama (if you are using Strata Cloud Manager instead, see here).
  2. You have shared your gateway IP addresses with Lumia. This allows us to restrict access to your tenant to traffic coming only from your organization.
  3. GlobalProtect is deployed and enforced on all endpoints subject to Lumia governance.
  4. SSL Inspection is already configured (active inspection is not required; the certificate infrastructure only needs to be in place).
  5. Palo Alto must not be configured with Proxy Auto-Configuration (PAC) files.
If one of the above prerequisites are not met, please contact us before proceeding.

Step 1: Sign Lumia’s CA with your Palo Alto CA

Prerequisites: For this step, you should have received the lumia.csr (Certificate Signing Request) file from Lumia. If you have not received it, please contact us.
We recommend ensuring that a revocation mechanism is in place before signing certificates (see here).
To help govern employees’ use of AI, Lumia needs to decrypt SSL traffic that is managed by your Palo Alto VPN. To do this, your Palo Alto system will sign a certificate that Lumia will use. In this step, you will sign Lumia’s CA certificate using your Palo Alto Forward Trust CA.
  • Export your Palo Alto Forward Trust CA certificate, including its private key, so you can use it to sign Lumia’s CA.
    Never share this file with anyone (including Lumia), and delete it immediately after completing this step.
    To export the certificate:
    • Go to DEVICE → Certificate Management → Certificates
    • Identify the certificate marked with Forward Trust Certificate in the USAGE column
    • Click Export Certificate
    notion image
  • Check Export Private Key, choose a passphrase for the exported file, click OK. The file will be downloaded to your Downloads folder with a name such as palo.pem. Never share the exported PEM file or its passphrase with anyone.
notion image
  • Open a terminal or command prompt.
  • Create a ca.ext certificate extension configuration file that defines the permissions granted to the Lumia certificate (add any additional extension your organization may require):
basicConstraints = critical, CA:true, pathlen:0 keyUsage = critical, keyCertSign, cRLSign subjectKeyIdentifier = hash authorityKeyIdentifier = keyid:always,issuer
  • Place lumia.csr, ca.ext, and palo.pem in the same directory, then run the following command to sign (-days 365 defines the number of days the certificate will remain valid and can be set to any value):
openssl x509 -req -in lumia.csr -CA palo.pem -CAkey palo.pem -out lumia.crt -days 365 -sha256 -extfile ca.ext
  • You will be prompted to enter the private key’s password (the password you provided when exporting the private key in the previous steps).
  • If the process completes successfully, a file named lumia.crt will be created. Please share this file with Lumia at support@lumia.security to proceed with the integration.

Step 2: Enable SSL inspection for Lumia’s proxy

Prerequisites: For this step, you should have received your Lumia Proxy FQDN from Lumia (it will look similar to 85fca78ac...6abccad95ee3dc.proxy.us.lumiasecurity.com). If you do not have this, please contact us.
In this step, you will instruct your Palo Alto to encrypt traffic to Lumia’s proxy. This will ensure the traffic is both secured and identifiable.
  • Go to POLICIES → Decryption → Pre Rules, then click Add.
notion image
  • In the General tab:
    • Set Name to decrypt-lumia-proxy.
  • In the Source tab:
    • Select Any for SOURCE ZONE.
    notion image
  • In the Destination tab:
    • Select Any for DESTINATION ZONE.
    • Click Add under DESTINATION ADDRESS.
    • Click New Address.
    notion image
    • In the Address window:
      • Set Name to Lumia Proxy.
      • Set Type to FQDN.
      • Set FQDN to your Lumia Proxy FQDN.
      • Click OK.
      notion image
  • In the Options tab:
    • Set Action to Decrypt.
    notion image
  • Click OK to create the decryption rule.

Step 3: Configure a Header Insertion Profile for Lumia’s proxy

In this step, you will create a Header Insertion Profile for your Palo Alto to send encrypted user identification together with the traffic it forwards to Lumia.
  • Go to OBJECTS → Security Profiles → URL Filtering, then click Add.
notion image
  • Set Name to Add X-Authenticated-User.
  • Select the HTTP Header Insertion, then click Add.
notion image
  • In the HTTP Header Insertion window:
    • Set Type to Custom.
    • Set Name to X-Authenticated-User (skip this block if already exists.)
    • Click Add Domains.
    • Set * to catch all domains.
    • Click Add Headers.
    notion image
    • In the Headers window:
      • Set Header to X-Authenticated-User
      • Set Value to ($user)@($domain)
      notion image
  • Click OK three times to create the URL Filtering Rule.

Step 4: Assign the Header Insertion Profile to the Security Policy

In this step, you will configure your Palo Alto to use the Header Insertion Profile when forwarding traffic to the Lumia proxy.
  • Go to POLICIES → Security → Pre Rules, then click Add.
notion image
  • In the General tab:
    • Set Name to Allow access to Lumia Proxy.
  • In the Source tab:
    • For SOURCE ZONE, select the zone used by your VPN users. If your are not sure, it is ok also acceptable to select Any.
    notion image
  • In the Destination tab:
    • Set DESTINATION ZONE to Any.
    • Set DESTINATION ADDRESS to the Lumia Proxy Address object you created in Step 2.
    notion image
  • In the Actions tab:
    • Set Action to Allow.
    • Set Profiles Type to Profiles.
    • Set URL Filtering to the Add X-Authenticated-User profile you created in Step 3.
    notion image
  • Click OK to create the security policy rule.
  • Security rules are evaluated from top to bottom, so ensure the newly added rule is matched before any broader rules. If you are unsure, and because the rule is very specific, you can move it to the top of the list by clicking Move Top.
notion image

Step 5: Push Lumia’s PAC settings via GlobalProtect

Prerequisites: For this step, you should have received your Lumia PAC URL from Lumia (it will look similar to https://pac.us.lumiasecurity.com/pac/XPDG3ZHNKSU...3QU7F3NGKBKLJTDO23CQN5L5OTM/proxy.pac). If you do not have this, please contact us.
In this step, you will configure GlobalProtect users to use Lumia’s PAC URL.
  • Go to NETWORK → GlobalProtect → Portal, then click the relevant GlobalProtect profile.
notion image
  • Click the Agent tab, then click the relevant Agent Config profile.
notion image
  • In the Configs window:
    • Select the App tab.
    • In the App Configuration pane, look for Proxy Auto-Configuration (PAC) File URL, then set it to the Lumia PAC URL.
notion image
  • Click OK two times to update the GlobalProtect to push Lumia’s PAC.

Step 6: Commit and test

Once everything is configured, commit and push the changes you’ve made.
You can use https://check.lumiasecurity.com to make sure everything is working.
Â