For the complete documentation index, see llms.txt. This page is also available as Markdown.

Zscaler Private Access

Managed just-in-time access to Zscaler Private Access application segments

This page documents how to install P0 for a Zscaler Private Access (ZPA) tenant so you can manage just-in-time access to ZPA application segments. Users request a segment, and P0 adds an access policy rule that allows them to reach it. P0 deletes the rule when access ends.

The Zscaler Private Access integration is in preview. Functionality and configuration may change.

Before you begin

Your ZPA tenant must use ZIdentity and OneAPI. You need administrator access to the ZPA admin console and the ZIdentity admin console.

P0 matches each requester to ZPA by email address. Your tenant needs a user identity provider that provisions users with SCIM, and each requester's SCIM primaryemail attribute must match their P0 identity.

Gather these values for each tenant:

  • ZIdentity vanity domain: the full URL of your ZIdentity sign-in domain, such as https://yourcompany.zslogin.net.

  • Customer ID: shown on the Account page of the ZPA admin console.

How the installation is organized

The integration has two components, and each one uses its own ZIdentity API client:

  • Zscaler Private Access network access lets P0 read your application segments. Install it first.

  • Zscaler Private Access policy management lets P0 add and delete access policy rules. You install it on a tenant that already has network access.

Create a role and API client for network access

  1. Create a role in ZPA. In the ZPA admin console, go to Configuration & Control > Administration Control > Roles. Create a role named P0 Security Network Access Integration. Give it Privileged Remote Access, with every permission set to Read Only.

  2. Create an API client in ZIdentity. In the ZIdentity admin console, go to Administration > Integration > API Clients and create a client.

  3. Fill in the Client tab. Name the client P0 Security Network Access Integration. Set Access Token Validity to at least 5 minutes and set Status to Enabled.

  4. Generate a secret. Choose Secret for client authentication, then click Add. Copy the secret value. You enter it in P0 later.

  5. Select the role. On the Resources tab, select P0 Security Network Access Integration as a scope. If the role does not appear, wait a few minutes and refresh.

  6. Save the client. On the Metadata tab, enter your details as the owner, then click Save. Copy the client ID, which you enter in P0 with the secret.

Install network access in P0

  1. Open the P0 dashboard at p0.app and log in to your organization.

  2. In the sidebar, click Integrations. Under Resources, click Zscaler Private Access.

  3. Select the Zscaler Private Access network access component and click Add customer.

  4. In the Customer name field, enter a name for this tenant, then click Next. Requesters use this name to choose the tenant from the P0 CLI.

  5. Enter the ZIdentity vanity domain and Customer ID you gathered earlier, and the Client ID and Client secret of the API client.

  6. Click Next to finish.

Create a role and API client for policy management

Repeat the steps in Create a role and API client for network access, with these changes:

  • Name both the role and the API client P0 Security Access Management Integration.

  • Give the role Policy Management, with only the Policies permission set to Full access.

Install policy management in P0

  1. On the Zscaler Private Access integration page, select the Zscaler Private Access policy management component and click Add customer.

  2. Under Customer name, select the tenant you installed for network access, then click Next.

  3. Enter the Client ID and Client secret of the policy management API client.

  4. Click Next to finish.

What P0 grants

P0 grants access to one ZPA application segment per request. When a request is approved, P0 adds an Allow rule to your access policy. The rule matches the requested segment and the requester's primaryemail, and its name starts with p0_.

When access expires, or when a user relinquishes it early, P0 deletes the rule. P0 doesn't change other rules in your access policy.

Limitations

  • P0 grants access to application segments only.

  • Each requester must be provisioned to ZPA through SCIM, with a primaryemail that matches their P0 identity.

Last updated