Topic starter
26/08/2026 11:51 am
TL;DR: AI agents are being granted broad delegated access through OAuth-style trust models that were designed for static software, not runtime decision-making, according to Cakewalk’s analysis. The core failure is assumption collapse: access reviews and signup-time consent do not govern agents that act dynamically across human, agent, and system boundaries.
Editorial analysis by NHI Mgmt Group, based on content published by Cakewalk: “Human â Agent â System: A Working Model for Governing Agent Access”.
Key questions
Q: What breaks when AI client access is governed only by per-app OAuth consent?
A: The IdP cannot see or centrally revoke the relationship between the AI client and the target tool.
Q: Why do agentic systems create accountability problems for identity teams?
A: Because the decision chain is no longer a simple request and approval flow.
Q: How should security teams enforce least privilege for AI agent identities?
A: Start by treating every agent as an NHI with a dedicated identity, a tight permission boundary, and a named owner.
Practitioner guidance
- Map delegated agent access paths Inventory where users can grant agents access to data, tools, and downstream systems, then document which grants persist beyond the original session or task.
- Move policy checks to runtime Require each agent tool call to be evaluated against the delegating human, the requested action, and the target system before execution.
- Separate agent tokens from the agent context Keep credentials in a separate vault and revoke them at session end so a compromised context window cannot expose reusable secrets.
Bottom line: AI agent access exposes a mismatch between static consent models and runtime behaviour, which makes traditional access governance too coarse for delegated actions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
26/08/2026 11:51 am
Static consent is the wrong governance unit for agent access: OAuth-style authorisation was designed for software that behaves within predefined bounds, not for actors that reinterpret context at runtime. Once an agent can change what it does, the original consent no longer describes the access in use. The implication is that identity programmes must stop treating signup-time approval as the control boundary for agent actions.
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.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between human consent and runtime authorisation for agents?
A: Human consent is the initial approval to let an agent act, while runtime authorisation is the live decision that a specific action is allowed now. For agents, the distinction matters because the original approval can be valid and still insufficient once context, target system or scope changes during execution.
👉 Read our full editorial: Human, agent and system: the governance gap in AI access