Agent identities are the new service accounts
说明与用途
AI 代理使用的服务账户管理流程包括清点、指派所有者、最小权限、密钥轮换以及使用 agent-off-switch 工具自动禁用身份。
问题
Service accounts, especially those used by AI agents, are hard to govern: they lack owners, are not recertified, and cannot be stopped quickly, leading to potential identity and privilege abuse.
结果
Implemented a repeatable process that inventories all non-human identities, flags ownership gaps, enforces least privilege, rotates or removes long-lived credentials, and provides an automated off-switch to stop identities safely.
工作流
- Run
aos reviewto inventory identities and identify findings - Use
aos offto generate an ordered runbook for disabling an identity - Execute each change command in order, then run the verification commands
- Record time and person for each step
- Use
aos driftto detect new or changed identities between inventories and review them
证据
The pattern I keep seeing has three parts. Nobody owns the list. Nobody recertifies it. And when something goes wrong, nobody can stop one of these identities quickly and prove it is stopped.
An ownerless identity with a tenant-wide Graph application permission.
The off switch is aos off. It prints an ordered runbook and runs nothing.
aos review examples/demo-tenant --as-of 2026-10-09 – Agent access review As of 2026-10-09: 13 non-human identities, 11 look like agents.
- 记录日期: 2026-10-16T08:41:14.513Z