Topic starter
08/01/2026 12:47 pm
TL;DR: Enterprise AI agents now access corporate data, external tools, and JIT permissions in ways that traditional IAM, PAM, CSPM, and DSPM cannot fully model, according to Veza. The governance gap is no longer hypothetical: effective permissions, data lineage, and MCP-connected tooling now determine blast radius, not just account sprawl.
Editorial analysis by NHI Mgmt Group, based on content published by Veza: “Decoding Identity Security for AI Security Posture Management (AISPM)”.
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 agentic systems increase identity security risk even when IAM is already in place?
A: Because traditional IAM is designed around stable identities and predictable lifecycles, while agents can combine human permissions, their own credentials, and JIT approvals in one run.
Q: How can teams tell whether AI access is actually under control?
A: Look for evidence that access is limited by purpose, not just by account.
Practitioner guidance
- Map agent effective permissions Build a current-state view of what each agent can actually do across data sources, tools, and delegated human rights.
- Classify agent trust paths Inventory every MCP-connected server, external tool, and data pipeline that an agent can reach.
- Separate deterministic and agentic identities Do not govern agents as if they were ordinary service accounts.
Bottom line: AI agents create an identity problem that spans inherited permissions, their own credentials, and runtime tool use, which legacy control models do not fully capture.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 9:15 pm
AI agent identity risk is a control-model problem, not just a new workload category. The article is right to separate agentic systems from deterministic workloads because their permissions change with context, prompts, and task flow. That breaks the assumption that identity can be governed only through stable provisioning states. Practitioners need to treat agent behaviour as an execution-time governance problem, not a static account-management problem.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: What is the difference between human identity governance and NHI governance for AI tools?
A: Human identity governance assumes a person, a manager, and a clear employment lifecycle. NHI governance has to manage credentials, tokens, bots, and agents that can appear instantly, change scope quickly, and outlive the original use case if no one explicitly retires them.
👉 Read our full editorial: AI agent identity risk is outpacing enterprise IAM controls