Identity & Access · Chapter 7
Machine and agent identity
Non-human identities already outnumber humans. AI agents are about to make that worse — and it is becoming a job title.
Every service account, CI runner, container, function and API client is an identity. In most organisations these already outnumber human identities by a wide margin, and they are governed far more weakly: no HR record, no joiner-mover-leaver, no manager to review them, frequently no owner and no expiry.
Why AI agents sharpen this
An AI agent is a non-human identity that acts unpredictably and can be influenced by the content it reads. Every existing weakness in machine identity becomes materially more dangerous, because the classic assumption — that a service account does one predictable thing — no longer holds.
- Agents need their own identity, not a borrowed one. An agent using a shared service account is unattributable: you cannot tell which agent, which user's request, or which run took an action.
- They should act on behalf of the requesting user, scoped per request, rather than holding standing authority. This is the confused-deputy problem, and delegation — OAuth token exchange, on-behalf-of flows — is the established pattern.
- Time-bound and task-bound. Credentials for the duration of the task, not the lifetime of the service.
- Every tool call attributable to an agent identity, a run, and an initiating human. Without that you cannot investigate.
This is now a hiring signal, visibly
In the postings behind this atlas the identity vendors are already advertising for it directly — “Forward Deployed Engineer, Okta for AI Agents”, “Product Manager, Identity for AI”, “Software Engineer, Identity for AI”. Non-human identity has moved from a hygiene topic to a product category inside about two years.
If you already know identity and you learn the AI material in the other books here, you are positioned for a specialism that barely has practitioners yet. That combination is rare on purpose — almost nobody has both halves.