Skip to content
Episode 325 - Simplified Threat Modeling, Defining A Vulnerability episode artwork

Jun 30, 2026

Episode 325 - Simplified Threat Modeling, Defining A Vulnerability

from Absolute AppSec

In episode 325 of Absolute AppSec, co-hosts Ken Johnson and Seth Law first break down an informal guide to threat modeling, arguing that overly prescriptive frameworks like STRIDE induce a heavy cognitive load on developers. Instead, they advocate for simplified, creative questions to expose architectural gaps, citing a historical GitHub planning flaw where private repository images were left exposed on S3 by relying solely on URL obfuscation. They warn that while rapid development in 2026 pushes toward automated lifecycles, human oversight, critical logging, and constructive friction remain essential. Next, they dissect a research paper exploring the philosophical definition of a vulnerability, framing it as a system disposition arising from a fault that manifests as a failure only when environmental and attacker conditions are jointly met. This definition sparks a debate on whether a flaw must carry immediate risk to qualify as a vulnerability, particularly when evaluating modern AI challenges like system prompt disclosures or exposed deprecated API paths.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Episode 325 - Simplified Threat Modeling, Defining A Vulnerability

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

When was this Absolute AppSec episode published?

This episode was published on June 30, 2026.

Can I download this Absolute AppSec episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.