We're used to thinking of AI as a tool that answers questions or generates text. However, over the past couple of years, the landscape has changed significantly: more and more systems are being built on so-called agents – programs that don't just respond, but act. They initiate tasks, query external services, make multi-step decisions, and often operate autonomously, without human intervention at every stage.
This convenience brings with it a new, more pressing question: who is monitoring what these agents are doing? And what happens if something goes wrong?
A standard chatbot is limited: it receives a query, generates a response, and that's it. Agentic systems are designed differently. An agent can access data, perform an action, hand off control to another agent, and re-check information – all within a single task.
Simply put, the more steps and the more autonomy involved, the more points there are where something can go wrong. This doesn't mean agentic AI is inherently dangerous; it means it requires a different approach to security.
This is precisely the focus of Microsoft's announcements at the RSAC 2026 conference.
Three Pillars, One Logic
Microsoft has articulated its approach to agentic AI security through three objectives: protecting the agents themselves, securing their foundation (i.e., the data, models, and infrastructure they run on), and using agents as a security tool – that is, applying AI to detect and respond to threats.
These are not three separate products; rather, it is a logic intended to permeate an organization's entire AI infrastructure. Security isn't an afterthought; it's built-in at every level.
When the Agent is Both an Attack Target and a Potential Source of Risk
Agents, like any software, can be vulnerable. They can be manipulated through input data, coerced into performing unwanted actions, or used as an entry point into the broader infrastructure.
One of the new capabilities Microsoft presented is protecting agents from 'prompt injection attacks.' This occurs when malicious data fed to an agent from an external source (like a document or a web page) contains hidden commands that the agent might inadvertently execute. This type of threat is specific to agentic systems and was virtually nonexistent in the era of simple chatbots.
In addition, tools are emerging to control what an agent is actually permitted to do: what data it can access, what actions it can perform, and which external services it can interact with. This is similar to the principle of least privilege, a long-standing concept in classic cybersecurity, but adapted for agentic scenarios.
The Foundation Also Needs Protection
An agent is only as reliable as the environment it operates in. If the model it's based on is compromised, or if the data it accesses contains something malicious, no amount of control over the agent's behavior will help.
Therefore, special attention is being paid to protecting the AI models and data themselves: monitoring how models are used, detecting anomalies in their behavior, and controlling what data goes into the training processes or becomes accessible to agents during their operation.
In short: it's not enough to protect what the agent does. You also need to protect what it's made of and what it runs on.
AI as an Ally in Defense
The third pillar is perhaps the most conceptually interesting. Microsoft is betting not only on protecting AI systems but also on using them to protect everything else.
Agents tailored for security tasks can monitor infrastructure, identify suspicious activity, prioritize incidents, and even suggest response options – and do it faster than a human team physically can.
This isn't a replacement for security specialists but rather an enhancement: the agent takes on the routine work – sifting through a vast stream of events – while the human focuses on decisions that require context and judgment.
Why This Matters Right Now
Agentic AI is no longer an experimental concept. Organizations are already building real-world workflows on it today: automating operations, handling customer support, and creating internal assistants with access to corporate data. The more widespread agents become, the more pressing the question: has security been properly thought through?
Historically, security often plays catch-up after a technology has already become widespread. RSAC 2026 is a signal that at least part of the industry is trying not to repeat that mistake.
No system is ever completely secure, and agentic AI is no exception. However, the difference between 'security built-in from the start' and 'security bolted on later' is fundamental. And it's precisely on this distinction that Microsoft is building its position in the new AI landscape.