Virtual Event: Threat Detection & Incident Response Summit - Watch Now
Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Artificial Intelligence

Rethinking Security for Agentic AI

When software can think and act on its own, security strategies must shift from static policy enforcement to real-time behavioral governance.

Prompt Engineering

Artificial intelligence has already transformed how enterprises operate, but the next wave of innovation, agentic AI, operates as autonomous or semi‑autonomous agents that can run code, interact with APIs, access databases, and make decisions on the fly. Organizations need to take immediate measures against security threats that can occur when software systems transition from producing passive text output to performing active operational tasks.

From Prompt‑Driven AI to Action‑Driven Agents

Organizations started their enterprise AI adoption with a focus on productivity gains. They incorporated LLMs into workflows to write documents, summarize data, and answer questions. Security issues centered on the misuse of prompts, data leaks, and privacy breaches. Though serious, organizations could manage these risks through standard security protocols which monitor input and output data and perform policy management and system surveillance.

Agentic AI shifts the equation. More than just responding to queries, agents act for users or themselves. They can trigger workflows, interact with sensitive systems, and even make decisions independently. As autonomy increases, so does the risk of harm. This makes it important to rethink security from the basics.

The New Risk Landscape

Agentic AI introduces several new security threats:

  • Action‑Level Exploits: Bad actors can deceive agents into carrying out dangerous operations that modify production databases or reveal unauthorized data.
  • Context Injection Attacks: Attackers feed false information to RAG systems (retrieval augmented generation), which triggers dangerous agent actions.
  • Invisible Operations: Agents often operate quietly behind the scenes, which makes it hard to notice what they are doing without strong monitoring.
  • Protocol Vulnerabilities: Standards such as the Model Context Protocol (MCP) help agents connect and work together more smoothly, but because they often start with overly open settings, they can accidentally leave systems vulnerable.

Recent attacks highlight the pressing need for action. For example, hackers compromised Amazon Q code assistant with a wiper‑style prompt injection. At the same time, researchers have disclosed vulnerabilities such as EchoLeak and CurXecute that exploit what they call the “lethal trifecta”: access to internal data, the ability to communicate externally, and exposure to untrusted inputs. Most agents require these three attributes to function effectively, making them highly exploitable. These cases demonstrate how agentic AI systems can be manipulated in ways that traditional LLM security frameworks were never designed to handle.

Building Guardrails for Autonomy

The challenge is finding the right balance between an agent’s usefulness and its safety. To minimize the risk, enterprises have to put in guardrails that trace the full chain of thought and actions executed by agents. This means monitoring the tool calls, intent verification, and application of contextual controls. Importantly, prevention strategies must work across platforms. Instead of focusing on a specific LLM, the emphasis should be on how agents interact with systems and manage data.

Developing an Agent Taxonomy

One important step in securing agentic AI is creating a taxonomy of agents. Not all agents are the same. Categorizing them will help prioritize controls. What really matters here is:

Advertisement. Scroll to continue reading.
  • Initiation: Human-initiated vs. autonomous agents;
  • Deployment: Local machines, on SaaS platforms, or in self‑hosted setups;
  • Connectivity: Internal APIs, third-party endpoints, or MCP servers;
  • Autonomy and Trust: What level of access agents have, and whether they should have it.

For instance, a local coding assistant in a development environment is far less risky than a background agent running inference across production systems. By listing agents and endpoints, security teams can monitor activity, evaluate posture, and apply precise controls.

Deterministic vs. Dynamic Security Approaches

Traditional LLM governance relies on deterministic controls: predefined policies restrict what the model can and cannot do. In contrast, agentic AI requires a dynamic approach. Because agents leverage reasoning, inference, and probabilistic decision‑making, they may behave in unexpected ways. For this reason, security frameworks must combine deterministic guardrails with real-time observability and adaptive controls.

Instead of simply blocking harmful queries, enterprises must map agent behavior proactively, validate intent, and control execution. This proactive process of governance is fundamental to handling the unpredictability of autonomous systems.

Toward an Agentic AI Security Framework

To address these challenges, organizations need a security approach with four main components:

  1. Discovery and Profiling: Build an inventory of agents, their lineage, and how they connect to systems.
  2. Agentic Posture Management: Assess risks by looking at the tools that agents use, the data they can access, and the identities they take on.
  3. Observability: Set up detailed logs and traces of agent actions so governance teams have clear visibility.
  4. Runtime Controls: Implement contextual risk monitoring, exploit prevention, and role-specific action controls.

This framework recognizes that each agent must be assessed in context, with controls adjusted to its autonomy, environment, and blast radius.

Redefining Enterprise AI Risk

The rise of agentic AI is a major shift. Enterprises are no longer just protecting data. They are managing flows of autonomous software that can act on their own. This changes the very notion of threat models, attack surfaces, and security strategies to contextual, adaptive, and real-time.

Unlike conventional LLMs that simply generate text in response to prompts, the independent nature of agentic AI redefines both opportunity and risk. Organizations that accept this new responsibility must rethink their security measures. They need to go beyond traditional protections and develop frameworks that anticipate, monitor, and control autonomous actions.

Related: Follow Pragmatic Interventions to Keep Agentic AI in Check

RelatedThe Wild West of Agentic AI – An Attack Surface CISOs Can’t Afford to Ignore

RelatedBeyond GenAI: Why Agentic AI Was the Real Conversation at RSA 2025

Written By

Etay Maor is Vice President of Threat Intelligence at Cato Networks, a founding member of Cato CTRL, and an industry-recognized cybersecurity researcher. Prior to joining Cato in 2021, Etay was the chief security officer for IntSights (acquired by Rapid7), where he led strategic cybersecurity research and security services. Etay has also held senior security positions at Trusteer (acquired by IBM) and RSA Security’s Cyber Threats Research Labs. Etay is an adjunct professor at Boston College and is part of the Call for Paper (CFP) committees for the RSA Conference and Qubits Conference. Etay holds a Master’s degree in Counterterrorism and Cyber-Terrorism and a Bachelor's degree in Computer Science from IDC Herzliya.

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Delve into big-picture strategies to reduce attack surfaces, improve patch management, conduct post-incident forensics, and tools and tricks needed in a modern organization.

Register

Organizations are investing heavily in third-party risk management, but breaches, delays, and blind spots continue to persist. Join this live webinar as we examine the gap between how organizations think their third-party risk programs are performing and what’s actually happening in practice.

Register

People on the Move

Joe Chen has become Chief Technology Officer at Trellix.

Usercentrics has named Pawan Hegde as COO and Elena Ignatova as CPTO.

SecureAuth has named Mark van Oppen as Chief Revenue Officer.

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.