--- name: configuring-zscaler-private-access-for-ztna-3b210c686d10 description: 'Configuring Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring access policies based on user identity and device posture, and integrating with IdPs. ' domain: cybersecurity subdomain: zero-trust-architecture tags: - zscaler - zpa - ztna - zero-trust - app-connector - access-policy - sase version: '1.0' author: Krishna Kumar (xalgord) license: Apache-2.0 nist_csf: - PR.AA-01 - PR.AA-05 - PR.IR-01 - GV.PO-01 --- # Configuring Zscaler Private Access for ZTNA ## When to Use - When replacing traditional VPN concentrators with application-level zero trust access - When providing remote users secure access to internal applications without network-level connectivity - When implementing least-privilege access where users only see authorized applications - When needing to make internal applications invisible to unauthorized users and the internet - When integrating ZTNA with existing SASE architecture using Zscaler Internet Access (ZIA) **Do not use** for applications requiring raw UDP access (ZPA primarily supports TCP), for providing full network-level access equivalent to site-to-site VPN (use ZPA AppProtection or branch connector instead), or when the organization requires on-premises-only access control without cloud dependency. ## Common Misconfigurations & Verification - **App segment Bypass Type not "Never":** if a segment is set to Bypass, or its domain overlaps a ZIA/forwarding-profile bypass, the Client Connector sends traffic straight to the internet/origin instead of through ZPA. Confirm `Bypass Type: Never` with no conflicting bypass. - **Internal app still routable off-ZPA:** ZPA only hides apps from clients using the connector. If the app server keeps a public IP, or the corporate LAN/legacy VPN can still reach `hr-portal.internal.corp` directly, the dark-cloud guarantee is void. Firewall the origin to accept only App Connector source IPs. - **Access policy without device posture:** an ALLOW rule keyed only on user group ignores the Device Posture Profile, so a personal device passes. Bind each rule to a posture profile (e.g., CrowdStrike ZTA score >= 60) and ensure a final **default-deny** rule exists and logs. - **Overly broad wildcard segments:** `*.internal.corp` exposes far more than intended; scope segments tightly. Verify: off the connector, `nslookup`/`curl` the app FQDN and its IP directly, neither must resolve or connect. In the Admin Portal check LSS/User Activity logs for `action="denied"` when a non-compliant device or unauthorized group attempts access, and confirm the default-deny rule is recording hits. ## Prerequisites - Zscaler Private Access subscription (Business or Transformation edition) - Identity provider configured: Okta, Microsoft Entra ID, Ping Identity, or SAML 2.0 IdP - App Connector VM requirements: Linux VM (CentOS 7/8, RHEL 7/8, Ubuntu 18.04+, Amazon Linux 2) with 2 vCPU, 4GB RAM minimum - Outbound connectivity from App Connector to ZPA cloud on port 443 (no inbound ports required) - DNS resolution from App Connector to internal application FQDNs - Zscaler Client Connector deployed on user endpoints ## Workflow ### Step 1: Deploy App Connectors in Application Network App Connectors establish outbound-only tunnels to the ZPA cloud, providing access to internal applications. ```bash # Download and install App Connector on Linux VM # Obtain provisioning key from ZPA Admin Portal > Administration > App Connectors # For RHEL/CentOS sudo yum install -y https://yum.private.zscaler.com/yum/el7/zpa-connector-latest.rpm # For Ubuntu/Debian curl -sS https://dist.private.zscaler.com/apt/pubkey.gpg | sudo apt-key add - echo "deb https://dist.private.zscaler.com/apt stable main" | sudo tee /etc/apt/sources.list.d/zpa.list sudo apt update && sudo apt install -y zpa-connector # Configure the connector with provisioning key sudo /opt/zscaler/bin/zpa-connector configure \ --provision-key "PROVISIONING_KEY_FROM_PORTAL" # Start the connector service sudo systemctl enable zpa-connector sudo systemctl start zpa-connector # Verify connector status sudo systemctl status zpa-connector sudo /opt/zscaler/bin/zpa-connector status # Deploy second connector for HA (minimum 2 per site) # Repeat on second VM with same App Connector Group provisioning key ``` ### Step 2: Define Server Groups and Application Segments Map internal applications to server groups and create application segments. ```text ZPA Admin Portal Configuration: 1. Server Groups: Navigate to: Administration > App Connectors > Server Groups - Name: "DC-East-Servers" - App Connector Group: "DC-East-Connectors" - Servers: - hr-portal.internal.corp (10.1.1.50, TCP 443) - finance-app.internal.corp (10.1.1.51, TCP 443) - git.internal.corp (10.1.2.10, TCP 22, 443) 2. Application Segments: Navigate to: Resources > Application Segments > Add Application Segment - Name: "HR Applications" - Domain/URL: hr-portal.internal.corp - TCP Ports: 443 - Server Group: DC-East-Servers - Health Reporting: Continuous - Bypass Type: Never (force all traffic through ZPA) - Name: "Engineering Tools" - Domain/URL: git.internal.corp, ci.internal.corp, wiki.internal.corp - TCP Ports: 22, 80, 443 - Server Group: DC-East-Servers - Segment Group: "Engineering Segment Group" ``` ### Step 3: Configure Access Policies Define who can access which application segments based on identity and device posture. ```text ZPA Admin Portal > Policies > Access Policy: Rule 1: HR Team Access - Name: "HR Portal Access" - Action: ALLOW - Criteria: - User Groups: "HR-Department" (from IdP) - Application Segment: "HR Applications" - Device Posture Profile: "Corporate Managed Device" - Client Type: Zscaler Client Connector - Conditions: - SAML Attribute: department = "Human Resources" - Device Trust Level: "HIGH" (CrowdStrike ZTA score > 70) Rule 2: Engineering Access - Name: "Engineering Tools Access" - Action: ALLOW - Criteria: - User Groups: "Engineering-Team", "DevOps-Team" - Application Segment: "Engineering Tools" - Device Posture Profile: "Developer Workstation" - Conditions: - Machine Group: "Engineering Laptops" Rule 3: Contractor Limited Access - Name: "Contractor Wiki Access" - Action: ALLOW - Criteria: - User Groups: "External-Contractors" - Application Segment: "Wiki Only" - Client Type: Zscaler Client Connector OR Browser Access - Conditions: - Time Window: Mon-Fri 08:00-18:00 EST Rule 4: Default Deny - Name: "Block All Other Access" - Action: DENY - Criteria: All Users, All Applications - Log: Enabled ``` ### Step 4: Configure Device Posture Profiles Integrate device posture signals from endpoint security tools. ```text ZPA Admin Portal > Administration > Device Posture: Profile 1: Corporate Managed Device - CrowdStrike Falcon: Running, ZTA Score >= 60 - OS: Windows 10 21H2+, macOS 13+, Ubuntu 22.04+ - Disk Encryption: Enabled (BitLocker/FileVault) - Firewall: Enabled - Screen Lock: Enabled Profile 2: Developer Workstation - Inherits: Corporate Managed Device - CrowdStrike Falcon: ZTA Score >= 70 - Patch Level: Within 30 days of latest - Certificate: Valid corporate certificate present Profile 3: BYOD Device - OS: Latest minus 1 version - Browser: Chrome 120+ or Edge 120+ - Antivirus: Any recognized AV running ``` ### Step 5: Enable Browser Access for Clientless ZTNA Configure Browser Access for users without Zscaler Client Connector installed. ```text ZPA Admin Portal > Resources > Application Segments: For "HR Applications" segment: - Enable Browser Access: Yes - Browser Access Type: HTTPS - Custom Domain: hr.access.company.com - Certificate: Upload TLS certificate for custom domain - Authentication: SAML via corporate IdP - Session Timeout: 4 hours - Clipboard Control: Disabled for sensitive apps - File Upload/Download: Restricted For Browser Access Portal: - Portal URL: access.company.com - IdP: Microsoft Entra ID (SAML 2.0) - MFA: Required - Applications shown: Only authorized per user group ``` ### Step 6: Configure Logging and Monitoring Set up log streaming for SIEM integration and continuous monitoring. ```text ZPA Admin Portal > Administration > Log Streaming Service: Log Receiver Configuration: - Name: "Splunk-SIEM" - Type: Splunk (HEC) - Destination: https://splunk-hec.company.com:8088 - HEC Token: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" - Log Types: - User Activity: Enabled - App Connector Status: Enabled - Audit Logs: Enabled - Browser Access: Enabled # Splunk search for ZPA access anomalies index=zscaler_zpa sourcetype=zpa:useractivity | where action="denied" | stats count by user, application, policy_name | where count > 10 | sort -count ``` ## Key Concepts | Term | Definition | |------|------------| | App Connector | Lightweight Linux service that creates outbound-only encrypted tunnels from internal networks to ZPA cloud, providing access to applications without inbound ports | | Application Segment | Logical grouping of internal applications defined by FQDN/IP and ports, mapped to server groups for access policy enforcement | | Server Group | Collection of application servers associated with App Connector groups that can serve requests for application segments | | Access Policy | Rules defining which users/groups can access which application segments under what conditions (device posture, time, location) | | Zscaler Client Connector | Endpoint agent installed on user devices that routes traffic to ZPA cloud for policy enforcement and application access | | Browser Access | Clientless ZTNA option allowing application access through a web browser without requiring Zscaler Client Connector installation | ## Tools & Systems - **Zscaler Private Access (ZPA)**: Cloud-native ZTNA platform replacing VPN with identity-based application access - **Zscaler Client Connector**: Cross-platform endpoint agent routing traffic through ZPA for policy enforcement - **ZPA App Connector**: Outbound-only tunnel endpoint deployed in application networks - **ZPA Admin Portal**: Web-based management console for policy, segment, and connector configuration - **ZPA Log Streaming Service (LSS)**: Real-time log export to SIEM platforms (Splunk, Sentinel, QRadar) - **CrowdStrike ZTA Integration**: Device posture scoring for conditional access policy enforcement ## Common Scenarios ### Scenario: Migrating 500-User Organization from Cisco AnyConnect VPN to ZPA **Context**: A financial services firm with 500 employees uses Cisco AnyConnect for remote access. VPN split-tunnel configuration creates security gaps, and full-tunnel mode causes performance issues. The firm needs application-level access control for SOX compliance. **Approach**: 1. Deploy 4 App Connectors (2 per data center) with HA configuration 2. Define application segments for 20 internal applications grouped by business function 3. Configure access policies mapping AD groups to application segments with device posture requirements 4. Integrate CrowdStrike ZTA scores as device posture input (minimum score 60 for standard, 80 for financial apps) 5. Enable Browser Access for contractors accessing the vendor portal 6. Configure LSS to stream access logs to Splunk for SOX audit trail 7. Run parallel operation for 3 weeks: VPN and ZPA side by side 8. Phase out VPN connections after validating all application access through ZPA **Pitfalls**: App Connector DNS must resolve all internal FQDNs used in application segments. Wildcard domain segments can cause performance issues if too broad. Browser Access does not support all web application frameworks (WebSocket-heavy apps may require Client Connector). CrowdStrike ZTA integration requires Falcon sensor deployment on all endpoints before enforcing posture policies. ## Output Format ``` ZPA ZTNA Deployment Report ================================================== Organization: FinanceCorp Deployment Date: 2026-02-23 INFRASTRUCTURE: App Connectors: 4 (2x DC-East, 2x DC-West) Connector Status: All healthy Connector Version: 24.1.2 APPLICATION COVERAGE: Application Segments: 20 Total Applications: 45 Server Groups: 4 Segment Groups: 6 ACCESS POLICIES: Total Rules: 12 Allow Rules: 11 Deny Rules: 1 (default deny) Device Posture Profiles: 3 USER ACCESS (last 30 days): Active Users: 487 / 500 Total Sessions: 124,567 Allowed Sessions: 123,890 (99.5%) Denied Sessions: 677 (0.5%) Browser Access Sessions: 2,341 VPN MIGRATION: Users migrated to ZPA: 487 / 500 VPN decommission date: 2026-03-15 ``` --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/zero-trust-architecture/configuring-zscaler-private-access-for-ztna/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/zero-trust-architecture/configuring-zscaler-private-access-for-ztna/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Operations Roles: DevOps / SRE, IT Operations Specialties: API Tools: Zscaler Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 1833c59bc20498d728a71ebc92bd26f67a57e1ce19fcb12b253935c86351e8c4