Non-human identities. Service accounts, keys, grants and the agents on top of them.
Every AI agent runs as a machine identity, and most of the risk arrives through identities that existed long before the agents did. These pages cover what they are, how they fail and what to change.
Questions, answered.
The basics, in two answers.
What is a non-human identity?
A non-human identity is any identity a machine or workload uses to authenticate and act: a service account, an API key, an OAuth application, a workload identity or an AI agent. It is not a person, it usually has no expiry and it frequently has no named owner.
Why is non-human identity security treated separately?
Because the controls built for staff accounts assume a person. There is no joiner, mover, leaver process for a service account, no single directory that lists every key, and nobody to ask what a credential is for, so reviews stall and permissions only grow.
Other Academy categories.
The same picture from a different starting point.
See what your agents can reach. Before someone else does.
Book a demo and we walk through the access paths in an environment like yours.