Persistent AI Coworkers Need Their Own Identities and Access Controls

· Original article ↗

Summary

The article warns that persistent AI agents using human credentials can accumulate excessive access and obscure audit trails. It recommends giving each agent its own identity, owner, scoped access, and defined expiration conditions.

Key points

  • Persistent agents may retain standing privileges, accumulate access across projects, and combine permissions beyond what was intended.
  • When agents act using a person’s credentials, audit logs can attribute their actions to that human rather than the agent.
  • The article says current hosted agent platforms generally do not provide agents with their own credentials; static bearer tokens are not a proper identity model.
  • Recommended controls include discovering unregistered agents through authentication traffic and assigning each persistent agent a distinct identity and human owner.
  • Scope permissions to the agent’s tasks, and define revocation or expiration conditions for events such as an owner leaving or prolonged inactivity.
  • The article notes that some identity vendors offer agent identity features, but those controls are limited to their own platforms.

Article Details

Defense Focus
Govern persistent AI agents as distinct identities rather than allowing them to act with borrowed human credentials, and detect unregistered agents through authentication activity.
Detection Methods
  • Identify unregistered agents by analyzing authentication traffic.
  • Look for OAuth grants, API keys, and login traffic associated with AI agents and MCP servers.
Data Sources
  • Authentication traffic
  • OAuth grants
  • API keys
  • Login traffic
Platforms
  • Entra Agent ID
  • Okta Universal Directory
Defensive Actions
  • Assign each persistent agent its own identity and record a human owner.
  • Scope access to the agent's tasks rather than inheriting the initiating user's permissions.
  • Set lifecycle and deprovisioning conditions, including owner departure and inactivity-based expiration.
  • Use scoped, rotated credentials and provide a revocation path.
  • Review agents that authenticate as humans because their actions may be misattributed in audit trails.

People

Vendors

Products

Related Articles