# Prisma Access — Business VPN & Zero Trust Access

Prisma Access by Palo Alto Networks, Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-19. Provenance: provenance unknown; sovereignty: 2 of 6 dimensions proven.

- Vendor: Palo Alto Networks, Inc. (https://www.paloaltonetworks.com)
- Category: [Business VPN & Zero Trust Access](https://whats-best.ai/software/business-vpn.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/business-vpn/prisma-access
- Alternatives: https://whats-best.ai/software/business-vpn/prisma-access/alternatives ([markdown](https://whats-best.ai/software/business-vpn/prisma-access/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-19 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Palo Alto Networks, Inc.
- Headquarters: Incorporated in the United States [S2]
- Data hosting: Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

Prisma Access is Palo Alto Networks' managed business VPN and zero-trust access service. Scores peak on visibility and audit at 6-7, on a field-level log schema: who authenticated, with which multi-factor vendor and factor, against which rule, with microsecond timestamps, exportable in Syslog, CEF, HTTPS and LEEF, with an on-premise collector option. The genuine split is access and connectivity, 4 to 7: the rationales repeatedly flag the same gaps — client platforms, gateway locations, split-tunnelling behaviour — but weigh them differently; the operations manager, at 4, could not judge what a contractor installs, while higher scores credited documented GlobalProtect agent, agentless and IPsec remote-network access plus bring-your-own-IP, IPv6 and a FedRAMP environment. Sovereignty sits at 3-4: the contracting entity is US-based, Santa Clara, California; transfers rest on standard contractual clauses and the EU-U.S. Data Privacy Framework; we found no public information on EU hosting or where logs and identities sit. A leaver gap recurs: removing a user from the Okta group needs a manual push or the user retains access; no price appears on any captured page, only named licences.

**Speaks for it:**
- Log schema documented field by field — who authenticated, with which multi-factor vendor and factor, against which rule, at microsecond timestamps
- Logs exportable in Syslog, CEF, HTTPS and LEEF, with an on-premise log collector as an alternative location
- Broad documented access: GlobalProtect agent, agentless access, IPsec remote networks with IKE, BGP, NAT-T and DPD, bring-your-own-IP, IPv6 and a FedRAMP environment
- Okta SCIM provisioning over OAuth 2.0, with multi-factor events logged per vendor and group-based policy fed by device-posture and quarantined-device data
- Coordinated vulnerability disclosure with a PSIRT contact and PGP key, published security advisories, and a Trust 360 programme with an information security measures document

**Held against it:**
- Removing a user from the Okta group does not automatically revoke access — a manual push is required or the user retains access
- We found no public information on log retention periods, an administrator configuration audit log, or a way to view and end active sessions
- The contracting entity is US-based in Santa Clara, California, and we found no public information on EU hosting or where the control plane, identities and logs are stored
- Penetration tests and Statements of Applicability are available only under NDA, and compensation for security reports is expressly prohibited
- The documented path to private applications requires a next-generation firewall deployed at headquarters or the data centre

**Best for:**
- You need field-level, exportable connection and authentication logs to feed a SIEM or audit workflow
- Your identity provider is Okta and your offboarding process can absorb a documented manual-push step
- You already run Palo Alto next-generation firewalls at your data centre and want documented IPsec remote networks and service connections on top of them
- You are a non-EU buyer for whom a US contracting entity with standard contractual clauses and DPF adherence is an acceptable transfer basis

**Avoid if:**
- You need to evidence an EU-resident chain for a GDPR- or NIS2-scoped deployment — we found no public information on EU hosting, an EU contracting entity, or where the control plane, identities and logs are stored
- Your leaver offboarding must be fully automatic — the documentation states Okta removals keep access until an administrator manually pushes the change
- You have no next-generation firewall at headquarters or your data centre — ask the vendor: the public pages we read do not show it
- You must hand an auditor public compliance reports — penetration tests and Statements of Applicability are available only under NDA

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The IT Lead | The DevOps Engineer | The MSP Technician | The Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Access model & connectivity | 3/5 | 3/5 | 3/5 | 2/5 | 3.5/5 | 3.5/5 |
| Identity, access policy & device posture | 2.5/5 | 3/5 | 3/5 | 3/5 | 2.5/5 | 3/5 |
| Logs, audit trail & incident response | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 3.5/5 |
| Deployment, API & administration | 2.5/5 | 2.5/5 | 2/5 | 2/5 | 2.5/5 | 2.5/5 |
| Architecture, reliability & security assurance | 2/5 | 3/5 | 2/5 | 2/5 | 2.5/5 | 2.5/5 |
| European sovereignty | 1.5/5 | 2/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **3/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** |

### The judges

- **The IT Lead** (v1.0): Head of a three-person IT team at a 140-person mechanical engineering firm with two plants and a sales office in Vienna. The VPN still runs on the firewall, and every update of it is a weekend. Wants a client that installs through Intune and connects on its own, sign-in with Microsoft Entra so a leaver loses access the same day, the ERP and the file server reachable without opening the whole network, a fixed IP for the supplier portal, and a price per user that survives the next budget round.
- **The DevOps Engineer** (v1.0): Platform engineer at a sixty-person software company with servers at Hetzner, a Kubernetes cluster on AWS and a bastion host everyone shares a key for. Wants a mesh that reaches every server and cluster without inbound ports, access policies kept in Git and applied with Terraform, SSH access tied to the identity provider, connectors that run as containers, and a published architecture that says what the vendor's relays can see.
- **The MSP Technician** (v1.0): Senior technician at an IT service provider in Hamburg that looks after thirty clients, from tax advisers to a dental chain. Each client has its own remote access, set up by whoever was on site that year. Wants one console with a tenant per client, gateways and users added in minutes, access logs a client can be shown after an incident, billing per tenant, and prices per user that can be quoted without calling the vendor first.
- **The Operations Manager** (v1.0): Runs operations at a fifty-person consultancy where a third of the work is done by freelancers on their own laptops and the rest of the team travels to client sites. Has no IT department, only an external provider billed by the hour. Wants each freelancer to reach one project system and nothing else, access that ends with the contract, a setup a non-specialist can follow, and no call to the helpdesk from a hotel lobby.
- **The Information Security Officer** (v1.0): Information security officer at a regional energy supplier that falls under NIS2 and was asked by its auditor who could reach the control systems last year. Wants access granted per resource, not per network, device checks before a connection, every access and admin change in a log that reaches the SIEM, an independent audit of the product, and the identities and logs kept in Europe by a vendor whose subprocessors are listed.
- **The Skeptic** (v1.0): Has seen "zero trust" on a VPN that still drops every user into the whole office network, "no logs" from a vendor that keeps every connection for a year, and a remote access tool that locked out the whole company when its own control plane went down. Asks who can see the traffic and the metadata, what keeps working when the vendor is offline, whether the audit was published or only announced — and whether the network could be moved to a self-hosted server.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 2 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S2] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S2] |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Cbpr prp certification: yes [S2]
- DPF frameworks: EU-U.S. DPF · Swiss-U.S. DPF · UK Extension to EU-U.S. DPF [S2]
- DPF ftc enforcement: FTC [S2]
- Information security measures: Information Security Measures document covering technical and organizational measures [S12]
- International transfers sccs: adequacy decisions · standard contractual clauses [S2]
- Operational resilience program: Global Operational Resilience Program protecting data integrity and continuity of operations [S12]
- Opt out targeted ads: yes [S2]
- Security advisories: Security Advisories page with timely vulnerability information [S12]
- Security assurance policy: Security Assurance and Vulnerability Disclosure Policy document [S12]
- Security measures: yes [S2]
- Security report requests: Security Compliance Reports available under NDA including penetration tests and Statements of Applicability [S12]
- Supply chain security: Palo Alto Networks Supply Chain Security program [S12]
- Trust360 program: Trust 360 Program — focal point for evaluating security controls; Trust 360 white paper encompasses security, compliance, and privacy controls [S12]

**Data**
- Analytics google: Google Analytics [S2]
- Audio retention embeddings: as long as necessary, then un-indexed and overwritten [S2]
- Duplicate detection: flags whether log data is available in multiple locations (Logging Service and on-premise log collector) [S8]
- Inferred information: yes [S2]
- Log export flag: flags logs exported from the firewall via log export function [S8]
- No biometric voiceprints: no [S2]
- No emotion recognition: no [S2]
- Payment third party: yes · no [S2]
- Repeat count field: aggregates sessions with same Source IP, Destination IP, Application, and Content/Threat Type in summary interval [S8]
- Retention audio 180 days: raw call audio and video files · 180 [S2]
- Retention principles: purpose limitation plus legal obligations and legitimate business interests [S2]
- Retention transcripts 180 days: full-text transcripts · 180 [S2]
- Tenant ID field: customer_id · Cortex Data Lake Tenant ID [S8]
- Timestamp fields: log_time (time received, microseconds since Unix epoch) · time_generated (firewall data plane, microseconds since Unix epoch) · time_generated_high_res (millisecond granularity, YYYY-MM-DDTHH:MM:SS[.DDDDDD]Z format) [S8]

**Integrations**
- Oauth token endpoint: https://auth.apps.paloaltonetworks.com/am/oauth2/access_token [S6]
- SCIM base URL: https://api.sase.paloaltonetworks.com/iam/v1/scim [S6]
- SCIM provisioning actions: Import New Users · Push New Users · Push Profile Updates · Push Groups · Import Groups [S6]
- SCIM unique identifier: userName [S6]
- Supported formats: Syslog · CEF · EMAIL · HTTPS · LEEF [S8]

**Legal**
- Copyright holder: 2026 Palo Alto Networks [S12]
- DPA reference: yes [S2]
- Entity copyright: 2026 · Palo Alto Networks [S1]
- GDPR applicability: EU GDPR 2016/679 · UK GDPR · yes [S2]
- Identity verification: yes [S2]
- Privacy contact email: privacy@paloaltonetworks.com [S2]
- Privacy effective date: 2026-08-27 [S2]
- Privacy mailing address: Palo Alto Networks, Inc. · 3000 Tannery Way, Santa Clara, CA 95054, USA [S2]
- Rights exercise channels: Individual Rights Form · contact methods on page [S2]
- Social media sources: Facebook · Google · Twitter [S2]
- Subprocessors list reference: yes [S2]
- UK swiss DPA contacts: ICO · FDPIC [S2]

**Product**
- Access point name field: access_point_name references PGW/GGSN in mobile network [S7]
- Advanced deployments scope: Section covers advanced routing and networking deployments for Prisma Access and how to configure them [S9]
- Agent availability: beta · on_request_via_account_team [S3]
- Agentless access: yes [S9]
- AI disclaimer: may contain errors; verify before applying changes · yes [S3]
- AI observability platform: AI-driven observability platform [S1]
- Analysis phases: Context gathering · Evidence gathering and correlation · Root cause determination · Remediation generation [S3]
- App acceleration: yes [S9]
- Auth factor field: auth_factor_num distinguishes primary authentication (1) vs additional factors (2, 3) [S8]
- Auth log fields: page defines authentication log schema fields including auth_description, auth_event_name.value, auth_factor_num, auth_policy, auth_proto, auth_server_profile, authenticated_user_info (domain/name/uuid), client_type, mfa_auth_id, mfa_vendo… [S8]
- Auth logs condition: firewall must be configured with authentication policies for auth logs to appear [S8]
- Auth logs source: Auth logs record authentication events seen by the next-generation firewall when users access resources controlled by authentication policy rules [S8]
- Automation modes: natural language queries in Strata Copilot · Prisma Access incident codes [S3]
- Byoip: yes [S9]
- Clean pipe: yes [S9]
- Cli command: Feature is enabled via CLI: set deviceconfig setting preserve-prenat-feature yes (disable with no) [S10]
- Cloud security products: Cortex Cloud · Application Security · Cloud Posture Security · Cloud Runtime Security · Prisma Cloud [S1]
- Cloud vs onprem flag: distinguishes cloud-based vs on-premise firewall log generation [S8]
- Colocate connect: yes [S9]
- Controller vs processor scope: Privacy Statement applies only when Palo Alto Networks acts as data controller; processor/service-provider processing is covered by the DPA and Trust Center [S2]
- Correlated alerts: four related portal clientless VPN auth alerts (success count dropped below baseline and timeout failures count exceeded above baseline, both all PA locations and per PA location) [S4]
- Country blocking: yes [S9]
- CRM automation uses: auto-draft follow-ups · CRM record updates · pseudonymized transcript indexing · semantic search [S2]
- Customer ID field: customer_id identifies the Cortex Data Lake instance that received the log record [S7]
- Data subject rights: access · portability · rectification · erasure · restriction · withdraw consent · object to legitimate-interest processing · lodge complaint with DPA [S2]
- Default sc can: Original ID Downstream is the default configuration on SC-CANs [S10]
- Device identification fields: log_source_id (Device SN; hidden for Prisma Access logs) · log_source_name (Device Name/hostname) · panorama_serial (Panorama SN associated with CDL) [S8]
- Disclosure channels: product vulnerability form · non-product vulnerability form · vulnerabilities affecting paloaltonetworks.com [S11]
- Disclosure embargo expectation: reporters must wait until notified the vulnerability is resolved before disclosing [S11]
- Doc update date: Page last updated Wed Sep 16 03:49:20 PDT 2026 [S7]
- Doc update date: 2026-11-13 [S9]
- Endpoints scanned daily: 480B [S1]
- Fedramp environment: yes [S9]
- Globalprotect flag: distinguishes cloud-based vs on-premise GlobalProtect log generation [S8]
- Gtp inner sessions traffic logs: Inner GTP sessions recorded via traffic logs with tunnel field value 1 [S7]
- Gtp log use: GTP logs identify start and end of GTP tunnels [S7]
- Gtp purpose: GTP defined by 3GPP to carry GPRS within cellular (3G and 4G) networks [S7]
- Identity data types: HIP data · IP-address-to-tag mappings · IP-address-to-user mappings · User-to-tag mappings · Quarantined devices [S5]
- Identity redistribution: Prisma Access shares GlobalProtect-discovered identity data across the environment and with on-premises devices at remote network or service connection sites [S5]
- Identity redistribution prerequisites: yes [S5]
- Identity redistribution SSL decryption limitation: yes [S5]
- Identity redistribution strata default enabled: yes [S5]
- Identity security products: Privileged Access Management · Identity and Access Management · Endpoint Privilege Manager · Identity Governance · Workforce Password Management · Agentic Identities · Secrets Management · Unified Secrets Governance · Application Credentia… [S1]
- Incident clear condition: cleared when average authentication timeouts are less than twice the baseline for 45 minutes [S4]
- Incident code: INC_PORTAL_CLIENTLESS_VPN_AUTH_TIMEOUT_FAILURES_COUNT_EXCEEDED_ABOVE_BASELINE_ALL_PA_LOCATIONS [S4]
- Incident code ecmp tunnel down: INC_RN_ECMP_TUNNEL_DOWN · One of the ECMP tunnels went down; ECMP tunnel state for all redundant paths, traffic distribution, DPD probe results, bandwidth and session distribution impact [S3]
- Incident code primary wan bgp down: INC_RN_PRIMARY_WAN_BGP_DOWN · Primary WAN BGP neighbor down; BGP neighbor state machine, hold and keepalive timer mismatches, MD5 authentication failures, route advertisement validation, prefix filtering and AS-path policy mismatches, rout… [S3]
- Incident code primary wan tunnel down: INC_RN_PRIMARY_WAN_TUNNEL_DOWN · Primary WAN tunnel down; tunnel establishment state, IKE negotiation traces, crypto profile comparison, SA rekey failures, primary/secondary tunnel failover [S3]
- Incident code site down: INC_RN_SITE_DOWN · Remote network site completely unreachable; IKE Phase 1 and Phase 2 negotiation state, proposal mismatches, PSK and certificate authentication failures, proxy-ID mismatches, NAT-T, DPD and tunnel-monitor probe status, CP… [S3]
- Incident gap filling window: 3 [S3]
- Incident raise condition: raised when average authentication timeouts are more than twice the baseline for 45 minutes [S4]
- Incident severity: Critical [S4]
- Incident synopsis: Portal authentication timeout failures are higher than twice the baseline for all Prisma Access locations. [S4]
- Ipsec troubleshooting agent: IPSec troubleshooting agent in Strata Cloud Manager, part of Network Security Agents included with Strata Copilot; automates diagnostics for Prisma Access remote network and service connection issues [S3]
- Ipv6 support: yes [S9]
- Is packet capture field: is_packet_capture indicates whether the session has a PCAP [S7]
- Is prisma branch field: is_prisma_branch: 1 = cloud-based firewall, 0 = on-premise firewall [S7]
- Is prisma mobile field: is_prisma_mobile: 1 = cloud-based GlobalProtect, 0 = on-premise GlobalProtect [S7]
- Location field: location · Prisma Access Location [S8]
- Log forwarding profile field: log_set · Log Setting [S8]
- Log source ID device sn: log_source_id is the generating firewall's serial number; not displayed for Prisma Access logs [S7]
- Management options: Prisma Access license · Strata Cloud Manager · Panorama [S9]
- Management platform: Strata Cloud Manager · Strata Cloud Manager Pro · Strata Cloud Manager [S3]
- Marketing uses targeted advertising: yes [S2]
- MFA fields: mfa_auth_id (unique ID across primary and multi-factor auth) · mfa_vendor (vendor providing additional factor authentication) [S8]
- MFA gateway context: Auth logs most frequently written when NGFW is configured as a Multi-Factor Authentication gateway [S8]

73 more facts on the canonical page: https://whats-best.ai/software/business-vpn/prisma-access

## Questions

### Is Prisma Access European?

Not determined: the vendor’s pages as captured do not say where Prisma Access is based. Its vendor, Palo Alto Networks, Inc., is incorporated in the United States, per [the vendor’s page captured 17 Nov 2026](https://whats-best.ai/evidence/25927).

### Where does Prisma Access store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

### Does Prisma Access have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

### What are the best alternatives to Prisma Access?

As of 19 Nov 2026, the panel rates [Defguard (3.5/5)](https://whats-best.ai/software/business-vpn/defguard), [Firezone (3.5/5)](https://whats-best.ai/software/business-vpn/firezone) and [Tailscale (3.5/5)](https://whats-best.ai/software/business-vpn/tailscale) highest among the other 19 Business VPN & Zero Trust Access products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [Defguard](https://whats-best.ai/software/business-vpn/defguard) (EU-Made, Poland). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Prisma Access alternatives](https://whats-best.ai/software/business-vpn/prisma-access/alternatives).

## What this page leaves out

- We found no public information on pricing on the pages we read (paloaltonetworks.com, paloaltonetworks.com/legal-notices/privacy, docs.paloaltonetworks.com/prisma-access/administration/prisma-access-advanced-deployments/troubleshoot-remote-network-ipsec-vpn-operational-health-agent, docs.paloaltonetworks.com/prisma-access/incidents-and-alerts/ai-powered-adem-incidents/incident-inc-portal-clientless-vpn-auth-timeout-failures-count-exceeded-above-baseline-all-pa-locations, docs.paloaltonetworks.com/prisma-access/administration/prisma-access-user-based-policy/identity-redistribution, docs.paloaltonetworks.com/common-services/identity-and-access-access-management/okta-scim-config and 6 more). If the vendor publishes it somewhere else, send us the page.
- 12 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown.

## Sources

- [S1] Vendor page: https://www.paloaltonetworks.com (checked 2026-11-17)
- [S2] Legal notice — found from the homepage: https://www.paloaltonetworks.com/legal-notices/privacy (checked 2026-11-17)
- [S3] Access model & connectivity — found from sitemap: https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-advanced-deployments/troubleshoot-remote-network-ipsec-vpn-operational-health-agent (checked 2026-11-17)
- [S4] Access model & connectivity — found from sitemap: https://docs.paloaltonetworks.com/prisma-access/incidents-and-alerts/ai-powered-adem-incidents/incident-inc-portal-clientless-vpn-auth-timeout-failures-count-exceeded-above-baseline-all-pa-locations (checked 2026-11-17)
- [S5] Identity, access policy & device posture — found from sitemap: https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-user-based-policy/identity-redistribution (checked 2026-11-17)
- [S6] Identity, access policy & device posture — found from sitemap: https://docs.paloaltonetworks.com/common-services/identity-and-access-access-management/okta-scim-config (checked 2026-11-17)
- [S7] Logs, audit trail & incident response — found from sitemap: https://docs.paloaltonetworks.com/strata-logging-service/log-reference/network-logs/network-tunnel-log (checked 2026-11-17)
- [S8] Logs, audit trail & incident response — found from sitemap: https://docs.paloaltonetworks.com/strata-logging-service/log-reference/network-logs/network-auth-log (checked 2026-11-17)
- [S9] Deployment, API & administration — found from sitemap: https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-advanced-deployments (checked 2026-11-17)
- [S10] Deployment, API & administration — found from sitemap: https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-advanced-deployments/service-connection-advanced-deployments/preserve-source-nat-for-service-connections-with-a-next-generation-firewall/preserve-source-nat-for-service-connections-with-a-next-generation-firewall-cloud-management (checked 2026-11-17)
- [S11] Architecture, reliability & security assurance — found from sitemap: https://www.paloaltonetworks.com/security-disclosure (checked 2026-11-17)
- [S12] Architecture, reliability & security assurance — found from sitemap: https://www.paloaltonetworks.com/legal-notices/trust-center/security (checked 2026-11-17)

---

Cite as: whats-best.ai, "Prisma Access — Business VPN & Zero Trust Access", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/business-vpn/prisma-access

Corrections: https://whats-best.ai/correct/1928?target=page
