Skip to content

Category 1 of 12 · Controls: Who the agent is

Agent identity and credentials

Tools that give each AI agent its own registered identity, owner, and short-lived credentials, instead of letting it run on a shared service account or a static API key.

Mitigates: ASI03 Identity and Privilege Abuse, ASI10 Rogue Agents, LLM06 Excessive Agency · MITRE ATLAS AML.T0053

Vendors, by signal score

Ranked within this category only. How the score works.

Also covers this category

Questions to ask a vendor

  1. Is each agent a first-class identity with a named human owner and a lifecycle?
  2. Are credentials short lived and minted just in time, or stored as static secrets?
  3. Can you revoke every credential one agent holds in a single action?

Go deeper

FAQ

How is agent identity different from non-human identity?
Non-human identity covers every machine credential: service accounts, API keys, certificates. Agent identity is the subset that acts autonomously and on behalf of people, so it also needs an owner, a delegation record, and a way to stop it mid-task.
Why not reuse a service account for an agent?
A shared service account cannot tell which agent or which user caused an action, usually carries standing privilege, and survives the agent's retirement. That is the Identity and Privilege Abuse risk (ASI03) in the OWASP agentic list.