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
It's supposed to do A and B, but now it's doing C, right?
Or it's supposed to have read access only, but now it's making write and delete calls.
You should be able to see and stop that immediately.
Another one similar to what we've looked at for APIs for a while, we've looked at even WAFs and DDoS, right?
Rate anomalies.
If you have sudden spikes in query volume, especially to sensitive systems, that suggests the agent's being used as a proxy, and so you need to be able to detect and block that.
And then traditional security perspective lateral movement.
If you have one agent accessing credentials or contacts intended for a different agent, now you certainly have a problem, and you need to be able to see that and block it pretty quickly.
for too often that a lot of organizations, the security organization is operated kind of outside the bounds of, or outside the parameters that we ask developers to do.
So I'd start with policy as code.
Those enforcement rules can live in version control right alongside the agent code.
They're reviewed in your CI CD pipeline before reaching production.
So take a similar approach you're taking to code with policy as well.
Observe before enforce, right?
That crawl, walk, run approach.
Start in audit mode.
Understand the baseline behavior before writing those blocking rules.
This helps avoid false positives at slow development.
But then you have to come back to it.
You have to move to enforce.
Showing 121–140 of 382 · page 7 of 20
← Previous
Next →