Topic starter
10/07/2026 9:10 pm
TL;DR: Agentic AI systems now connect to live data, workflows, and permissions, which expands the attack surface through prompt injection, poisoned data, excess permissions, silent misconfigurations, and over-trust, according to Illumio. The central issue is that autonomous action turns trust into a liability unless identity and containment controls constrain it continuously.
Editorial analysis by NHI Mgmt Group, based on content published by Illumio: “Agentic AI Security: How Illumio and Netskope Help You Adopt It Safely Without Trusting It Blindly”.
Key questions
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Q: Why do prompt injection and poisoned data matter more in agentic AI than in passive AI tools?
A: Because agentic systems can convert altered instructions into operations.
Q: How do security teams know if agentic AI controls are failing?
A: The main signs are session drift, repeated retry loops, unauthorized tool calls, and behaviour that diverges from the documented task sequence.
Practitioner guidance
- Define agent privilege boundaries before deployment Map each agent to the exact data stores, tools and workflows it may reach, then remove every permission that is not required for the target task.
- Constrain tool interactions at the gateway Inspect model context and agent-to-tool traffic so instructions, prompts and outbound actions can be blocked or scored before they trigger downstream systems.
- Segment workloads that host or serve agents Separate agent runtimes from surrounding applications and data paths so a compromise in one agent cannot laterally reach adjacent services.
Bottom line: Agentic AI turns software into a governed actor because it can make decisions, use tools and trigger actions against live systems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:33 pm
Agentic AI creates an identity problem, not just an AI safety problem: once software can choose actions and trigger workflows, the control plane must govern runtime authority rather than static assignment. Prompt injection, poisoned inputs and over-trust all matter because they steer an identity that can already act. The practitioner takeaway is that agent governance belongs in IAM, PAM and NHI operating models, not beside them.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between securing the agent interaction layer and the infrastructure layer?
A: The interaction layer governs what the agent can request, send or trigger through tools and external services. The infrastructure layer governs what workloads, applications and data paths the agent can reach once it is inside the environment. Both matter, because failure in one layer can undermine the other.
👉 Read our full editorial: Agentic AI security expands the identity attack surface and control gap