Topic starter
02/08/2026 11:51 am
TL;DR: Agentic AI systems can query databases, call APIs, send communications, and compound decisions without human review, creating a broader attack surface than prompt-based GenAI tools, according to Cyberhaven. The core issue is not the model alone but the identity, access, and audit assumptions built into existing security controls, which no longer fit autonomous workflows.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Agentic AI Security Risks: 6 Threats Enterprises Face”.
By the numbers:
- Cyberhaven research found that 39.7% of sensitive data interactions with AI tools involve data employees should not be sharing.
- Cyberhaven says agent adoption grew 276% compared with 2025.
- Cyberhaven says GenAI SaaS adoption grew 82%, highlighting how commonplace AI now is across the enterprise.
Key questions
Q: Why do traditional IAM and DLP controls fall short for agentic AI?
A: Traditional IAM and DLP controls assume risk can be judged at a point in time from one request or one response.
Q: Why do broad agent permissions increase security risk?
A: Broad permissions increase risk because one compromise or misconfiguration can expose many systems at once.
Q: What are the signs that shadow AI is creating governance and compliance gaps?
A: Common signs include limited visibility into who is using AI tools, no reliable audit trail for prompts and outputs, unclear data residency, and inconsistent handling of sensitive information.
Practitioner guidance
- Inventory all active AI agents Map agents across endpoints, SaaS tools, and developer workflows, including unsanctioned deployments, before trying to write policies around them.
- Treat AI agents as non-human identities Assign each agent a named owner, defined purpose, and narrow entitlement set so access is granted to the task, not to the environment.
- Enforce point-of-action data controls Apply policy checks when an agent reads, transforms, or forwards data, because post-event review will be too late for fast multi-step workflows.
Bottom line: Agentic AI changes the security problem because autonomous systems can chain actions across systems without human review, which pushes governance into identity, access, and runtime control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:00 pm
Agentic AI creates an identity governance problem, not just an AI governance problem. The article’s central point is that autonomous systems can make compounded decisions across systems, which means identity controls become the primary security boundary. Once an agent can act, retrieve, and forward data without human approval at each step, IAM must treat the agent as a governed principal rather than a convenience layer.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when autonomous AI touches sensitive data and privileged systems?
A: Contain the workflow first by linking data sensitivity to authorisation, then narrow the agent’s permission scope to the minimum required for the task. Review whether the workflow depends on standing privilege, and replace it with short-lived access, explicit approvals, and tighter monitoring across identity and data controls.
👉 Read our full editorial: Agentic AI security risks expose the limits of current IAM controls