Topic starter
06/06/2026 11:32 am
TL;DR: C1.ai argues that IAM models built for human-speed access are failing as AI agents authenticate at machine speed, inherit delegated authority, and spawn sub-agents that expand access beyond quarterly governance cycles. The old assumption that access can be reviewed after the fact collapses when privileges change and execute within the same session.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “Three Properties Identity Must Have in the Agentic Era”.
Key questions
Q: What breaks when organisations rely on periodic access reviews for AI systems?
A: Periodic access reviews break when the identity scope changes between review cycles.
Q: Why do AI agents increase non-human identity risk?
A: AI agents increase non-human identity risk because they can execute many actions quickly once they inherit a credential or tool permission.
Q: How do security teams know whether an agent identity is actually governed?
A: An agent identity is governed only when teams can identify the owner, locate the credentials, define the allowed scope, and revoke access without hunting across endpoints or backup files.
Practitioner guidance
- Define agent identity as a governed principal class Create a separate governance model for AI agents, including registration, ownership, delegated scope, and revocation responsibility, so agent activity is not hidden inside human account structures.
- Replace calendar-based review with continuous authorization Move from quarterly or annual certification to event-triggered access decisions that can react when an agent's context, task, or downstream delegation changes.
- Map delegation chains to downstream access paths Trace how human approval turns into parent-agent and sub-agent permissions across systems, then document where visibility ends and inherited authority begins.
Bottom line: AI agents expose a structural gap in identity programmes built around human review cycles, because access can be created and consumed before a governance process has any chance to intervene.
What's in the full article
C1.ai's full blog covers the operational detail this post intentionally leaves for the source:
- The full delegation-chain argument showing how parent agents pass authority to sub-agents across systems
- The article's broader market context on why identity infrastructure must be constant, omnipresent, and adaptable
- Specific examples of standards and architectures such as continuous access evaluation and identity fabrics
- The vendor's framing of how platform consolidation is changing the identity control plane
👉 Read C1.ai's analysis of identity control in the agentic era →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 12:23 pm
Access review processes were designed for access that lasts long enough to be reviewed. That assumption fails when the actor is an autonomous agent because privilege can be requested, used, and discarded within the same operating window. The implication is that governance built around quarterly certification is now structurally behind the behaviour it is supposed to control.
A question worth separating out:
Q: How should teams govern access when AI agents and service accounts share the same business systems?
A: Treat them as different identity subjects with the same governance obligation. Create one access model that covers ownership, entitlement scope, review cadence, and offboarding across human and non-human identities, then apply role-appropriate controls to each class. The goal is not separate programmes. It is one risk model that can follow access across systems and workflows.
👉 Read our full editorial: Identity in the agentic era needs constant, omnipresent, adaptable control