Skip to content
Connection Guide

Connect Zscaler Private Access Without Breaking the Audit Trail

Use this guide to connect Zscaler Private Access or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryZtna
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Zscaler Private Access and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated ZPA API key bound to the predefined ZPA Read Only Administrator role and capture base_url, customer_id, client_id, and client_secret.
  2. 2
    Supply microtenant_id only when the tenant uses microtenants or the selected API surface requires it.
  3. 3
    Enable Log Streaming Service only if Aurora needs audit, user-activity, or user-status enrichment; the core runtime works from management-plane reads alone.
  4. 4
    Validate the login-controller token exchange against the target cloud before enabling scheduled sync for a customer tenant.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.