Aller au contenu
Implementa.
← Full glossary

Agent identity

security

agent workload identity · cryptographic agent identity

A cryptographic, verifiable identity assigned to an AI agent (not a person) so other systems know who it is, what it is allowed to do, and for how long — without hardcoded keys.

Agent identity (agent workload identity) answers a question that only shows up once agents run in production: when an agent acts on its own and calls APIs, databases, or other agents, which credentials does it use and who is accountable? Rather than reusing a human API key or a static embedded secret, the agent is given its own verifiable identity via standards such as SPIFFE/SPIRE: the platform issues short-lived, narrowly scoped tokens (only what that agent needs), and when agent A calls agent B the token is exchanged for one scoped to B. It is the basis of zero-trust for agents — every action is attributable, audited, and revocable. It is distinct from observability (what the agent did) and governance (what it is allowed to do): identity is the 'who' that makes attributing and limiting the rest possible.

How it differs from

User authentication
User authentication identifies a person; agent identity identifies an autonomous process acting with no human present that needs its own credentials, not the user's.
API key
An API key is a static, often shared secret; agent identity issues short-lived, action-scoped credentials with no hardcoded keys.

FAQ

Why not just give the agent the team's existing key?
A shared key makes it impossible to know which agent did what, can't be revoked without breaking everyone, and widens the blast radius if leaked. Agent identity issues its own short-lived, least-privilege credentials so every action is attributable and contained.

Related terms

Sources & further reading

Agent identity — Glosario AI Operations · Implementa · Implementa