Enterprise SWG & MDM HTTPS inspection on a Mac

Understand how Zscaler, Netskope, and Cloudflare Gateway inspect HTTPS/SSL on MDM-managed Macs, why browsers show a lock icon, and how to check each domain.

SWG bar · Updated

On a company-managed Mac, web traffic frequently passes through a Secure Web Gateway (SWG)—such as Zscaler, Netskope, or Cloudflare Gateway—to enforce security and access policies. Depending on policy, the gateway may simply forward encrypted connections for one domain while performing full HTTPS/SSL inspection (break-and-inspect) on another.

Because mobile device management (MDM) can install an organization’s root certificate authority (CA) silently into macOS Keychain, Safari and Chrome continue showing a normal lock icon even when TLS is terminated and re-encrypted by the gateway.

Why the browser padlock looks the same

On an unmanaged Mac, if an intermediary replaces a website’s TLS certificate, the browser displays a prominent security warning because the signing CA is unknown. On an MDM-enrolled Mac, IT deploys a trusted root CA profile to the system trust store:

  1. Your Mac connects to an HTTPS destination through the SWG agent or network tunnel.
  2. For inspected categories or domains, the SWG decrypts the payload, applies policy checks, and presents a newly generated certificate signed by your company’s root CA.
  3. macOS evaluates the chain, finds the MDM-trusted root CA in Keychain, and reports a valid connection to the browser.

As a result, looking at the address bar padlock alone cannot tell you whether a domain used the origin’s public certificate or a locally trusted enterprise root.

Three different connection states on a managed Mac

When auditing domains on macOS, separate routing from HTTPS decryption:

State Certificate chain observed Traffic path
HTTPS / SSL break-and-inspect Signed by a locally trusted enterprise or inspection root CA rather than a public root CA. Terminated, decrypted, and re-encrypted by the SWG.
Gateway forwarding / TLS exception Public certificate chain issued by a public CA (such as Let’s Encrypt, DigiCert, or Google Trust Services). Still traverses the SWG or corporate network, without TLS decryption.
Per-domain SWG bypass Public certificate chain from the destination (when no other intercepting proxy is present). Selected hostname uses a direct route outside gateway decryption on authorized networks.

Read SWG bypass vs. TLS inspection exception for a full breakdown of why seeing a public certificate chain alone does not prove traffic bypassed the gateway.

Check which domains your SWG decrypts on macOS

  1. Install SWG bar on macOS 14 or later (Apple silicon) and open it from the menu bar.
  2. Check Overview to see the percentage of observed domains classified as Confirmed or Suspected inspection and which root certificates are signing them.
  3. Open Domains to inspect individual hostnames, or install the Chrome companion extension to view recorded domain status in your browser toolbar as you browse.
  4. Open Certificates (or run swgbar certificates list via the CLI) to inspect the issuer, validity window, SHA-256 fingerprint, and full list of observed domains tied to each local root CA.
SWG bar certificate view showing root certificate clusters and trust details on macOS; illustrative preview.

Illustrative preview of the SWG bar Certificates view on macOS.

Common symptoms and next steps