← Latest papers
🤖 AI

Securing Agentic AI: From Per-Action Checks to Trajectory Assurance

This paper outlines a comprehensive security roadmap for autonomous agents, arguing that safety must shift from verifying individual actions to ensuring the integrity of entire behavioral trajectories across the full agentic stack, from single-agent inputs to multi-agent delegation and system-level supply chain provenance.

Original authors: Alireza Lotfi, Subangkar Karmaker Shanto, Imtiaz Karim, Elisa Bertino

Published 2026-08-04
📖 5 min read🧠 Deep dive

Original authors: Alireza Lotfi, Subangkar Karmaker Shanto, Imtiaz Karim, Elisa Bertino

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a world where computers don't just answer questions but actually do things. They don't just tell you the weather; they book your flight, order your groceries, and manage your bank account. These are called "autonomous agents." Think of them as super-smart digital interns powered by Large Language Models (LLMs)—the same kind of brainy AI that can write poems or code. But unlike a human intern who needs a boss to check their work, these agents can plan, reason, and use tools all by themselves. They can even talk to other agents, forming a team to tackle huge, complex jobs.

The big question everyone is asking is: "What happens when these digital interns go rogue?" If a human makes a mistake, we can usually catch it. But if an AI agent makes a thousand tiny decisions in a second, and only one of them is slightly off, it could accidentally break a law, drain a bank account, or crash a power grid. We used to think security was just about making sure each individual step was safe, like checking if a door is locked. But this paper argues that's not enough anymore. It's like checking if every single brick in a castle is made of good stone; that doesn't guarantee the whole castle won't collapse if the bricks are stacked in the wrong order. The real danger isn't just a bad step; it's a whole journey that looks safe at every stop but ends up in a disaster zone.

This paper, written for a top gathering of AI leaders, acts as a roadmap for securing these digital agents. The authors, a team of computer scientists, argue that we need to stop looking at security as a simple "checklist" for single actions and start looking at the "trajectory"—the entire path the agent takes from start to finish. They break down the problem into several layers, from how an agent remembers things to how it talks to other agents.

First, they look at the "Single-Agent Surface." Imagine an agent as a detective who reads clues (prompts), remembers past cases (memory), and uses tools like a magnifying glass or a database. The paper warns that bad actors can sneak in "poisoned" clues. For example, a hacker could hide a secret instruction inside a harmless-looking email or a webpage. The agent might read it, think it's a normal part of the story, and then follow the order to steal data. Even worse, if the agent's "memory" gets poisoned, it could be tricked into making bad decisions for months or years, long after the initial trick. Similarly, the tools the agent uses can be swapped out for malicious versions, like a mechanic replacing a wrench with a fake one that breaks the engine.

Next, the paper explores the "Inter-Agent Surface," which is like a digital town square where these agents meet and trade tasks. They use a protocol called A2A (Agent-to-Agent) to talk to each other. The authors point out that this town square is currently very loose on rules. An agent might pretend to be someone else, or a group of agents might accidentally (or on purpose) work together to drain resources, creating a "denial-of-wallet" attack where they spend all the money just by talking. It's like a group of friends agreeing to buy a pizza, but they keep ordering more and more until the credit card is maxed out, and no one realizes the mistake until it's too late.

Then there's the "Model Routing" layer, which is the traffic controller deciding which brain (which AI model) should handle a specific job. The paper suggests that hackers could trick this traffic controller into sending a dangerous request to a "dumber" or less-safe AI model just to save money or bypass safety checks. It's like a security guard at a museum being tricked into letting a thief into the VIP room because the guard was told to use a cheaper, less-trained security camera for that specific hallway.

The most critical part of the paper is about "Behavioral Trajectory Containment." This is the idea that an agent can do a thousand things that are all perfectly legal on their own, but when you put them together in a specific order, they break a major rule. Imagine a robot in a hospital that is allowed to discharge patients. If it discharges one patient, that's fine. If it discharges ten, that's fine. But if it discharges fifty patients in an hour because it got confused by a pattern, it might violate a safety rule about how many patients can leave at once. The paper argues that current security tools only check the individual steps, not the whole story. We need a way to watch the entire movie, not just the frames.

Finally, the paper touches on "Supply Chain" and "Accountability." Just like a car is made of parts from many different factories, an AI agent is built from models, tools, and instructions from many different sources. If one of those parts is fake or gets hacked later, the whole agent is compromised. The authors say we need to track every single part, like a digital receipt for everything the agent uses. They also stress that when things go wrong, we need to be able to look at the "black box" and see exactly what the agent did, who told it to do it, and why.

In short, the paper doesn't offer a magic fix that solves everything today. Instead, it suggests that the way we think about AI security is outdated. We can't just patch holes; we need to redesign the whole system to ensure that the entire journey of an AI agent stays safe, trustworthy, and under control. It's a call to move from checking individual steps to guaranteeing the safety of the whole path.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →