If you use a company-issued MacBook, you have probably run into this exact paradox: Safari and Chrome load GitHub, npm, and AI tools with a completely normal padlock icon, while your Terminal explodes with errors like unable to get local issuer certificate, CERTIFICATE_VERIFY_FAILED, or mysteriously dropped WebSocket and HTTP/2 streams.

The culprit is almost always corporate SSL/HTTPS inspection (often called break-and-inspect) enforced by a Secure Web Gateway (SWG) such as Zscaler Client Connector, Netskope, Cloudflare WARP Zero Trust, Cisco Secure Client, or Palo Alto GlobalProtect.

Here is how to verify in 60 seconds whether your Mac is being intercepted, why most generic proxy workarounds fail on modern macOS, and the three safe ways engineers actually fix it.

1. How to Tell If Your Work Mac Is Intercepting HTTPS

When IT enrolls a Mac in MDM (Jamf, Kandji, or Microsoft Intune), they silently push a corporate Root Certificate Authority (CA) into macOS Keychain. Because Safari and Chrome trust macOS Keychain automatically, the browser never warns you when an SWG terminates your TLS connection, inspects the decrypted traffic, and re-signs it with the company root CA.

You can check what is installed on your Mac right now with four read-only Terminal commands (no admin password needed):

# 1. Check whether the Mac is enrolled in corporate MDM profiles status -type enrollment # 2. Check explicit system proxies and PAC URLs scutil --proxy # 3. Inspect custom root trust overrides in macOS Keychain security dump-trust-settings -d # 4. Inspect the live TLS certificate issuer presented to Terminal openssl s_client -connect api.github.com:443 -servername api.github.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject 

Look at the issuer= line from openssl:

  • Public CA (DigiCert, Let’s Encrypt, Google Trust Services): that specific hostname was not decrypted.
  • Corporate / Gateway CA (Zscaler Root CA, *.goskope.com for Netskope, Cloudflare Gateway CA, or your company name): HTTPS inspection is active on that domain.

Keep in mind that checking one domain only tells you about that hostname — many corporate policies exclude banking or Microsoft 365 while decrypting GitHub, PyPI, npm, and LLM APIs. If you want continuous visibility across every domain without clicking browser padlocks one tab at a time, a native macOS menu bar SSL inspection checker like SWG bar compares macOS System Trust against Apple’s public root store per hostname and flags any Domain interception ratio above 0% (see the full work Mac HTTPS inspection checklist).

2. Why Common "Bypass" Tips Fail on macOS 14+

Before touching system files, it helps to understand why the top forum suggestions usually backfire on a managed Mac:

  • Turning off Wi-Fi proxies (System Settings → Network → Proxies): Modern SWG agents like Zscaler Z-Tunnel 2.0, Netskope, and Cloudflare WARP use a macOS NetworkExtension transparent proxy or utun virtual interface below system proxy toggles. Even an empty scutil --proxy output does not mean traffic is uninspected.
  • Deleting the corporate Root CA in Keychain Access: Removing the certificate does not stop the gateway from intercepting packets. Instead, Safari and Chrome immediately block every intercepted website with NET::ERR_CERT_AUTHORITY_INVALID, and MDM typically re-pushes the profile on the next check-in.
  • Running curl -k or export NODE_TLS_REJECT_UNAUTHORIZED=0: Disabling TLS validation does not bypass SSL inspection — your traffic still flows through and gets decrypted by the gateway, while simultaneously exposing your API tokens on any untrusted network.
  • Killing the SWG daemon with launchctl bootout: Enterprise agents use Tamper Protection and watchdog daemons to respawn within seconds, and stopping the agent often breaks device-posture checks for Okta or Entra ID SSO.

3. Three Legitimate Ways to Handle SWG SSL Inspection on Mac

Option Stops SSL Decryption? Keeps SWG Agent & Corporate SSO Running? Best When
CLI & Runtime CA Trust (NODE_EXTRA_CA_CERTS, SSL_CERT_FILE) No (traffic remains inspected) Yes Policy requires decrypted routing and Git/npm/Python/Claude Code/Cursor only reject the enterprise CA
IT Gateway Do Not Decrypt Exclusion Yes (central policy) Yes Certificate-pinned desktop apps or mTLS endpoints break team-wide
Per-Domain SWG Bypass (SWG bar) Yes (selected hostnames over physical IPv4) Yes Authorized networks where a specific inspected hostname breaks pinning, WebSockets, or latency

Option A: Configure CLI & Runtime CA Trust (Keeps SWG Inspection Active)

If company policy requires traffic to stay decrypted by the SWG and you only need Git, Node.js, Python, Homebrew, Claude Code, or Cursor to stop failing certificate checks, export your corporate root CA as a PEM file (or request it from IT) and configure your runtimes cleanly in ~/.zshrc:

# Node.js, npm, Claude Code, Cursor export NODE_EXTRA_CA_CERTS="$HOME/.certs/corporate-ca.pem" # Python (pip, requests), OpenSSL, Homebrew curl export SSL_CERT_FILE="$HOME/.certs/corporate-ca.pem" export REQUESTS_CA_BUNDLE="$HOME/.certs/corporate-ca.pem" export CURL_CA_BUNDLE="$HOME/.certs/corporate-ca.pem" # Git git config --global http.sslCAInfo "$HOME/.certs/corporate-ca.pem" 

Option B: Request an IT Gateway "Do Not Decrypt" Exclusion

When an application uses strict TLS certificate pinning or mutual TLS (mTLS), trusting the corporate CA still will not make it work because the binary checks for the origin server’s hardcoded public key. In those cases, submit the exact failing hostnames (including separate auth, API, and CDN domains) to your IT team so they can add a central Do Not Inspect / Do Not Decrypt exclusion in Zscaler, Netskope, Cloudflare Gateway, or Palo Alto.

Option C: Per-Domain SWG Bypass on an Authorized Mac

When you administer a network or are authorized to test uninspected routing for specific broken hostnames without turning off your corporate agent globally, you can route just the selected domain over your Mac’s physical Hardware IPv4 interface (en0 / en7) while leaving all other corporate traffic and SSO posture untouched.

With SWG bar on Apple Silicon Macs (macOS 14+), you can inspect the affected hostname in the menu bar app or via CLI and toggle per-domain bypass in one step:

# Check which domains are confirmed intercepted swgbar domains list --status confirmed # Enable bypass for one specific hostname (on authorized networks) swgbar bypass enable api.example.com # Re-probe to verify the public certificate chain is now returned swgbar probe api.example.com 

Once the rule shows Bypassing, reload the browser tab or restart your CLI/IDE session so existing keep-alive sockets and HTTP/3 streams reopen on the direct path. If your corporate firewall blocks direct outbound IPv4 traffic, disable the rule immediately (swgbar bypass disable <domain>) and fall back to Option A or Option B.

Vendor-Specific Guides & Further Reading

If you want deeper step-by-step commands for your specific macOS setup, these technical guides cover every edge case in detail:

One final rule of thumb for work laptops: always respect your organization’s acceptable-use policy, keep personal banking and private accounts off MDM-managed devices, and verify any TLS change with fresh certificate evidence rather than guessing.