Home Podcasts DevSec Station
DevSec Station

DevSec Station

Tanya Janca | SheHacksPurple 5 Episodes Oct 8, 2026

DevSec Station is a security focused podcast for software developers who want to create amazing applications. Hosted by Tanya Janca, also known as SheHacksPurple, these short lessons will help you level up.

Episodes

Your AI Worked 59 Times. What About the 60th?
Your AI Worked 59 Times. What About the 60th? Oct 8, 2026 563 What happens when your AI assistant does exactly what you expect 59 times... and then does something completely bananas on the 60th?While teaching a secure coding class, I watched nearly 60 students use the same AI assistant, programming language, and prompts. For 59 of them, everything went as expected.But one student's AI-generated Python code included instructions to suppress linting check
Security Requirements: What They Are and How to Add Them to Your Project
Security Requirements: What They Are and How to Add Them to Your Project Sep 23, 2026 416 Security problems don't generally happen because developers 'don't care' or lack skill. They happen because no one clearly defined what "secure" meant in the first place. When security expectations are left implicit, developers are forced to guess. And that's where vulnerabilities are born.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya
Threat Modeling for Developers (How To)
Threat Modeling for Developers (How To) Sep 9, 2026 428 Threat modeling has a reputation for being complicated, full of diagrams, and requiring long meetings. In reality, most developers already do it, they just don't realize it. The difference is that doing it intentionally helps you catch security problems before they become security incidents.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca breaks threat modeling
How to Do Secure Code Review (When You’re Not a Security Expert)
How to Do Secure Code Review (When You’re Not a Security Expert) Aug 26, 2026 530 Secure code review isn't about finding obscure vulnerabilities or thinking like an elite hacker. It's about verifying that the security controls your application depends on are actually present, in the right place, and correctly implemented.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explains how developers can perform effective secure code reviews wi
The Most Common Secure Coding Mistakes Good Devs Make
The Most Common Secure Coding Mistakes Good Devs Make Aug 12, 2026 504 Security bugs aren't usually caused by 'bad developers'. More often, they're the result of good developers making rational decisions under deadlines, competing priorities, and imperfect systems.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explores why common secure coding mistakes are often incentive problems rather than knowledge problems. Y
Secure Defaults Beat Secure Training
Secure Defaults Beat Secure Training Jul 29, 2026 411 Security training has its place. But if training alone solved security problems, we wouldn't keep seeing the same vulnerabilities appear over and over again. The real problem usually isn't that developers don't know what to do; it's that the easiest path is often an insecure one.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explains why secure
Why Current Security Tools Fail Developers
Why Current Security Tools Fail Developers Jul 15, 2026 389 Security tools are supposed to help developers build safer software. But sometimes it seems like they create more frustration than security.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explains why many security tools overwhelm developers with alerts, how alert fatigue erodes trust, and why "more findings" doesn't mean "more security." Y
Vibe Coding, Copilots, and Security Drift
Vibe Coding, Copilots, and Security Drift Jul 1, 2026 470 AI coding assistants can help developers move incredibly fast. But this new speed comes with a new challenge: security drift.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explores how tools like GitHub Copilot, ChatGPT, Cursor, and other AI coding assistants can unintentionally change the security assumptions your software was built on. You'll learn what sec
Secrets Management: Stop Playing Whack-a-Mole
Secrets Management: Stop Playing Whack-a-Mole Jun 17, 2026 428 If you've ever committed an API key, password, token, certificate, or other secret to a repository, you're not alone. Most secret leaks don't happen because developers don't care about security. They happen because the easiest place to put a secret is inside the code that uses it.This episode is sponsored by Maze.In this episode of DevSec Station, Tanya Janca explains why secre
Supply Chain Is More Than Just Dependencies
Supply Chain Is More Than Just Dependencies Jun 4, 2026 420 Most developers think software supply chain security starts and ends with dependencies. But modern supply chain attacks don't stop there. Attackers look for paths into your software, and those paths often run through developers, CI/CD systems, build tools, deployment pipelines, and other trusted parts of the software delivery process.This episode is sponsored by Maze.In this episode of DevSec
Malicious Dependencies Aren’t an Accident
Malicious Dependencies Aren’t an Accident May 20, 2026 469 Malicious dependencies are not accidents. They are often intentionally designed to look trustworthy so developers install them without hesitation. In this episode of DevSec Station, Tanya Janca explains how attackers use typosquatting, dependency confusion, fake packages, and even AI-generated recommendations to compromise developer environments and steal credentials. This episode is sponsored by
NPM Supply Chain Attack: Active Worm Stealing Tokens, SSH Keys, and Credentials
NPM Supply Chain Attack: Active Worm Stealing Tokens, SSH Keys, and Credentials Apr 22, 2026 149 🚨 Emergency DevSec Station update.There’s an active npm supply chain attack happening right now.Malicious npm packages are running install scripts that quietly steal: • SSH keys • AWS credentials • GitHub tokens • Browser passwords • Crypto walletsFrom there, the attack uses your npm publish token to spread into every package you maintain. That’s how this turns into a worm across the npm ecosystem

Recommended