IT Glossary
AI agent identity gives each autonomous AI agent its own owner, credentials and scopes. How it works and how it differs from a service account.
November 2, 2026
AI agent identity is a type of non-human identity that represents one autonomous AI agent: the named human who owns it, the credentials it authenticates with, the scopes it holds and the systems it can act in. It lets IT and security answer, for every action an agent takes, which agent acted, on whose behalf and with which rights.
Two neighboring terms are often mixed up. Non-human identity is the category that includes service accounts, API keys, workloads and agents. AI agent governance is the program around agents: inventory, risk assessment, approval and review. Protocols are starting to formalize agent access: the MCP authorization specification defines an optional authorization mechanism for HTTP-based transports, based on OAuth 2.1 (an IETF draft) and related OAuth RFCs.
A 150-person marketing agency runs three AI agents: one triages support tickets, one drafts client reports from the CRM and one updates the project tool. All three were connected with the personal API keys of the employee who set them up. When she leaves, offboarding disables her account in the identity provider, but the keys keep working, and nobody can tell which actions the agents took for whom. The fix is one identity per agent, a named owner and scoped, short-lived credentials.
Corma gives IT visibility into shadow AI and the AI tools in use, with their costs, and brings those applications into the same access reviews and deprovisioning workflows as the rest of the SaaS stack, so a departure also removes the person's accounts in those tools.
Yes. AI agents are one kind of non-human identity, alongside service accounts, API keys and workload identities. They stand apart because they decide their own actions.
No, not a shared password or a personal API key. If the agent must act for a user, it should use delegated, scoped tokens, so its actions stay limited and traceable to both the agent and the user.
A named person, usually the business owner of the use case, who answers for the agent's purpose, access and retirement. IT or security sets the rules and reviews them.
Revoke its tokens and keys, delete its OAuth client or workload identity and remove its accounts in connected applications. Do the same when its owner leaves.