Topic starter
06/11/2026 6:38 pm
TL;DR: Agentic AI security governs autonomous agents that can plan, choose tools and act across systems, according to Opti. NHI Mgmt Group's view is that identity governance now has to assume runtime action, not just static access.
Editorial analysis by NHI Mgmt Group, based on content published by Opti: “Agentic AI Security: 7 Key Risks and 10 Essential Controls”.
Key questions
Q: How should organisations govern AI agents as non-human identities?
A: Organisations should classify AI agents as NHIs and place them under the same identity governance controls used for service accounts and APIs.
Q: Why do access reviews miss privilege creep in AI agents?
A: Access reviews miss privilege creep in AI agents when reviewers only see assigned roles or static entitlements, not the tools, prompts, datasets and API scopes the agent actually used.
Q: Why do prompt injection attacks create governance risk for AI agents?
A: Prompt injection creates governance risk because the model often sits in the control path between text input and tool execution.
Practitioner guidance
- Inventory every agent identity Track owner, purpose, authentication method, credentials, connected tools, data sources and lifecycle status for every AI agent in scope.
- Move authorization to the tool layer Enforce allowlists, parameter validation and API-layer checks so runtime tool selection cannot exceed the task that was approved.
- Apply least privilege to agent access Scope each agent to the minimum resources, operations and data needed for its current task, then remove inherited access that is no longer required.
Bottom line: Agentic AI security extends NHI governance into systems that can decide and act during execution, which changes how identity risk has to be measured.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Agentic AI security is NHI governance with a faster blast radius. The control problem is not new, but the runtime decision loop changes the exposure window. An agent can request, combine and use access within a single task, which means the real question is how much authority the identity can exercise before any human checkpoint exists. Practitioners should treat agents as governed machine identities, not as a separate security category.
A few things that frame the scale:
- 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.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams prevent confused deputy attacks in multi-user AI agents?
A: Security teams should enforce authorization at the moment of execution, not at prompt time. Use a runtime that evaluates the agent identity, the delegated user identity, and the task context before each tool call. Keep credentials isolated from the model context window, and require the effective permission to be the intersection of agent and user rights.
👉 Read our full editorial: Agentic AI security extends NHI governance to autonomous agents