Every AI Agent Is an Identity, but Most Organizations Don’t Treat Them That Way

· Original article ↗

Summary

A sponsored article argues that organizations should govern AI agents as identities by inventorying their access, limiting permissions to their intended purpose, and continuously monitoring their behavior and integrations.

Key points

  • AI agents connected to business systems may use high-privilege credentials to access data, trigger workflows, or make changes.
  • The article says a 2026 CSA survey commissioned by Token Security found 82% of organizations discovered at least one AI agent created without security, IT, or governance teams’ knowledge in the past year.
  • The same survey is cited as finding that 65% of organizations experienced an AI-agent-related security incident in the past year, with 61% reporting sensitive-data exposure or mishandling.
  • Recommended controls include identifying each agent’s owner, users, connected systems, credentials, and permissions.
  • Organizations should align agent permissions with their intended purpose, remove unnecessary access, and rotate or revoke unused credentials.
  • The article recommends continuous governance to detect unexpected credentials, access patterns, or actions as agents and integrations change.

Article Details

Defense Focus
Discover and continuously govern AI agents as identities, managing their access, behavior, risk, and lifecycle.
Detection Methods
  • Discover and inventory agents, including agents unknown to security, IT, or governance teams.
  • Continuously monitor for agents accessing applications outside their normal patterns, using unexpected credentials, or taking actions inconsistent with their stated purpose.
Data Sources
  • Agent ownership and who can invoke each agent
  • Connected applications and systems
  • Credentials used by agents
  • Permissions and capabilities, including what agents can read, write, delete, or execute
Defensive Actions
  • Define each agent’s intended purpose and assess whether its permissions match that scope.
  • Apply least privilege by trimming permissions and remediating overprivileged service accounts.
  • Rotate or remove unused credentials and address risky connections.
  • Maintain continuous governance as agents, instructions, users, and integrations change.

Vendors