Skip to main content

People Talk, but Should AI Agents?

Trevor Dearing
Illumio

Artificial intelligence is moving from hype to action, but not all AI is created equal. The current wave of interest primarily focuses on large language models (LLMs) and generative AI tools that create content, summarize data, and automate human workflows. Useful as they are, these systems still depend on people to guide and apply them.

Instead of waiting for prompts, agentic AI can decide on a course of action, connect with other systems, and carry out tasks on its own. That level of independence is already drawing interest from attackers, who are testing ways to use automation and adaptation to gain an edge in cyberattacks.

What Makes AI Agents Different

To understand why agentic AI matters, it is helpful to examine how it differs from other forms of AI.

LLMs are the best-known example. Tools like ChatGPT are massive, general-purpose systems hosted in the cloud. They excel at generating text, answering questions, and summarizing information, but they still rely on humans to prompt them.

Small language models (SLMs) take a different path. They are slimmer, built for specific purposes, and are usually integrated right into the software people already use. A SLM might run a help desk chatbot, analyze network data, or handle routine office processes. They bring AI into daily operations, but only within the boundaries of the application that contains them.

AI agents move beyond these limits by operating independently. They can link actions together, interact with different systems, and follow a task through to completion without constant oversight. For consumers, that might look like booking a dinner reservation or operating a car's controls. In a security setting, it could mean probing for weaknesses, shifting tactics on the fly, or carrying out containment steps.

It is tempting to think of these agents as virtual employees to whom you can assign logins, permissions, and responsibilities. But unlike people, AI agents lack ethics, situational awareness, and accountability. They will follow their programming without pausing to consider context, consequences, or corporate values. Treating them like human team members is not only misleading but also potentially dangerous.

The Risks of "Talking Agents"

One appeal of agentic AI lies in their ability to "talk" to each other and complete tasks without human input. That sounds efficient, but it is also risky. If an agent can connect to external systems, it could inadvertently share sensitive data or execute actions outside its intended scope. Agents should only be allowed to communicate with authorized peers or applications. Segmentation and containment are essential guardrails.

"Poisoning" is another risk that organizations must mitigate. Smaller models that support agents are relatively easy to corrupt. Think of it like adding food coloring to a glass of water, rather than a lake. The impact is immediate and obvious. If attackers insert bad data or manipulate training inputs, they can influence how an agent behaves in unpredictable ways.

Scale adds another layer of complexity. Enterprises could soon be running thousands of agents. Unlike employees, these agents do not tire, but they also lack judgment. Securing and monitoring such a large, fast-moving population will be far harder than managing a workforce of humans.

Finally, there are moral blind spots. Again, autonomous systems may make split-second decisions without any ethical framework to guide them. In business and security contexts, the absence of ethics and accountability can have serious consequences.

Why Security Must Be Different for AI Agents

The unique risks posed by these autonomous systems demand a shift in strategy, one that treats agents as untrusted technologies from the outset and prioritizes segmentation as a foundational safeguard. Segmentation belongs in the same category as patching and multifactor authentication as a core part of basic cyber hygiene that every enterprise should apply.

By confining agents to interact only with approved peers and applications, organizations can block unauthorized access and mitigate the fallout if an agent is compromised or makes a mistake.

Other controls are just as critical. For example, authentication ensures only trusted entities can interact with an agent. Encryption protects the data it handles while continuous monitoring detects unusual activity. Additionally, containment keeps any mistakes or malicious actions from spreading across the environment.

These measures reinforce one another and align with Zero Trust principles. Applying Zero Trust systematically means treating every agent as untrusted until you verify it. Without that discipline, organizations hand too much autonomy to systems that lack human judgment.

Practical Implications

As adoption of agentic AI increases, these systems may eventually control critical infrastructure. An agent might balance an energy grid, regulate water flows, or direct transportation systems and drones. In such environments, a single mistake or compromise could have consequences far beyond the business itself. The stakes will only grow as agentic AI moves into more high-value and high-risk industries.

Another pressing issue is literacy. Most organizations today have only a surface-level understanding of agentic AI. Security professionals urgently need education on the risks and safeguards before adoption accelerates. Without that awareness, companies may deploy agents faster than they can secure them.

Finally, there are lessons to learn from the past. During the early stages of digital transformation, many organizations often added security as an afterthought, resulting in considerable costs. With AI, it’s possible to make the same mistake. That’s why it’s essential to embed security from the beginning, built into every step of the design and deployment process.

Agentic AI is still in its earliest stage. Version 1.0 systems are immature, unpredictable, and prone to vulnerabilities. Organizations cannot afford to assume these agents behave like people or trust them with human-like responsibilities.

Now is the time to build guardrails. Segmentation, Zero Trust principles, and ongoing education are crucial for managing risks before they spiral out of control. By treating AI agents as untrusted technologies and embedding security from the start, enterprises can benefit from their speed and autonomy without exposing themselves to unnecessary danger.

Trevor Dearing is Director of Critical Infrastructure Solutions at Illumio

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

People Talk, but Should AI Agents?

Trevor Dearing
Illumio

Artificial intelligence is moving from hype to action, but not all AI is created equal. The current wave of interest primarily focuses on large language models (LLMs) and generative AI tools that create content, summarize data, and automate human workflows. Useful as they are, these systems still depend on people to guide and apply them.

Instead of waiting for prompts, agentic AI can decide on a course of action, connect with other systems, and carry out tasks on its own. That level of independence is already drawing interest from attackers, who are testing ways to use automation and adaptation to gain an edge in cyberattacks.

What Makes AI Agents Different

To understand why agentic AI matters, it is helpful to examine how it differs from other forms of AI.

LLMs are the best-known example. Tools like ChatGPT are massive, general-purpose systems hosted in the cloud. They excel at generating text, answering questions, and summarizing information, but they still rely on humans to prompt them.

Small language models (SLMs) take a different path. They are slimmer, built for specific purposes, and are usually integrated right into the software people already use. A SLM might run a help desk chatbot, analyze network data, or handle routine office processes. They bring AI into daily operations, but only within the boundaries of the application that contains them.

AI agents move beyond these limits by operating independently. They can link actions together, interact with different systems, and follow a task through to completion without constant oversight. For consumers, that might look like booking a dinner reservation or operating a car's controls. In a security setting, it could mean probing for weaknesses, shifting tactics on the fly, or carrying out containment steps.

It is tempting to think of these agents as virtual employees to whom you can assign logins, permissions, and responsibilities. But unlike people, AI agents lack ethics, situational awareness, and accountability. They will follow their programming without pausing to consider context, consequences, or corporate values. Treating them like human team members is not only misleading but also potentially dangerous.

The Risks of "Talking Agents"

One appeal of agentic AI lies in their ability to "talk" to each other and complete tasks without human input. That sounds efficient, but it is also risky. If an agent can connect to external systems, it could inadvertently share sensitive data or execute actions outside its intended scope. Agents should only be allowed to communicate with authorized peers or applications. Segmentation and containment are essential guardrails.

"Poisoning" is another risk that organizations must mitigate. Smaller models that support agents are relatively easy to corrupt. Think of it like adding food coloring to a glass of water, rather than a lake. The impact is immediate and obvious. If attackers insert bad data or manipulate training inputs, they can influence how an agent behaves in unpredictable ways.

Scale adds another layer of complexity. Enterprises could soon be running thousands of agents. Unlike employees, these agents do not tire, but they also lack judgment. Securing and monitoring such a large, fast-moving population will be far harder than managing a workforce of humans.

Finally, there are moral blind spots. Again, autonomous systems may make split-second decisions without any ethical framework to guide them. In business and security contexts, the absence of ethics and accountability can have serious consequences.

Why Security Must Be Different for AI Agents

The unique risks posed by these autonomous systems demand a shift in strategy, one that treats agents as untrusted technologies from the outset and prioritizes segmentation as a foundational safeguard. Segmentation belongs in the same category as patching and multifactor authentication as a core part of basic cyber hygiene that every enterprise should apply.

By confining agents to interact only with approved peers and applications, organizations can block unauthorized access and mitigate the fallout if an agent is compromised or makes a mistake.

Other controls are just as critical. For example, authentication ensures only trusted entities can interact with an agent. Encryption protects the data it handles while continuous monitoring detects unusual activity. Additionally, containment keeps any mistakes or malicious actions from spreading across the environment.

These measures reinforce one another and align with Zero Trust principles. Applying Zero Trust systematically means treating every agent as untrusted until you verify it. Without that discipline, organizations hand too much autonomy to systems that lack human judgment.

Practical Implications

As adoption of agentic AI increases, these systems may eventually control critical infrastructure. An agent might balance an energy grid, regulate water flows, or direct transportation systems and drones. In such environments, a single mistake or compromise could have consequences far beyond the business itself. The stakes will only grow as agentic AI moves into more high-value and high-risk industries.

Another pressing issue is literacy. Most organizations today have only a surface-level understanding of agentic AI. Security professionals urgently need education on the risks and safeguards before adoption accelerates. Without that awareness, companies may deploy agents faster than they can secure them.

Finally, there are lessons to learn from the past. During the early stages of digital transformation, many organizations often added security as an afterthought, resulting in considerable costs. With AI, it’s possible to make the same mistake. That’s why it’s essential to embed security from the beginning, built into every step of the design and deployment process.

Agentic AI is still in its earliest stage. Version 1.0 systems are immature, unpredictable, and prone to vulnerabilities. Organizations cannot afford to assume these agents behave like people or trust them with human-like responsibilities.

Now is the time to build guardrails. Segmentation, Zero Trust principles, and ongoing education are crucial for managing risks before they spiral out of control. By treating AI agents as untrusted technologies and embedding security from the start, enterprises can benefit from their speed and autonomy without exposing themselves to unnecessary danger.

Trevor Dearing is Director of Critical Infrastructure Solutions at Illumio

Hot Topics

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...