Discover
Coffee, Chaos and ProdSec
Coffee, Chaos and ProdSec
Author: Cameron Walters and Kurt Hendle
Subscribed: 3Played: 64Subscribe
Share
© Cameron Walters and Kurt Hendle
Description
Coffee, Chaos & ProdSec is where cybersecurity meets caffeine-fueled chaos.
Hosts Kurt (security architect and chaos tamer) and Cameron (ProdSec wrangler and DevSecOps junkie) dive into hacking, AppSec, supply chain failures, AI surprises, and the everyday madness of defending modern systems.
With humor, sharp insight, real breach breakdowns, bad password confessions, and a few questionable impressions, they explore the messy reality of security and how teams survive it.
New episodes Every Wednesday at 5 AM Eastern.
Hosts Kurt (security architect and chaos tamer) and Cameron (ProdSec wrangler and DevSecOps junkie) dive into hacking, AppSec, supply chain failures, AI surprises, and the everyday madness of defending modern systems.
With humor, sharp insight, real breach breakdowns, bad password confessions, and a few questionable impressions, they explore the messy reality of security and how teams survive it.
New episodes Every Wednesday at 5 AM Eastern.
64 Episodes
Reverse
🎙️ Coffee, Chaos and ProdSec, Ep 63 A recruiter sends a take-home test. An engineer runs it on a work laptop. A few hops later, Binance is looking at $6.34 billion in impacted assets. This week Cameron and Kurt trace the chain from fake interview to wallet signing service and argue the dev laptop is production attack surface now. Kurt's advice: get your own laptop, break your own stuff. They also untangle the AI jargon. Mythos is a model, Claude Code is a harness, a skill is just a reusable prompt, and your agent is not a robot. Then it's slopsquatting, SCA scans that skip what they can't resolve, sandboxes that leak once an agent gets an outbound link, and a complaint about slopnades. If you run Product Security, Application Security, Security Architecture, DevSecOps, or anything else in Cybersecurity, your dev environment is in scope. Please Fill out our Survey <<< ☕ New episodes every Wednesday. Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.
🎙️ Coffee, Chaos and ProdSec, Ep 62 Agents fix vulns without arguing. Developers still push back. And security teams still measure their worth in bug counts. Blake is back for the Q3 2026 State of ProdSec, and the first question wasn't even on the list. Cutting open source dependencies to stop the CVE tsunami fire drills turned into a Log4j and attack surface debate before anyone defined Product Security. From whether a system prompt that says please counts as an AI guardrail to why an agent sandbox breakout gets a press release while an employee gets jail time, Cameron and Kurt dig into the Security Architecture and Application Security calls teams are making today. Plus GRC asking if you're "Mythos ready" and the bug janitor identity crisis. If you work in Product Security or DevSecOps and your Cybersecurity program reports nothing but burndown charts, this Chaos is for you. ☕ New episodes every Wednesday. Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.
🎙️ Coffee, Chaos and ProdSec, Ep 61Q3 ended with PHP on fire and AI agents breaking out of their own test labs. Somehow security teams are still graded on how many findings they produce.This week Cameron and Kurt team up with Seth Law and Ken Johnson of Absolute AppSec for the quarterly state of ProdSec. The crew gets into the vuln count value trap and the bug janitor careers it created, where whole teams exist to triage one scanner's output.From frontier labs locking in boardrooms and absorbing security researchers, to custom source replacing open source and making bug bounties more targeted, the room splits 2v2 between doom and enablement. Kurt calls it the incident response era.If you work in Product Security, Application Security, Security Architecture, DevSecOps, or Cybersecurity and AI has turned your backlog into pure chaos, you'll feel right at home.☕ New episodes every Wednesday.Coffee, Chaos and ProdSec -> strong coffee, stronger opinions
🎙️ Coffee, Chaos and ProdSec, Ep 60 Your build pipeline runs whatever gets pushed to it. Your secrets sit unmasked in runner memory. And the attackers figured this out before your defenders did. This week Cameron and Kurt bring on François Proulx, CTO of Boost Security, who spent four years publishing supply chain research only to watch threat actors quote his own tools back to him on a dark web forum. So he built SmokedMeat, Metasploit but for CI/CD, and a CTF called whooli so you can run it without going to jail. From the Ultralytics and tj-actions compromises, to dumping OIDC tokens straight out of an ephemeral runner, to why private repos are the bigger risk and not the safer one, this episode gets into how build pipeline exploitation actually works and what Product Security teams keep getting wrong. Real attack paths, real incidents, and the AI angle making all of it faster. If you work in ProdSec, DevSecOps, Security Architecture, or Cybersecurity and you still don't threat model your YAML, this one is for you. ☕ New episodes every Wednesday. Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.
🎙️ Coffee, Chaos and ProdSec, Ep 59 AI writes most of the code now, and Cybersecurity still shows up after it ships to review it. Cameron and Kurt join Michael Nov, Co-Founder and CEO of Prime Security, to fight about where Product Security belongs in the agentic SDLC. Cameron wants scanning inside the agent loop and out of the PR. Michael says keep control at the PR, because a developer can just type ignore. They also get into whether developers should still learn security or whether you build guardrails around them, and who owns the fix when a vendor promised one and the breach landed anyway. Kurt's Security Architecture answer: the judge tells you to leave. If your Application Security scanner hands you thousands of findings and no fix, this DevSecOps chaos will feel familiar. ☕ New episodes every Wednesday. Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.




