Coffee, Chaos and ProdSec

🎙️ 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 61

Q3 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.

🎙️ Coffee, Chaos and ProdSec, Ep 58

Your PR gate blocked the merge again. Or worse, the scan is still spinning and engineering wants to know why.

This week Cameron and Kurt make the case for informing over blocking. Cameron explains why every PR blocking rollout he's run caused more headache than value, and it was the ops game, not the findings. Engineering merges, engineering owns the risk.

Kurt takes it into the agentic SDLC, where scanners find and agents fix at machine speed, so a blocking gate just stalls the loop. They also vent about the chaos of the AI news cycle and call agent sandboxing what it is, system hardening.

If you work in Product Security, Application Security, DevSecOps, Security Architecture, or anywhere in Cybersecurity and you've ever unblocked a PR at 2 AM, this one's for you.

☕ New episodes every Wednesday.

Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.

🎙️ Coffee, Chaos and ProdSec, Ep 57

Your AI chat window has a human reader now. Your bug bounty program can't triage its own findings. And somewhere out there, 18 AI agents are shipping code that nobody's going to review.

This week Cameron and Kurt trace one thread through four different stories: the gap between what we assume is private and what actually is. From an encrypted AI chat pitch built on the same logic that created Signal, to a leaked contractor pipeline reading real ChatGPT conversations, to a vulnerability management rant about why finding bugs faster doesn't make you more secure, to a solo developer running a fleet of AI agents that write more code in a day than any human could review in a week.

They cover zero retention agreements that nobody can actually audit, bug bounty programs that exist for legal cover more than for catching bugs, and what it means for Product Security and DevSecOps when code review quietly stops being a human job.

If you work in ProdSec, Application Security, or Security Architecture and you've ever clicked "accept" without reading it, this one's for you.

☕ New episodes every Wednesday.

Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.

🎙️ Coffee, Chaos and ProdSec, Ep 56

Everyone agrees AI needs to slow down. Nobody is actually slowing down. Cameron's already annoyed before the coffee's poured.

This week Cameron goes on a rant about people who let Claude build something and then post like they hand coded it themselves, and why he thinks agent skills are just long prompts dressed up to sound complicated. Kurt pushes back on where the line actually sits between prompting and ownership. Then they get into the AI slowdown discourse nobody can agree on, a governing agent that stood down because the model it was watching claimed to be "just in a simulation," and the NSA, CISA and FBI advisory naming six China based companies for distilling US frontier models, which Cameron calls corporate espionage through the API and Kurt says flat out smells funny.

They close on GTIG's six hour agentic attack chain, why 30 day patch SLAs are already dead, micro segmentation making a comeback, and Kurt's callout that every cyber capability benchmark for these models gets run with the guardrails switched off.

If you work in Cybersecurity, Application Security, Product Security, DevSecOps, or Security Architecture and you're sick of hearing "guardrails" used as a whole sentence, this one's for you.

☕ New episodes every Wednesday.

Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.

🎙️ Coffee, Chaos and ProdSec, Ep 55

Your AI code reviewer costs eleven dollars a pull request. A model from China does the same job for forty two cents. Nobody saw that landing in September.

This week Cameron and Kurt sit down with Patrick Collins and Simon Harloff of Dam Secure, who benchmark every model drop against planted vulnerabilities in real pull requests. Patrick admits he told Simon six months ago that open weights would never catch the frontier labs. Simon told him he was wrong. The data agreed with Simon.

They get into why the best model in the field still misses a third of planted bugs, why Python recall craters compared to TypeScript, what happened when they asked an agent to break out of its own sandbox, and the DIY harness bill that runs past four hundred thousand dollars a year when you pick wrong.

If you work in Product Security, Application Security, DevSecOps, Security Architecture, or Cybersecurity and you are about to sign a twelve month contract on a model that re-ranks every six weeks, listen first.

☕ New episodes every Wednesday.

Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.

🎙️ Coffee, Chaos and ProdSec, Ep 54

An artifact registry handed out admin access to anyone who asked. A print server got popped before the vendor even knew it had a bug. And somehow the vulnerability management metric everyone still quotes doesn't mean what people think it means anymore.

This week Cameron and Kurt tear through two back-to-back critical CVEs, a JFrog Artifactory auth bypass that went from patch to admin token minting in three days, and a PaperCut NG/MF chain that was already being exploited before PaperCut had a name for it. From there they get into Uber open sourcing its Agentic Detection and Response system, the approval fatigue math that breaks human-in-the-loop at scale, and why credential leakage quietly beat prompt injection as the real problem nobody saw coming.

The back half is the DryRun Security piece both hosts read twice before recording. Ken Johnson's argument that chasing Mythos-level parity is a floor, not a strategy, kicks off a real debate about detection versus prevention, the three competing definitions of Mythos ready, and why defenders already hold context attackers can't touch.

If you work in Application Security, Product Security, DevSecOps, or Security Architecture and you're tired of the phrase secure by default meaning nothing, this one's for you.

☕ New episodes every Wednesday.

Coffee, Chaos and ProdSec -> strong coffee, stronger opinions.