IBM Gives AI Agents Verified Identities: Why Identity Is Now the Foundation of Safe Agent Scale

At TechXchange 2026 on 26 October, IBM and HashiCorp announced a joint answer to the question that is quietly keeping more chief information security officers awake than any model benchmark: who owns the agent that just accessed the customer database?

The announcement is not a research project or a future roadmap. It is a shipping product. HashiCorp Vault now issues verified, short-lived identities to AI agents. IBM's Agent Identity adds the governance layer: who owns the agent, what it is authorised to do, and how to revoke that authority in real time when an agent attempts something it should not.

For enterprise buyers, the message is practical and urgent. Gartner estimates that by 2028 the average Fortune 500 will run more than 150,000 AI agents. IBM's own data, presented at the event, says only 13% of organisations believe they currently have the right agent governance in place. The gap is not theoretical. It is the difference between deploying agents and trusting them.

What IBM and HashiCorp announced

The announcement has two parts that only work together. HashiCorp Vault, already the standard for secrets management at organisations including the London Stock Exchange, BlackRock, Adobe and Starbucks, now extends to AI agents. IBM's Agent Identity provides the governance framework that sits on top.

Agent Identity. IBM has created a governed identity record for each agent. This includes who owns it within the organisation, its lifecycle status, and the authority it has been granted. The identity record is designed to extend existing identity investments rather than replace them, and it shares context with HashiCorp Vault's credential controls so that access enforcement and identity ownership are linked.

Short-lived credentials. HashiCorp Vault issues secured, expiring credentials to each agent. Instead of persistent tokens that sit in environment variables for months, credentials are generated for the specific task, scoped to the minimum permissions required, and automatically rotated or revoked. If an agent attempts an action outside its approved permissions, Vault can deny the access and revoke the session in real time.

Least-privilege enforcement. The combination means that every agent receives only the access it needs, for only as long as it needs it. This is the same principle that governs human employee access in regulated enterprises, but applied to a new class of non-human identity that can act thousands of times faster than a person.

The announcements also include Vault 2.2 with post-quantum encryption for agent credentials, Secure Hub for centralised Vault governance visibility, and an integration with NVIDIA OpenShell that pairs verified identity with policy-governed runtime environments.

Why identity is the missing layer

Enterprise AI agents have spent the last 18 months proving what they can do. The next 18 months will be about proving who did it and whether they were allowed to.

The problem is visible in three patterns that security teams are already seeing.

Persistent credentials. Many agents today run with API keys or tokens that are set once and never rotated. If the agent is compromised, the credential often remains valid long after the breach is discovered. Short-lived credentials solve this by design.

Unclear ownership. When an agent performs an action, most organisations cannot answer a basic forensic question: who created the agent, who approved its permissions, and which business process authorised the action? Agent Identity creates an authoritative record that auditors and incident response teams can query.

Disconnected controls. Agents built in one platform can access tools and data in another, often with no central visibility. IBM watsonx Orchestrate, also announced at TechXchange, adds discover, contain and evaluate capabilities across Amazon Bedrock, Microsoft Foundry and Google Gemini, so organisations can find agents they did not know they had, isolate rogue agents, and test agents before they reach production.

Shailesh M. Shenoy, assistant dean for information technology at Albert Einstein College of Medicine, set the problem in human terms at the event: technologies such as IBM Verify and HashiCorp Vault can play an important role in helping organisations establish the identity, access and security controls needed to innovate with confidence.

What it means for enterprise buyers

For procurement and security teams, the announcement creates a useful checklist for agent platform evaluation.

Ask about agent identity. Every agent in production should have a recorded owner, a defined lifecycle and a documented authority scope. If a vendor cannot show you this, they are not building for enterprise governance.

Ask about credential lifetime. Persistent API keys are a red flag. Short-lived, dynamically generated credentials that expire automatically are the standard that HashiCorp Vault has established for application secrets. Agents should meet the same standard.

Ask about real-time revocation. When an agent misbehaves, how quickly can access be removed? The difference between immediate revocation and a ticket in the IT backlog is the difference between a contained incident and a breach.

Ask about cross-platform visibility. Most enterprises will use agents from multiple providers. A governance system that only works inside one platform creates blind spots. IBM's approach, with watsonx Orchestrate connecting to Bedrock, Foundry and Gemini, signals that buyers should expect cross-platform agent discovery and containment.

What it means for suppliers

For companies building and selling agentic AI platforms, the signal is equally clear. Feature capability is no longer the only buying criteria. Identity, accountability and auditability are becoming prerequisites for enterprise procurement.

Suppliers that can demonstrate verified agent identity, scoped permissions, automatic credential rotation and real-time revocation will have a structural advantage in regulated industries: financial services, healthcare, government, telecommunications and critical infrastructure. These are the same industries that spend the most on agentic AI, and the same industries where a governance failure is most expensive.

The NVIDIA OpenShell integration is also worth noting. When identity governance connects to runtime governance, an agent cannot just be identified. It can be contained at the point of execution. This is the kind of layered architecture that enterprise risk committees will increasingly require.

The Agentic Expo angle

Agentic Expo, at Olympia London on 23 to 24 March 2027, is where the buyers and suppliers of agentic AI converge. By then, the governance conversation will have moved from early-adopter concern to mainstream procurement requirement.

The IBM and HashiCorp announcement is a signpost in that transition. Identity and credential management, once the quiet back-office concern of cybersecurity teams, is becoming the foundation upon which enterprise agent scale will be built. The exhibitors and visitors at Agentic Expo who understand this shift will have a clearer path to adoption.

For buyers, the practical question for every vendor on the show floor should be straightforward: how does your agent prove who it is, who owns it, and what it is allowed to do? The quality of the answer will tell you more about the platform's enterprise readiness than any capability demo.