Craig Thomas
speaker
382 appearances
2 recordings
1 series
first heard Jun 2026
last heard 8 Jul
Craig Thomas’s voice in public audio — every appearance, attributed to the second.
Trend
recordings per month · last 12 monthsRecordings per month over the last 12 months — 2 in all, peaking in Jul 2026 with 1.
Appearances
Yeah, great to be back.
I know last time we talked about rogue AI, so excited to dive in deeper about the threats and how to solve some of the AI problems today.
Yeah, great question, Noah.
First of all, just kind of like the frame, this whole discussion, right, that traditional security really was built to answer one question.
Who gets access?
Firewall rules, identity access policies, network segmentation, all of it's fundamentally controlling the gate.
But AI has to move that problem past the gate.
And so you asked about detect and respond systems.
Traditional IR assumes a human attacker moving at human speed.
You have time to detect, triage, contain that attack.
But as we talked about before in some of the other episodes, AI compresses that timeline dramatically.
A model can exfiltrate, manipulate corrupt data in milliseconds versus hours, days, or even weeks.
And so this incident with AI may not look like an incident, looks like normal API calls, normal outputs and traffic.
I like to think about it, about how incident response was designed.
Traditionally, someone breaches the perimeter, they move laterally out over hours, days, weeks, your SIM fires an alert, SOC analyst opens a ticket.
That mental model all assumes time.
AI just doesn't give you that time anymore.
And so if that prompt injection or that attack causes your AI agent to start dumping customer records to an external endpoint, that loop closes in seconds.
So by the time your SIM would normally fire, the data's already gone.
And detect and respond built for a world where attackers are slower than defenders.
Showing 1–20 of 382 · page 1 of 20
Next →