TL;DR: AI agents are being framed as autonomous software that can plan and act on their own, and Ory argues that secure digital identity is the missing foundation for accountability, least privilege, and auditability across enterprise workflows. The governing assumption collapses when agents can initiate actions without a stable identity tether, because existing IAM review and logging models were built for human-paced access, not autonomous execution.
Editorial analysis by NHI Mgmt Group, based on content published by Ory: “Digital Identity is the Next Frontier for AI Agents”.
Key questions
Q: What breaks when AI agents are given access without identity governance?
A: What breaks is accountability.
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 are the signs that AI agent governance is too weak for production use?
A: Weak governance usually shows up as poor visibility into what agents can access, incomplete audit trails, and inconsistent oversight across security, legal, compliance, and operations teams.
Practitioner guidance
- Define a separate identity lifecycle for AI agents Issue, sponsor, review and retire agent identities as distinct subjects with named owners, approved purpose and explicit scope.
- Bind each agent to a verifiable sponsor and purpose Record who created the agent, what business function it serves, which version is live and which data model it may use.
- Constrain agent permissions to task-scoped access Use narrow, task-bound entitlements that limit which tools, datasets and actions an agent can reach in a single workflow.
Bottom line: AI agents introduce a governance problem because their actions must remain attributable even when no human approves each step.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Digital identity is the governance baseline for autonomous software: AI agents are no longer best understood as tools that users operate. They are actors that create their own execution paths, so accountability has to be attached to the identity that authorises and records those paths. The practitioner implication is straightforward: if the identity layer cannot name the actor, it cannot govern the actor.
A few things that frame the scale:
- 54% of organisations are actively deploying AI agents across workflows, yet only 21% report a mature governance model for agentic AI.
A question worth separating out:
Q: How can organisations govern AI agents that use service accounts and tokens?
A: Treat those credentials as governed non-human identities with lifecycle controls, not as temporary developer conveniences. That means provisioning them with clear scope, monitoring how they are used, rotating them on a schedule, and removing them when the workflow ends. The goal is to keep the agent’s privilege bounded across its entire operating life.
👉 Read our full editorial: Digital identity for AI agents is becoming the governance baseline