Netskope SSL Inspection on Mac: Check Decryption & Bypass per Domain

Check if Netskope Client is decrypting HTTPS on your Mac (*.goskope.com CA), compare per-domain SWG bar bypass vs. Do Not Decrypt policy, and configure nscacert_combined.pem.

SWG bar · Updated

To check whether Netskope Client is performing SSL/TLS decryption on your Mac, open SWG bar → Overview (or run swgbar overview) and verify whether the Domain interception ratio is above 0% with a Netskope or *.goskope.com tenant certificate under MITM certificates. To bypass Netskope SSL inspection for a specific hostname on an authorized Mac, open SWG bar → Domains, select the hostname, and click Enable beside Bypass SWG (or run swgbar bypass enable <domain>).

Netskope Secure Web Gateway is widely deployed on enterprise macOS fleets using a NetworkExtension steering client and a tenant-specific intermediate CA. Because the Netskope root CA is pushed via MDM into macOS Keychain, browsers display normal green/valid security indicators while CLI runtimes (pip, npm, AWS CLI, git, Docker, Claude Code) and certificate-pinned desktop apps fail with CERTIFICATE_VERIFY_FAILED or UNABLE_TO_GET_ISSUER_CERT_LOCALLY.

1. Verify whether Netskope is decrypting a domain on your Mac

Check both system-wide interception and individual hostnames:

  • Menu bar & Chrome visibility with SWG bar: Install SWG bar (macOS 14+ Apple silicon, 14-use-day free trial) and browse or run your failing command. Open SWG bar → Domains or run swgbar domains list --status confirmed to list every hostname whose TLS certificate was re-signed by your Netskope tenant CA (commonly formatted like ca.<tenant>.goskope.com or your company’s custom CA). Pair it with the free SWG bar Chrome extension to see status badges in your browser toolbar.
  • Check Netskope certificates and live issuer in Terminal:
# Check whether a Netskope CA is installed in the macOS System Keychain
security find-certificate -c "Netskope" /Library/Keychains/System.keychain

# Inspect the live certificate issuer returned for a specific hostname
openssl s_client -connect registry.npmjs.org:443 -servername registry.npmjs.org </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject

Remember that Netskope policies often decrypt some SaaS or code-hosting domains while steering others untouched; always test the exact hostname that is failing.

2. Why quitting Netskope Client usually does not work

In managed environments with Netskope’s Protect Client configuration and resources tamper-protection policy enabled, the Disable option in the Netskope menu bar icon is disabled or password-locked, and force-unloading the daemon breaks system network routing. Clearing macOS Wi-Fi proxy fields also does nothing because Netskope steers traffic at the macOS NetworkExtension layer.

3. Choose the right Netskope fix on macOS

Method Stops Netskope decryption? Requires Netskope Tenant Admin? Best when
Per-domain SWG bypass (SWG bar) Yes, for selected hostnames over physical Hardware IPv4 No (local control on an authorized Mac) A pinned app, WebSocket, or dev endpoint fails under Netskope decryption and a direct IPv4 path exists (How to bypass SWG on a Mac)
Netskope Tenant Do Not Decrypt / Certificate Pinned Apps exception Yes, centrally across managed Macs Yes (Policies → SSL Decryption → Do Not Decrypt or Steering Configuration → Exceptions) Organization-wide pinned desktop apps or shared developer endpoints break for the whole team (SWG bypass vs. TLS exception)
Combined CA bundle (nscacert_combined.pem) for CLI tools No (traffic remains inspected) No Policy requires decrypted Netskope routing and CLI/AI tools just need to trust the Netskope CA chain

4. Apply per-domain bypass or configure Netskope CLI CA trust

Option A: Per-domain bypass via SWG bar (when authorized)

  1. Open SWG bar → Domains, select the exact inspected hostname (for example api.anthropic.com or pypi.org), and click Enable beside Bypass SWG—or run swgbar bypass enable <domain>.
  2. Wait until Bypassing appears, then restart your browser tab, terminal tool, or IDE so existing pooled TLS/HTTP/3 connections reconnect over the physical Hardware IPv4 interface.
  3. Confirm with swgbar probe <domain> that the origin’s public certificate chain is now served. To revert immediately, click the active control or run swgbar bypass disable <domain>.

Option B: Build a combined PEM bundle for CLI tools under Netskope

If traffic must remain inspected by Netskope, export a combined PEM bundle from your macOS trust stores (or use the nscacert_combined.pem bundle provided by your IT team) and point your developer tools to it in ~/.zshrc:

security find-certificate -a -p \
  /System/Library/Keychains/SystemRootCertificates.keychain \
  /Library/Keychains/System.keychain > "$HOME/.certs/nscacert_combined.pem"

export NODE_EXTRA_CA_CERTS="$HOME/.certs/nscacert_combined.pem"
export REQUESTS_CA_BUNDLE="$HOME/.certs/nscacert_combined.pem"
export SSL_CERT_FILE="$HOME/.certs/nscacert_combined.pem"
export AWS_CA_BUNDLE="$HOME/.certs/nscacert_combined.pem"

See Fix SWG TLS & SSL certificate errors in CLI and AI tools and Homebrew, Docker, Python, and Node.js CA trust for tool-specific setup.