Zscaler SSL Inspection on Mac: How to Check & Bypass per Domain
Check whether Zscaler Client Connector is decrypting HTTPS on your Mac, why killing ZCC fails under Tamper Protection, and how to bypass per domain or fix CLI CA trust.
SWG bar · Updated
To check whether Zscaler (ZIA / Zscaler Client Connector) is decrypting HTTPS traffic on your Mac, open SWG bar → Overview (or run swgbar overview) and look for a Domain interception ratio above 0% with a Zscaler Root CA or corporate intermediate CA listed under MITM certificates. To bypass Zscaler SSL inspection for a single broken hostname on an authorized Mac, open SWG bar → Domains, select the hostname, and enable Bypass SWG (or run swgbar bypass enable <domain>).
Most online guides for bypassing Zscaler assume you have login access to the Zscaler Admin Portal (ZIA). On a company MacBook managed via Jamf, Kandji, or Intune, developers and employees rarely have portal access—yet Zscaler’s Z-Tunnel 2.0 (NetworkExtension / utun tunnel) and Zscaler Root CA routinely break certificate-pinned apps, Homebrew, npm, git, Python, Docker, Claude Code, and Cursor.
1. Check if Zscaler is actively inspecting HTTPS on your Mac
Because MDM pre-installs and trusts the Zscaler Root CA in macOS Keychain, Safari and Chrome show a normal padlock even while Zscaler performs HTTPS break-and-inspect. Verify per-domain decryption using either method:
- Continuous check with SWG bar: Install SWG bar (macOS 14+ Apple silicon, 14-use-day free trial) and visit the target sites. Open SWG bar → Domains or Certificates—or run
swgbar probe <domain>—to see whether the domain is Confirmed intercepted byZscaler Root CA(or your company’s Zscaler intermediate CA) vs. passing through with a Public trust path. - Spot-check one domain in Terminal:
openssl s_client -connect api.github.com:443 -servername api.github.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject
If issuer= shows Zscaler or your organization’s custom Zscaler intermediate CA instead of a public CA (such as DigiCert, Let’s Encrypt, or Google Trust Services), Zscaler SSL inspection is active for that hostname. See Verify TLS certificates with OpenSSL and security verify-cert to cross-check SHA-256 fingerprints.
2. Why logging out or unloading Zscaler Client Connector fails
Trying to disable Zscaler globally on a managed Mac almost always backfires:
- Tamper Protection: Most corporate ZCC App Profiles require a one-time IT password to log out or disable Internet Security (
ZIA), andsudo launchctl bootout system /Library/LaunchDaemons/com.zscaler.*is blocked or immediately respawned. - Z-Tunnel 2.0 bypasses System Proxy settings: Turning off Wi-Fi HTTP/HTTPS proxy toggles in macOS System Settings has no effect on Z-Tunnel 2.0 packet steering.
- Broken corporate access: Even if ZCC stops, ZPA (Zscaler Private Access) internal apps and device-posture-gated SSO (
Okta,Entra ID) stop working.
3. Three practical ways to handle Zscaler SSL inspection on macOS
| Approach | Who controls it | Keeps ZCC & corporate SSO running? | Best use case |
|---|---|---|---|
Per-domain SWG bypass (SWG bar) |
Local Mac user (on authorized networks) | Yes — routes only the selected hostname over your Mac’s physical Hardware IPv4 interface |
Immediate hostname-level relief for pinned apps, WebSockets, or broken developer APIs without disabling ZCC (How to bypass SWG on a Mac) |
Zscaler Admin Portal exclusion (Do Not Inspect / App Profile) |
Enterprise IT / Security team | Yes | Permanent organization-wide exemption under Policy → SSL Inspection → Do Not Inspect or macOS App Profiles → Hostname/IP Bypass (SWG bypass vs. TLS exception) |
| Export & trust Zscaler Root CA in CLI tools | Local developer | Yes (traffic stays inspected) | Corporate policy requires decrypted routing and git, npm, brew, Python, Claude Code, or Cursor fail with unable to get local issuer certificate |
4. Enable per-domain bypass or configure Zscaler Root CA for CLI tools
Option A: Per-domain bypass with SWG bar (when authorized)
- Open SWG bar → Domains, find the exact failing hostname (note that login, API, and CDN domains are separate hostnames—see multi-domain SSO, API, and CDN bypass), and click Enable next to Bypass SWG—or run
swgbar bypass enable <domain>. - Wait for Bypassing, then restart the browser tab, IDE, or CLI session so pooled connections reopen on the direct
HardwareIPv4 route. - Verify with
swgbar probe <domain>that the origin server’s public certificate chain is now returned. If a firewall blocks direct outbound connections, runswgbar bypass disable <domain>to restore normal Zscaler routing immediately.
Option B: Configure CLI & AI tools to trust Zscaler Root CA
If your network policy requires traffic to stay decrypted by Zscaler, export your Zscaler Root CA PEM bundle from Keychain Access (or request the PEM file from IT) and configure your runtimes instead of disabling SSL verification:
# Node.js, npm, Claude Code, Cursor
export NODE_EXTRA_CA_CERTS="$HOME/.certs/zscaler-root.pem"
# Python (pip, requests), OpenSSL, Homebrew curl
export SSL_CERT_FILE="$HOME/.certs/zscaler-root.pem"
export REQUESTS_CA_BUNDLE="$HOME/.certs/zscaler-root.pem"
export CURL_CA_BUNDLE="$HOME/.certs/zscaler-root.pem"
# Git
git config --global http.sslCAInfo "$HOME/.certs/zscaler-root.pem"
For full runtime instructions covering Homebrew, Docker Desktop, Python, Node.js, Claude Code, and Cursor, read Configure CA trust for Homebrew, Docker, Python, and Node.js and Fix Claude Code & Cursor certificate errors on macOS.