Devvret Rishi

speaker

402 appearances 1 recordings 1 series first heard Jul 2026 last heard 7 Jul

Devvret Rishi’s voice in public audio — every appearance, attributed to the second.

Trend

recordings per month · last 12 months

Recordings per month over the last 12 months — 1 in all, peaking in Jul 2026 with 1.

Appearances

newest first · ▶ plays the moment

Eye On A.I. · The Biggest AI Security Problem Isn't the Model. It's This. | Devvret Rishi · 7 Jul 2026 podcast

And so if you're even a smaller organization, but you built some level of like, uh,

IP that you want to make sure that you have some protection around, your database is sensitive.

Certainly this gets more and more relevant as you become a larger organization, you have stake, you're a public company, you're regulated.

But really I think about is anyone who has something to lose and are going to go and unleash agents on that, you'll probably want like a level of protection against it.

And I just want to like underscore, there's a very good reason you unleash agents on the sensitive things that you have something to lose, which is like, that's how they actually ultimately drive productivity in ROI.

But to your second question, which is around like the agent fabric, how does that evolve?

I think that we see this first party inside of Rubrik today, which is a lot of what agents do is they go call another agent.

You know, you have your triage agent, which is like getting maybe a first line support.

And then you have your next step of an agent that's looking to be able to do a resolution or investigation.

I think that the same primitives of how you want to secure and govern agent-to-agent interaction apply from when you're a single agent to a multi-agent workflow, which is that you want to be able to make sure that what's going into each agent and coming out of each agent is something that you have an opportunity to check on.

So if an agent is receiving an input and then giving a route clip to another agent, you want to be able to fly your Barbara's on that input and also that output.

And so then you kind of make sure every node in the graph or every edge connecting those nodes in the graph is secure.

And that's the way we've been approaching as.

Yeah.

And so we can see things like is the agent, you know,

classic example for where this can go wrong, right, is like, agent A doesn't have access to sensitive data, but agent B has access to sensitive data.

And you want to make sure that agent A doesn't actually get and return sensitive data via agent B. So as long as you're running the guardrail on, like, what is agent A getting in this end book?

What is agent A getting as output?

You find Paul's agent B, and you're kind of, like, intercepting that at the point at which we recognize something as sensitive.

Yeah, I think the orchestration layer takes care of making sure that the calls are kind of chained, let's say, correctly, but oftentimes misses the context on what

Showing 241–260 of 402 · page 13 of 21