Notifications
Clear all
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 argues they need governed identity, per-action authorization, isolation, and auditability at the infrastructure layer, not prompt-level controls. The key assumption that breaks is that access can be granted once and reviewed later; agentic execution collapses that review window.
NHIMG editorial — based on content published by Oleria Security: zero trust identity security for autonomous AI agents
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
Q: How should security teams govern semiautonomous AI agents before they go live?
A: Start with task-scoped permissions, explicit credential lifecycles, and human oversight points before deployment volume makes retrofits impractical.
Q: Why do autonomous AI agents change least privilege requirements?
A: Autonomous agents change least privilege because their access cannot be assumed to stay fixed for the full life of a session.
Q: What do security teams get wrong about auditability for AI agents?
A: Teams often treat auditability as a logging requirement when it is actually the proof that human intent still survives delegation.
Practitioner guidance
- Map the agent governance boundary Define which controls belong to the model provider and which controls remain the enterprise’s responsibility, including identity, authorisation, secure runtime, and audit evidence.
- Replace standing agent access with per-action policy Scope every meaningful agent action to a specific task, require just-in-time approval for state-mutating operations, and deny by default when the task boundary is unclear.
- Build containment into the agent runtime Use isolation, segmented execution, and explicit trust boundaries so a compromised agent cannot inherit privilege across a fleet or trigger broad downstream effects.
What's in the full article
Oleria Security's full post covers the operational detail this analysis intentionally leaves for the source:
- The full responsibility split between the enterprise and the AI platform provider for agent identity and runtime control
- The Maestro operating model for per-action authorisation, isolation, and recorded rationale in autonomous agent workflows
- The Trustguardian identity layer and Trustfusion context model that underpin governed agent execution
- The platform architecture details behind proof of attention, multi-agent routing, and controlled restart
👉 Read Oleria Security's analysis of zero trust identity security for autonomous AI agents →
Autonomous AI agents and identity controls: what changes now?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
14/08/2026 6:43 pm
Autonomous agents invalidate the assumption that access can be reviewed after it is granted. Access review cadences were designed for identities whose privileges persist long enough to be observed, recertified, and removed. That assumption fails when an autonomous agent can acquire, use, and discard authority inside a single task cycle. The implication is not that reviews become stricter, but that the governance model itself has to change.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: Who should own AI agent governance in the identity stack?
A: Ownership should sit with identity and security teams together, because agent governance spans access policy, audit, lifecycle, and platform integration. It cannot live only in application teams or only in infrastructure operations. The right model is shared accountability with a single control plane for policy and revocation.
👉 Read our full editorial: Zero trust identity security for autonomous AI agents
