Notifications
Clear all
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.
NHIMG editorial — 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.
- Agentic AI adoption grew 276% compared to 2025.
- GenAI SaaS adoption grew 82%, highlighting how commonplace AI now is across the enterprise.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents increase blast radius compared with prompt-based GenAI tools?
A: AI agents can chain retrieval, transformation, communication, and archival across multiple systems without human review between steps.
Q: What do financial institutions get wrong about shadow AI discovery?
A: They often assume discovery alone is enough, but visibility without interaction-level auditability leaves a gap between detection and proof.
Practitioner guidance
- Inventory all AI agents and agentic workflows Create a complete register of agents running in endpoints, SaaS environments, and developer toolchains.
- Scope each agent to task-specific access Grant only the data sources, APIs, and communication endpoints required for the agent’s intended function.
- Move policy enforcement to the point of interaction Apply controls where the agent retrieves data, invokes APIs, or forwards outputs, rather than relying only on downstream DLP and log review.
What's in the full article
Cyberhaven's full article covers the operational detail this post intentionally leaves for the source:
- The vendor's breakdown of six specific agentic AI failure modes and how each one manifests in enterprise workflows.
- Implementation-oriented examples of how AI agents interact with endpoints, SaaS platforms, and developer toolchains.
- The platform description for data lineage, content inspection, and endpoint visibility in AI workflows.
- The FAQ-style explanations that map agentic AI risk to day-to-day security operations.
👉 Read Cyberhaven's analysis of six agentic AI security risks →
Agentic AI security risks: are your identity controls keeping up?
Explore further
02/08/2026 1:00 pm
AI agents are becoming a governance category, not just a tooling category. The article shows that the enterprise risk is no longer limited to prompt misuse or content leakage. Once an agent can decide when to query, what to retrieve, and how to forward outputs, identity governance has to cover software entities with persistent authority. That shifts the control conversation toward NHI lifecycle management, entitlement scope, and auditable delegation.
A question worth separating out:
Q: How should organisations prove that AI agents are following policy?
A: They should prove it with identity-linked evidence, not with policy text or system prompts. The minimum control set is an authorization record, execution logs tied to a specific principal, and device or runtime context. That combination lets auditors reconstruct what happened and who owned the action when the agent made a decision.
👉 Read our full editorial: Agentic AI security risks expose the limits of current IAM controls
