Agent Identity
Giving an AI agent its own credential and audit trail instead of letting it borrow a human’s.
What is agent identity?
Agent identity means an AI agent authenticates as itself — its own principal, its own scoped credential, its own audit trail — rather than reusing the credentials of the person who started it. Every action it takes is attributable to that agent, and its permissions are the ones the agent needs rather than the ones its operator happens to have.
The default today is the opposite. An agent runs with a developer's Git token, their cloud profile and their shell. It can do everything they can do, and in the audit log it *is* them: there is no way, after the fact, to distinguish an action the person took from one the model decided to take.
How it works
Three properties, and an agent identity is not one without all three:
- 01
A distinct principal
The agent gets its own service identity, not a copy of a human's session. Every request it makes is stamped with that identity.
- 02
Scoped to the task
Permissions are the union of what this agent's tools actually require — see capability scoping — not whatever its operator holds. A code-review agent needs read on one repository, not write on every repository.
- 03
Short-lived and revocable
Credentials expire on the order of the task, not the employment relationship, and a single agent can be revoked without disturbing anyone's login.
Why it matters
Borrowed credentials break accountability, which is the property every other control depends on. If the log cannot separate the human from the agent, then incident review, access review and compliance evidence are all built on an ambiguity.
They also break least privilege in the most expensive direction. An agent inherits its operator's full permission set, which for an engineer is usually broad. A prompt injection or a poisoned tool description then executes against all of it — the injection did not need to escalate, because the privilege was already there.
And revocation becomes coupled to people. When the only way to stop a misbehaving agent is to disable the account it borrowed, the response to an agent incident is to lock out an employee.
What value it adds
Attribution
"Which agent did this, on whose behalf, with what scope" becomes answerable from the log alone.
Real least privilege
Permissions match the task, so a compromised agent reaches what its tools reach and nothing more.
Independent revocation
Kill one agent without locking anyone out.
Reviewable access
Agents show up in access review as principals, which is the only way over-scoped ones get noticed.
Auditable exceptions
When an agent genuinely needs more, a break-glass workflow makes the grant explicit and time-boxed.
How Safeguard uses it
Safeguard issues agents their own identities with scoped, expiring credentials, and records every action against the agent rather than its operator. See Portal and the AI governance workflow.
Stop agents borrowing your engineers’ credentials.
Safeguard gives every agent its own scoped, expiring identity and an audit trail that names it.
Self-healing security runs on Safeguard.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.