IBM Agent Identity and Vault 2.2: AI agents get owners, not keys

IBM just made AI agent identity a product line. At TechXchange 2026 in Atlanta today, IBM announced Agent Identity and HashiCorp Vault 2.2, both generally available. They give every AI agent its own secured account, a named owner, credentials that renew on their own, and a revoke switch. The IBM release is written for the Fortune 500. The idea underneath it costs nothing, and most small businesses skip it.

What actually happened

IBM grouped the launch under discovery, identity, access and actions. The parts that matter, per the release:

• Generally available: Vault 2.2 gives agents their own accounts, renews their credentials automatically and adds post-quantum encryption. Agent Identity records each agent's owner, lifecycle status and granted authority, and works with Vault for least-privilege access and real-time revocation. watsonx Orchestrate can now test agents, models and MCP servers before deployment and monitor them after, with cost tracking built in.
• Public preview: a Terraform remote MCP server and a Terraform Developer Portal, so AI agents can change infrastructure only through approved configurations. Secure Hub gives one view across Vault environments.
• Tech preview: Orchestrate Discover finds agents built on Amazon Bedrock, Microsoft Foundry and Google Gemini. Orchestrate Contain runs agents in sandboxes with a kill switch.

IBM did not publish pricing. Preview features can change before they ship.

Why it matters for your business: AI agent identity is the cheap part

You will not buy watsonx to run four agents. The pattern is still correct, and you can copy it with tools you already pay for.

The usual small-business setup is one API key for everything. The support bot, the n8n workflow and the Shopify sync all share it. When one of them misbehaves, you cannot tell which one did it, and you cannot cut one off without breaking the other three.

The IBM model fixes that with four rules we already apply to client builds:

• One identity per agent. A separate API key, service account or OAuth client for each agent. Name it after the job, not the vendor.
• One owner per agent. One person's name in the inventory. No owner means no agent.
• Short-lived credentials. Use your secrets manager to rotate them. Vault, Doppler, 1Password and AWS Secrets Manager all do this. No key lives in a config file for a year.
• Infrastructure through a gate. If an agent can change DNS, billing or servers, it goes through a reviewed path, like a Terraform plan a person approves. It never gets the root console.

Sources: IBM Newsroom, IBM release via PR Newswire.