Topic starter
14/08/2026 6:37 pm
TL;DR: Autonomous AI agents can read systems, call tools, move data and change configuration, so Oleria Security argues that prompt-level controls are insufficient and governed identity enforcement has to move to the infrastructure layer. The assumption that access can be granted once and reviewed later collapses when actions are authorised at execution time.
Editorial analysis by NHI Mgmt Group, based on content published by Oleria Security: “Introducing Maestro: Oleria’s Zero Trust Identity Security for AI Agents”.
Key questions
Q: What breaks when autonomous AI agents are governed with prompt-level controls only?
A: Prompt-level controls can shape output, but they do not govern runtime action.
Q: How do organisations reduce risk when an AI agent can act without human approval gates?
A: They move authorisation to the moment of action and keep the agent’s scope task-bound.
Q: What signs show agent governance is too dependent on standing permissions?
A: The warning signs are broad access scopes, delayed review cycles and weak attribution after the fact.
Practitioner guidance
- Define per-action authorisation for agents Scope every state-mutating agent action to the current task and require policy evaluation at execution time, not at provisioning time.
- Separate identity from model safety Treat enterprise agent identity, entitlement context and lifecycle governance as customer responsibilities that sit above the model provider layer.
- Contain agent compromise with isolated execution Use hard execution boundaries so a single compromised agent cannot reach unrelated systems or expand its blast radius across the environment.
Bottom line: Autonomous AI agents turn identity governance into a runtime control problem because they can initiate actions, not just request them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/08/2026 6:43 pm
Zero trust for autonomous agents is an infrastructure problem, not a prompt problem. Autonomous behaviour means the actor can make runtime decisions that a text filter never sees, including tool selection and action timing. That breaks the assumption that prompt governance can stand in for execution governance. The implication is that identity security for agents must be enforced where actions are executed, attributed and contained.
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.
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: Who should own AI agent governance when identity and access are shared across teams?
A: AI agent governance should sit with identity, security, and platform owners together, because no single team sees the full risk surface. IAM owns the control model, security owns containment and monitoring, and platform teams own the runtime integration. Shared ownership matters because agent risk spans identity, policy, and downstream execution.
👉 Read our full editorial: Zero trust identity security for autonomous AI agents