Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

AI Security Table

AI Security Table artwork

Don't Bury the Model T: Why STRIDE Still Drives in an AI World

Jul 1, 202659 minAudio

Do AI systems require a new threat-modeling method, or are we abandoning useful tools before understanding their limits? Chris Romeo, Izar Tarandach, and Matt Coles first examine npm's move toward safer install defaults and the risk that agents trained on older behavior will simply re-enable dangerous options. Then they debate the claim that STRIDE belongs to a world that no longer exists. The discussion separates threat categories from modeling techniques, non-deterministic model behavior from deterministic controls, and unfamiliar failures from familiar security responsibilities. The Model T analogy gives both sides something to argue with: an older framework may need adaptation, but declaring it obsolete does not explain how the replacement improves the analysis. Mentioned in this Episode: ➜ npm install documentation ➜ Microsoft Threat Modeling Tool: STRIDE threats Chapters: 00:00:00 - Intro: deterministic fans 00:01:32 - npm and secure install defaults 00:03:22 - Will AI agents re-enable risky behavior? 00:05:35 - Other package managers and safe defaults 00:10:02 - Checking packages and internal repositories 00:15:26 - Let's Encrypt and code-signing certificates 00:20:04 - Install scripts and compatibility 00:25:05 - The search for the wheat color 00:27:34 - Was STRIDE built for a vanished world? 00:30:04 - Threat categories and modeling methods 00:35:19 - Non-deterministic AI and deterministic controls 00:40:15 - Hallucination and cross-context failures 00:45:04 - STRIDE and the Model T analogy 00:50:34 - Tracing code versus explaining model behavior 00:55:46 - Closing assessment Follow AI Security Table: ➜ Home: https://securitytable.ai/ ➜ X: https://x.com/SecTablePodcast ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/ ➜ YouTube: https://www.youtube.com/@AISecurityTable

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Claude Code Said ‘Don’t Ask Again.’ Then It Leaked Your Secrets to GitHub

    Nov 18, 202642 minAudio

    Click “Yes, and don’t ask again” in Claude Code and it saves the exact command you approved, password and all, into a local settings file that keeps turning up in public GitHub repos. We start by admitting we all run...

    Credit the people on this episode

  2. Stop Patching Bugs, Just Rewrite It… Says the Guy Selling the Tokens

    Nov 11, 202650 minAudio

    Cisco's president handed a 27 year old engineer unlimited AI tokens and 24 months to rewrite 98 percent of the company's legacy code, and Sam Altman now says we can no longer just patch all the bugs. Chris sees a step...

    Credit the people on this episode

  3. You Don't Trust AI. So Why Are You Shipping Its Code?

    Nov 4, 202650 minAudio

    Sam Altman told a Stanford audience he no longer thinks we can just patch all the bugs, and the AI Security Table can't agree on whether that is news. Chris argues a swarm of subagents can tear through a repo and drive...

    Credit the people on this episode

  4. Anthropic Ditched Git. Here’s Why Your Agents Will Too

    Oct 28, 202645 minAudio

    Anthropic got tired of Git. With merges jumping from about 2,500 a day in May to more than 30,000 by September, a seven person team built Scion, a centralized, always online source control system designed for agents...

    Credit the people on this episode

  5. Don't Yell at Claude

    Oct 21, 202644 minAudio

    The White House has ordered federal agencies to stop saying AI and start saying Super Intelligence, and the hosts want to know whether anything actually changed overnight. Matt walks through the executive order and the...

    Credit the people on this episode