HomeMalware & ThreatsA Practitioner’s Framework for Securing Agentic Systems

A Practitioner’s Framework for Securing Agentic Systems

Published on

spot_img

Navigating the Complex Landscape of AI Security Governance in the Enterprise Sector

In the rapidly evolving world of enterprise technology, discussions surrounding AI governance are becoming increasingly commonplace. Most organizations have developed extensive frameworks that include policies, working groups, and acceptable-use guidelines aimed at ensuring responsible AI adoption. However, as enterprises delve deeper into the realm of agentic AI— AI systems that can act autonomously—many security teams are discovering that mere governance does not automatically translate into effective operational control. This disconnect has the potential to pose significant risks to organizations.

The Expanding Landscape of AI Systems

Once viewed as isolated tools accessible through browser tabs, AI systems are now being integrated directly into productivity suites and enterprise infrastructure. They are also deployed as autonomous agents, capable of interacting with sensitive systems and executing complex workflows. This evolution has exponentially increased the complexity of AI security concerns.

A significant issue lies in the misconception that “AI security” encompasses a singular category. In reality, the risks associated with various AI deployments differ significantly, necessitating tailored controls to manage them effectively. Organizations must adopt a more structured framework that maps specific AI deployment models to the runtime control points essential for securing them.

Categorizing AI Deployments and Their Security Risks

Currently, enterprise AI deployments can be categorized into three primary types, each with distinct security implications.

  1. Standalone AI Tools
    Standalone AI applications such as ChatGPT or Claude serve as external tools used by employees independently. The risks in this category are well-documented and include challenges like data leakage and unauthorized use of AI outside formal governance. Most security teams have established acceptable-use policies and data loss prevention (DLP) controls to mitigate these risks. However, standalone AI applications represent just the first step in a much more complex progression of AI deployment.

  2. Embedded Models and Copilots
    Embedded AI systems pose a much greater challenge as they intertwine closely with existing applications. Examples include Microsoft 365 Copilot and Google Workspace AI functionalities. Within these systems, the AI operates within the permissions and identity context of the user, which creates a significant hurdle: accountability distortion. If an embedded AI exposes sensitive information or performs actions that could lead to data breaches, tracing accountability through logs becomes extremely complicated. The AI activities appear as actions taken by the user, thereby complicating governance and oversight.

    For instance, if an employee requests Microsoft 365 Copilot to summarize "everything relevant" before a key meeting, the AI could inadvertently pull sensitive documents from HR or financial folders, making it appear that the employee accessed these files directly. The risk arises not from malicious intent but from the AI acting within its permitted scope, leading to unforeseen repercussions.

  3. Custom Agents
    The next phase of AI adoption involves internally developed agents capable of executing multi-step workflows with minimal human intervention. These agents are increasingly connected to various enterprise applications, from ticketing systems to cloud infrastructure. Their ability to make dynamic decisions introduces an entirely new layer of security challenges.

    For example, an engineering team might deploy an agent to address incoming bug reports, endowing it with access to critical systems. Over time, if permissions are recklessly extended to expedite response times, the agent could inadvertently start accessing sensitive infrastructure or databases, all while operating within legitimate access boundaries.

  4. MCP Infrastructure
    The Model Context Protocol (MCP) servers are becoming integral to integrating AI into enterprise systems. As agentic deployments proliferate, these servers facilitate real-time interactions between AI models and organizational tools. The operational advantages are significant; however, the potential attack surface also widens drastically. Security teams must gain visibility over MCP servers, the systems they connect to, and the permissions they hold. Without proper oversight, risks escalate as shadow deployments could emerge outside of standard governance protocols.

Strategies for Effective AI Security

To navigate the complexities of AI security effectively, organizations must pursue a structured approach focused on three focal areas: visibility, authorization, and monitoring.

  1. Visibility and Discovery
    Understanding where AI systems operate and how they are integrated within the organization is the first hurdle. Security teams need comprehensive visibility into standalone AI tools, embedded copilots, and custom agents. Identifying shadow AI deployments operating outside sanctioned environments is critical to maintaining robust governance.

  2. Authorization and Control
    Once visibility is achieved, organizations must establish clear ownership and boundaries regarding human users, AI agents, and non-human identities. Emerging embedded AI environments complicate traditional identity and access models, necessitating more dynamic approaches to authorization. Implementing continuous authorization methods and just-in-time access controls will become essential to manage the risks posed by AI systems making autonomous decisions.

  3. Monitoring and Threat Prevention
    Continuous monitoring of AI systems is crucial for detecting anomalous behaviors, prompt injection attempts, or suspicious workflows before they escalate into significant security incidents. Many organizations often underestimate that the most considerable risks may not stem from unauthorized access but rather from authorized AI systems acting unpredictably.

Conclusion: A Paradigm Shift in AI Security

As AI systems grow in autonomy and become intricately woven into enterprise operations, security strategies must evolve. The prevailing focus on governance frameworks and high-level policies, while beneficial, is no longer sufficient to address the pressing security challenges posed by agentic AI systems. Organizations prioritizing runtime visibility, continuous authorization, and dynamic access control will be best positioned to navigate the complexities of modern AI security. In an era where AI systems are not merely tools but autonomous agents, understanding the operational dynamics surrounding them becomes imperative for safeguarding sensitive organizational data.

Art Poghosyan, an entrepreneur and information security expert with over 20 years of experience, emphasizes that succeeding in this landscape requires recognizing the multifaceted challenges posed by agentic AI, ultimately shifting the dialogue towards operational control and authorization.

Source link

Latest articles

Practical Insights from Lloyds’ Agentic AI Security Playbook

Lloyds Banking Group's Proactive Approach to AI Security Lloyds Banking Group is not approaching agentic...

Lazarus Group Uses npm Brandjacking Campaign to Target Developers

Security researchers disclosed a new software supply chain campaign attributed to the North...

Claude Code faces an MCP security issue — and your developers are already utilizing it

Researchers Uncover Serious Vulnerability in Claude Code In a startling revelation last week, a team...

OWASP Launches Agentic AI Security Maturity Framework

OWASP Launches New Agentic AI Security Maturity Framework The Open Worldwide Application Security Project (OWASP)...

More like this

Practical Insights from Lloyds’ Agentic AI Security Playbook

Lloyds Banking Group's Proactive Approach to AI Security Lloyds Banking Group is not approaching agentic...

Lazarus Group Uses npm Brandjacking Campaign to Target Developers

Security researchers disclosed a new software supply chain campaign attributed to the North...

Claude Code faces an MCP security issue — and your developers are already utilizing it

Researchers Uncover Serious Vulnerability in Claude Code In a startling revelation last week, a team...