How to Bypass SSL Inspection on a Mac (Corporate SWG & Per-Domain Fix)

Learn how to bypass corporate SSL inspection on macOS per domain with SWG bar—why deleting Keychain certs or using curl -k fails, plus IT policy and CA trust options.

SWG bar · Updated

To bypass corporate SSL inspection for a specific hostname on a Mac, open SWG bar → Domains, select the inspected domain, and click Enable next to Bypass SWG (or run swgbar bypass enable <domain> in Terminal). Wait for Bypassing, then reload the browser tab or restart your developer tool so new TLS connections route over your Mac’s physical Hardware IPv4 interface instead of through gateway SSL decryption.

On a work Mac managed via MDM, SSL inspection (also called HTTPS break-and-inspect) is enforced by a Secure Web Gateway (SWG) such as Zscaler, Netskope, Cloudflare Gateway, Cisco Secure Client, or Palo Alto GlobalProtect. Unlike consumer proxy settings, enterprise SSL inspection relies on a system-trusted root CA and a macOS NetworkExtension tunnel—which is why most generic internet advice breaks your Mac or fails silently.

Why common SSL bypass workarounds fail on macOS

Many generic posts recommend fixes designed for local debugging or mobile reverse-engineering that either break corporate access or expose your credentials:

  • Deleting or distrusting the corporate root CA in Keychain Access: Removing an MDM-pushed root CA does not stop the gateway from intercepting packets. Instead, Safari and Chrome immediately reject every intercepted website with NET::ERR_CERT_AUTHORITY_INVALID, and Jamf, Kandji, or Intune typically reinstalls the profile on the next check-in.
  • Disabling TLS verification (curl -k, NODE_TLS_REJECT_UNAUTHORIZED=0, git http.sslVerify false): Turning off certificate verification does not bypass SSL inspection—traffic still flows through and gets decrypted by the gateway, while simultaneously exposing your API tokens and packages to any untrusted Wi-Fi network.
  • Using Frida or browser HSTS hacks: Tools like Frida hook SSL pinning during mobile/desktop reverse-engineering to enable local interception, not to bypass an upstream corporate SWG. Clearing HSTS in chrome://net-internals/#hsts only resets browser strict-transport state and leaves gateway decryption untouched.
  • Turning off Wi-Fi HTTP/HTTPS proxy toggles: Enterprise SWG agents intercept traffic below System Settings → Network → Proxies via a NetworkExtension transparent proxy or utun interface.

Confirm which domains are undergoing SSL inspection first

Before adding any bypass rule, confirm that SSL inspection is actually replacing certificates for the failing hostname rather than a DNS, firewall, or server issue:

  1. Install SWG bar (macOS 14+ on Apple silicon, 14-use-day free trial) and open SWG bar → Overview (or run swgbar overview). Any Domain interception ratio above 0% confirms local root CA interception is active on your Mac.
  2. Open Domains (or run swgbar probe <domain>) to inspect the exact hostname. Remember that web apps, OAuth logins, CDNs, and package registries use distinct hostnames—see multi-domain SSO, API, and CDN SWG bypass.
  3. Review the Certificates tab to verify which enterprise MITM root CA is signing the leaf certificate. For a step-by-step walkthrough, read How to tell if your Mac is intercepted by an SWG.

Compare the 3 safe ways to handle corporate SSL inspection on Mac

Option Stops SSL decryption? Best scenario Setup path
Per-domain SWG bypass (SWG bar) Yes, for selected hostnames over a physical IPv4 path An inspected hostname breaks pinning, WebSockets, or latency on an authorized network SWG bar → Domains → Bypass SWG → Enable or swgbar bypass enable <domain> (full bypass guide)
IT gateway SSL inspection exclusion (Do Not Decrypt) Yes, inside the SWG policy Organization-wide certificate-pinned apps, mTLS endpoints, or banking/health domains Request an admin policy exclusion; compare in SWG bypass vs. TLS inspection exception
Configure tool CA trust (NODE_EXTRA_CA_CERTS, SSL_CERT_FILE) No (traffic remains inspected) Policy requires decrypted routing and CLI tools only reject the enterprise root CA Export PEM bundle and configure runtimes; see Homebrew, Docker, Python, and Node.js CA trust

Step-by-step: Enable and verify per-domain SSL bypass on macOS

  1. Open SWG bar → Domains, select the inspected hostname, and click Enable beside Bypass SWG (or run swgbar bypass enable <domain> via the CLI or MCP).
  2. On first use, approve the macOS network extension and network configuration prompts, then wait until the domain shows Bypassing.
  3. Reload the browser tab or restart the failing terminal command so existing keep-alive sockets and HTTP/3 streams open fresh TCP connections over the bypass rule.
  4. Confirm with fresh evidence: run swgbar probe <domain> (or cross-check with OpenSSL and security verify-cert) to verify that the origin server’s public certificate chain is now presented over a Hardware interface.

Network & policy boundaries: SWG bar 2.4.12 requires an available IPv4 path over a physical network interface (en0 / en7). If a strict corporate firewall drops direct outbound connections, disable the rule (swgbar bypass disable <domain>) to return immediately to normal gateway routing. Always follow your organization’s acceptable-use and security policies.