<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: SWG bar</title>
    <description>The latest articles on DEV Community by SWG bar (@swgbar).</description>
    <link>https://dev.to/swgbar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253356%2F94fa85fe-5858-424f-a9bd-90fde1476bf8.png</url>
      <title>DEV Community: SWG bar</title>
      <link>https://dev.to/swgbar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/swgbar"/>
    <language>en</language>
    <item>
      <title>How to Check and Bypass Corporate SSL Inspection (SWG, Zscaler, Netskope) on a Mac</title>
      <dc:creator>SWG bar</dc:creator>
      <pubDate>Thu, 19 Nov 2026 08:55:22 +0000</pubDate>
      <link>https://dev.to/swgbar/how-to-check-and-bypass-corporate-ssl-inspection-swg-zscaler-netskope-on-a-mac-2m0n</link>
      <guid>https://dev.to/swgbar/how-to-check-and-bypass-corporate-ssl-inspection-swg-zscaler-netskope-on-a-mac-2m0n</guid>
      <description>&lt;p&gt;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 &lt;code&gt;unable to get local issuer certificate&lt;/code&gt;, &lt;code&gt;CERTIFICATE_VERIFY_FAILED&lt;/code&gt;, or mysteriously dropped WebSocket and HTTP/2 streams.&lt;/p&gt;

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

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. How to Tell If Your Work Mac Is Intercepting HTTPS
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;You can check what is installed on your Mac right now with four read-only Terminal commands (no admin password needed):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# 1. Check whether the Mac is enrolled in corporate MDM&lt;/span&gt;
profiles status -type enrollment

&lt;span class="c"&gt;# 2. Check explicit system proxies and PAC URLs&lt;/span&gt;
scutil --proxy

&lt;span class="c"&gt;# 3. Inspect custom root trust overrides in macOS Keychain&lt;/span&gt;
security dump-trust-settings -d

&lt;span class="c"&gt;# 4. Inspect the live TLS certificate issuer presented to Terminal&lt;/span&gt;
openssl s_client -connect api.github.com:443 -servername api.github.com &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;/dev/null 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null &lt;span class="o"&gt;|&lt;/span&gt; openssl x509 -noout -issuer -subject
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Look at the &lt;code&gt;issuer=&lt;/code&gt; line from &lt;code&gt;openssl&lt;/code&gt;:&lt;/p&gt;

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

&lt;p&gt;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 &lt;a href="https://swgbar.com/en/guides/ssl-inspection-checker-mac/" rel="noopener noreferrer"&gt;SWG bar&lt;/a&gt; compares &lt;strong&gt;macOS System Trust&lt;/strong&gt; against &lt;strong&gt;Apple’s public root store&lt;/strong&gt; per hostname and flags any Domain interception ratio above &lt;code&gt;0%&lt;/code&gt; (see the full &lt;a href="https://swgbar.com/en/guides/check-if-work-mac-intercepting-https/" rel="noopener noreferrer"&gt;work Mac HTTPS inspection checklist&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Why Common "Bypass" Tips Fail on macOS 14+
&lt;/h2&gt;

&lt;p&gt;Before touching system files, it helps to understand why the top forum suggestions usually backfire on a managed Mac:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Turning off Wi-Fi proxies (&lt;code&gt;System Settings → Network → Proxies&lt;/code&gt;)&lt;/strong&gt;: Modern SWG agents like Zscaler Z-Tunnel 2.0, Netskope, and Cloudflare WARP use a macOS &lt;code&gt;NetworkExtension&lt;/code&gt; transparent proxy or &lt;code&gt;utun&lt;/code&gt; virtual interface below system proxy toggles. Even an empty &lt;code&gt;scutil --proxy&lt;/code&gt; output does not mean traffic is uninspected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deleting the corporate Root CA in Keychain Access&lt;/strong&gt;: Removing the certificate does not stop the gateway from intercepting packets. Instead, Safari and Chrome immediately block every intercepted website with &lt;code&gt;NET::ERR_CERT_AUTHORITY_INVALID&lt;/code&gt;, and MDM typically re-pushes the profile on the next check-in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Running &lt;code&gt;curl -k&lt;/code&gt; or &lt;code&gt;export NODE_TLS_REJECT_UNAUTHORIZED=0&lt;/code&gt;&lt;/strong&gt;: Disabling TLS validation does &lt;strong&gt;not&lt;/strong&gt; bypass SSL inspection — your traffic still flows through and gets decrypted by the gateway, while simultaneously exposing your API tokens on any untrusted network.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Killing the SWG daemon with &lt;code&gt;launchctl bootout&lt;/code&gt;&lt;/strong&gt;: 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.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Three Legitimate Ways to Handle SWG SSL Inspection on Mac
&lt;/h2&gt;

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

&lt;h3&gt;
  
  
  Option A: Configure CLI &amp;amp; Runtime CA Trust (Keeps SWG Inspection Active)
&lt;/h3&gt;

&lt;p&gt;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 &lt;code&gt;~/.zshrc&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Node.js, npm, Claude Code, Cursor&lt;/span&gt;
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;NODE_EXTRA_CA_CERTS&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$HOME/.certs/corporate-ca.pem"&lt;/span&gt;

&lt;span class="c"&gt;# Python (pip, requests), OpenSSL, Homebrew curl&lt;/span&gt;
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;SSL_CERT_FILE&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$HOME/.certs/corporate-ca.pem"&lt;/span&gt;
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;REQUESTS_CA_BUNDLE&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$HOME/.certs/corporate-ca.pem"&lt;/span&gt;
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;CURL_CA_BUNDLE&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$HOME/.certs/corporate-ca.pem"&lt;/span&gt;

&lt;span class="c"&gt;# Git&lt;/span&gt;
git config --global http.sslCAInfo &lt;span class="s2"&gt;"$HOME/.certs/corporate-ca.pem"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Option B: Request an IT Gateway "Do Not Decrypt" Exclusion
&lt;/h3&gt;

&lt;p&gt;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 &lt;strong&gt;Do Not Inspect / Do Not Decrypt&lt;/strong&gt; exclusion in Zscaler, Netskope, Cloudflare Gateway, or Palo Alto.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option C: Per-Domain SWG Bypass on an Authorized Mac
&lt;/h3&gt;

&lt;p&gt;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 &lt;code&gt;Hardware&lt;/code&gt; IPv4 interface (&lt;code&gt;en0&lt;/code&gt; / &lt;code&gt;en7&lt;/code&gt;) while leaving all other corporate traffic and SSO posture untouched.&lt;/p&gt;

&lt;p&gt;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:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Check which domains are confirmed intercepted&lt;/span&gt;
swgbar domains list --status confirmed

&lt;span class="c"&gt;# Enable bypass for one specific hostname (on authorized networks)&lt;/span&gt;
swgbar bypass &lt;span class="nb"&gt;enable&lt;/span&gt; api.example.com

&lt;span class="c"&gt;# Re-probe to verify the public certificate chain is now returned&lt;/span&gt;
swgbar probe api.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once the rule shows &lt;strong&gt;Bypassing&lt;/strong&gt;, 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 (&lt;code&gt;swgbar bypass disable &amp;lt;domain&amp;gt;&lt;/code&gt;) and fall back to Option A or Option B.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vendor-Specific Guides &amp;amp; Further Reading
&lt;/h2&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://swgbar.com/en/guides/how-to-bypass-swg/" rel="noopener noreferrer"&gt;How to bypass SWG on a Mac (one-click domain bypass, NetworkExtension approval &amp;amp; CLI)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://swgbar.com/en/guides/zscaler-ssl-inspection-bypass-mac/" rel="noopener noreferrer"&gt;Zscaler SSL inspection on Mac (ZIA / Z-Tunnel 2.0 detection, bypass &amp;amp; CLI CA setup)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://swgbar.com/en/guides/netskope-ssl-inspection-bypass-mac/" rel="noopener noreferrer"&gt;Netskope SSL inspection on Mac (&lt;code&gt;*.goskope.com&lt;/code&gt; checks &amp;amp; &lt;code&gt;nscacert_combined.pem&lt;/code&gt;)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://swgbar.com/en/guides/ssl-inspection-checker-mac/" rel="noopener noreferrer"&gt;SSL inspection checker for Mac (menu bar app + free Chrome extension + CLI/MCP)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://swgbar.com/en/guides/ai-coding-agents-claude-code-cursor-swg-macos/" rel="noopener noreferrer"&gt;Fix Claude Code &amp;amp; Cursor &lt;code&gt;unable to get local issuer certificate&lt;/code&gt; on Mac&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

</description>
      <category>macos</category>
      <category>cybersecurity</category>
      <category>devops</category>
      <category>networking</category>
    </item>
  </channel>
</rss>
