Topic starter
10/06/2026 10:58 pm
TL;DR: Agents are moving from pilots to production, but IAM models built for human sessions cannot reliably govern continuous tool use, delegated actions, and runtime decision paths, according to Cerbos' EIC 2026 analysis. The real control question is no longer inventorying agents first, but deciding what actions they may take at the point where money, data, or production state can move.
Editorial analysis by NHI Mgmt Group, based on content published by Cerbos: “EIC 2026: Stop counting agents, protect what they can touch”.
Key questions
Q: What breaks when IAM relies on human session reviews for agent access?
A: Human session reviews assume access lasts long enough to be observed, certified, and revoked on a schedule.
Q: Why do delegated agent actions create accountability problems?
A: Delegated agent actions can hide which model chose the path, which policy allowed it, and which tool executed it.
Q: How should security teams decide where to place agent authorization controls?
A: Teams should place authorization controls at the point where the action becomes consequential, such as a vault, transfer rail, production record, or sensitive tool call.
Practitioner guidance
- Define vault-class resources first Inventory the tools, APIs, data stores, workflows, and transaction points where agent action creates irreversible impact, then classify those as vault-class controls.
- Move authorization into the runtime path Place policy evaluation where the action becomes real, rather than relying on provisioning, quarterly review, or static role assignment to decide agent access.
- Preserve delegation through each hop Require the agent, delegated human context, policy decision, and outcome to survive every service call so accountability does not disappear at the boundary.
Bottom line: Agent governance is shifting from who exists to what the agent is allowed to do at the point of consequence.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
12/06/2026 4:43 am
Agent authorization is now the primary control plane, not a secondary policy layer. Identity gets an agent into the environment, but authorization determines whether the agent may touch the vault, the transfer rail, or the production record. That shifts control value from inventory and onboarding to decision quality at the moment of action. The practitioner conclusion is straightforward: control the action point, not just the actor list.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between agent identity and agent authorization in AI governance?
A: Agent identity answers who the agent is and who it acts for, while authorization answers what it may do at the moment of each action. Identity gives the agent a managed, accountable presence instead of borrowed credentials. Authorization turns that presence into enforceable control by checking every tool call and producing the audit record that proves what was allowed or denied.
👉 Read our full editorial: Agent authorization for AI systems: what IAM teams must protect
This post was modified 7 days ago by NHI Mgmt Group