Show notes
Creating an application threat model was a resource-intensive process that took weeks or months, resulting in static documents that were abandoned 80% of the time after their initial creation. However, with development speeds accelerating through AI, security teams must move away from point-in-time blueprints and adopt continuous, enterprise-wide threat modeling to keep pace. In this episode, Ashish sits down with Ben Oster, CPO at ThreatModeler, to discuss how AI is fundamentally changing how we secure software design. Ben explains how Large Language Models (LLMs) can ingest context from Terraform, code repositories, and Confluence pages to generate comprehensive threat models in minutes instead of months. By integrating AI directly into pull requests, organizations can continuously monitor architectural drift across microservices and reduce the manual burden on both developers and security architects.
Guest Socials - Ben's Linkedin
Podcast Twitter - @CloudSecPod
If you want to watch videos of this LIVE STREAMED episode and past episodes - Check out our other Cloud Security Social Channels:
-Cloud Security Podcast- Youtube
- Cloud Security Newsletter
If you are interested in AI Security, you can check out our sister podcast - AI Security Podcast
Questions asked:
(00:00) Introduction to Continuous Threat Modeling(02:50) Ben Oster’s Background in Privacy, Compliance, and Cybersecurity(04:00) Why 80% of Traditional Threat Models Are Abandoned(06:30) How LLMs Generate Threat Models from Repositories and Confluence(08:30) Shifting from Point-in-Time Blueprints to Continuous Assessment(10:30) Integrating Threat Models Directly into AI Engineering Prompts(12:30) Moving Beyond STRIDE: Focusing on Speed and Developer Adoption(15:30) Building Enterprise-Wide Reusable Security Controls(18:30) The "Build vs. Buy" Dilemma for Continuous Threat Modeling(22:30) Managing Cascading…
Website: podcasters.spotify.com