# 45 - Governing AI Sprawl Before It Governs You with Yabing Wang Page: https://stenobird.com/podcast/cloud-currents-6702988/45-governing-ai-sprawl-before-it-governs-you-with-yabing-wang Text version: https://stenobird.com/podcast/cloud-currents-6702988/45-governing-ai-sprawl-before-it-governs-you-with-yabing-wang.md Podcast: [Cloud Currents](https://stenobird.com/podcast/cloud-currents-6702988) Published: 2026-02-26T00:37:00+00:00 Episode link: https://traffic.megaphone.fm/LDB6597870408.mp3 Audio file: https://traffic.megaphone.fm/LDB6597870408.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/cloud-currents-6702988/episodes/45-governing-ai-sprawl-before-it-governs-you-with-yabing-wang Duration seconds: 3034 ## Resource In this episode of Cloud Currents, host Matt Pacheco sits down with Yabing Wang, VP of Security & IT Services and dual CISO/CIO at JustWorks, for one of the most candid conversations yet on what it actually takes to lead security in the age of AI. Yabing opens up about her unlikely path from philosophy major to Netscape engineer to cybersecurity leader — and why that winding road gave her the mental frameworks she relies on today. Then the conversation gets into the real stuff: how AI is reshaping the threat landscape faster than most organizations can respond, why your attack surface grew from 5 integrations to 500 almost overnight, and what "AI tool sprawl" is actually costing your business in risk, money, and operational clarity. ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/cloud-currents-6702988/episodes/45-governing-ai-sprawl-before-it-governs-you-with-yabing-wang/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/cloud-currents-6702988/45-governing-ai-sprawl-before-it-governs-you-with-yabing-wang.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.