IBM announced new identity and access controls for AI agents at TechXchange on 27 October. Agent Identity, used with HashiCorp Vault, is designed to record who owns an agent and what authority it has, while limiting the credentials it uses to reach business systems.
The practical distinction is between recognising an agent and authorising its actions. A verified identity does not by itself justify access to every database or application. Short-lived credentials and defined permissions are intended to narrow both what an agent can do and how long that authority remains valid.
The company also announced tools for discovering and containing agents across platforms. Those discovery and containment capabilities are in technology preview; they should not be described as generally available production features. Agent Identity and Vault 2.2 are among the capabilities IBM lists as generally available.
These are vendor announcements, not independent proof that a deployment cannot be compromised. Their value depends on how organisations define roles, configure permissions and monitor use. An agent given excessive authority can still create risk even when its identity is correctly recorded.
For companies moving from chatbots to agents that execute tasks, this is a substantive governance question. The decision is no longer only what an AI system can answer, but which actions it may take, on whose behalf, and how that permission can be withdrawn. Clear limits and an audit trail become part of the deployment itself.
