Saturday, 31 October 2026Global tech news & guides — what changed, and what it means for you.
AuTechWire
Original editorial illustration of a control room of software-agent figures, each wearing a distinct glowing badge, with one figure's badge dimmed and its connection line cut, dark background, teal and amber accents

IBM Gives AI Agents an Identity: What Its New Controls Actually Do

by

IBM Gives AI Agents an Identity: What Its New Controls Actually Do

In brief

  • IBM announced verified agent identities and short-lived credentials at TechXchange 2026. What is live now, what is preview, and why it matters.
  • The centerpiece, IBM Agent Identity, is generally available now. It keeps an authoritative record for each agent: who owns it, whether it is active, and what authority it has been granted.
  • HashiCorp Vault 2.2 extends secrets management to agents, issuing credentials that expire on their own and can be revoked in real time if an agent steps outside its permissions.
  • Cross-platform discovery in watsonx Orchestrate, which finds agents built on Amazon Bedrock, Microsoft Foundry, and Google Gemini, is in tech preview, not general availability — the distinction matters for buyers planning a rollout.
  • The context, from IBM’s citation of Gartner: by 2028 the average global Fortune 500 enterprise will run more than 150,000 agents, up from fewer than 15 in 2025, while only 13% of organizations believe they have the right agent governance in place today.

Why agents need identities at all

An AI agent is not a chatbot answering questions. In enterprise deployments, agents read databases, call internal tools, move data between systems, and act across teams and cloud platforms. Every one of those actions happens under some credential, and that is where the governance problem starts.

IBM’s announcement names three specific failures: persistent credentials that never expire, unclear ownership of agents, and disconnected controls spread across platforms. A long-lived password or API key issued to an agent is a weak spot with a long shelf life. If it is stolen, or if the agent drifts outside its task, the damage can spread before anyone notices, because nothing in the system ties the action back to a single accountable identity.

The traditional fix for human users — one identity per person, least-privilege access, and a record of who did what — has never been applied consistently to software agents. Agents are often created ad hoc by different teams, run under shared service accounts, and left running long after the project that created them ends. IBM’s pitch is that the enterprise AI rollout now needs the same identity discipline that human access has had for decades, and that it needs it before agent counts explode rather than after.

That framing is worth taking seriously even if you never buy an IBM product. The question “who owns this agent, what can it touch, and can we shut it off?” is now a standard due-diligence question for any organization deploying agents, whatever platform they run on.

What is generally available now

Two pieces of the announcement are live today, and they are the parts a buyer can actually deploy.

First, IBM Agent Identity, now generally available. It is the system of record for agents: for each agent it records the owner, its active status, and the authority granted to it. That record is what makes the rest of the controls possible. Without an authoritative identity, access rules have nothing to attach to, and audit logs have no one to blame. IBM positions Agent Identity as the foundation layer, not a feature bolted onto an existing product.

Second, HashiCorp Vault 2.2, which extends Vault’s established secrets management to agents. Agents get their own secured accounts, and Vault renews their credentials automatically. The credentials are short-lived by design: they expire on their own, and if an agent attempts to read data or take an action outside its approved permissions, access can be denied and the session ended in real time. Vault 2.2 also adds post-quantum encryption for agent credentials, a forward-looking choice given how long some enterprise credentials live in backups and logs.

The short-lived credential is the most practically important idea in the announcement. A stolen long-lived key is useful for months. A stolen short-lived credential may already be expired by the time an attacker tries to use it, and revocation closes the window immediately. This is standard practice for human service accounts in mature shops; extending it to agents closes a gap that has been open since agents started touching production systems.

What is still in preview

The third piece, and the one most likely to be oversold in secondhand coverage, is discovery. IBM watsonx Orchestrate is designed to unify discovery, containment, and evaluation across vendors rather than inside one platform. Its new discovery feature connects to Amazon Bedrock, Microsoft Foundry, and Google Gemini to find agents built elsewhere, and it also covers models and MCP servers.

That discovery feature is in tech preview. That means it is available for evaluation, not a finished, supported product, and its coverage and behavior may change before general availability. For an organization whose agents are scattered across three clouds, discovery is arguably the most valuable capability in the announcement — you cannot govern agents you cannot find — but it is also the least finished. Any rollout plan that depends on cross-platform discovery should be written with that preview status in mind, and with a fallback: an internal agent inventory maintained by hand until the tooling is final.

A separate evaluation feature lets teams test agents for quality, accuracy, and compliance before launch, then monitor them in production. Built-in cost tracking shows which agent is burning through tokens. These are operational controls, not security controls, but they belong in the same governance conversation: an agent that is secure but unmonitored for cost and quality is still an unmanaged liability.

The 150,000-agent number, read carefully

The headline figure in IBM’s announcement comes from Gartner, and it deserves a careful read. Gartner predicted in an April 28, 2026 press release that by 2028 an average global Fortune 500 enterprise will have over 150,000 agents in use, up from fewer than 15 in 2025, and that only 13% of organizations believe they have the right agent governance in place.

Three cautions apply. First, 150,000 is a forecast, not a count of agents running today; the jump from under 15 to over 150,000 in three years assumes an adoption curve that may or may not arrive on schedule. Second, “agents” in such forecasts is a loose category that can include everything from a scheduled script with a language model attached to a fully autonomous workflow, so the number is best read as a direction of travel, not a precise headcount. Third, the 13% figure is a self-reported belief about governance readiness, not a measured audit result.

None of that makes the governance problem imaginary. Even a fraction of the forecast volume — thousands of agents per large enterprise, each holding credentials — is enough to make manual agent management fail. The honest reading is: agent counts are rising fast, governance is widely acknowledged as behind, and the exact slope of the curve is uncertain. Buyers should plan for the direction, not the precise number.

What this means for you

  • If you run agents in production today: inventory them now, with an owner per agent, before buying any tooling. IBM’s discovery feature is in preview; your spreadsheet is available today.
  • If you issue long-lived keys to agents: that is the first thing to fix. Short-lived, auto-renewed credentials with real-time revocation are the single highest-value control in this announcement, and the pattern applies on any platform.
  • If your agents span multiple clouds: treat cross-platform discovery as a roadmap item, not a deployed capability, until it leaves tech preview. Plan the interim inventory by hand.
  • If you are evaluating IBM’s stack: the generally available pieces (Agent Identity, Vault 2.2) are deployable now; evaluate discovery and evaluation on their preview terms, with exit criteria for going live.
  • If you are not an IBM shop: steal the model, not the product. Verified identity, least-privilege access, and revocation are platform-independent controls, and every major cloud vendor is building its own version.

What is still unproven

This is a vendor announcement, not an independent test. No third party has published a hands-on evaluation of Agent Identity or Vault 2.2’s agent controls yet, and IBM disclosed no pricing in the announcement. Performance at scale — tens of thousands of agents issuing and renewing short-lived credentials — is asserted, not demonstrated. Organizations evaluating the stack should run a proof of concept against their own agent estate, including a revocation drill: create an agent, grant it access, revoke it mid-task, and confirm the session actually ends.

The cross-vendor story also deserves scrutiny. Discovery across Bedrock, Foundry, and Gemini is a strong claim, and its usefulness depends on how deep the integration goes in practice — whether it finds agents, or merely lists them, and whether containment actions taken in Orchestrate actually stop an agent running on another platform. Those are questions for the proof of concept, not the press release.

Related reading

Sources

  • IBM announcement, “IBM Introduces Identity and Control for AI Agents,” PRNewswire, October 27, 2026: https://www.prnewswire.com/news-releases/ibm-introduces-identity-and-control-for-ai-agents-securing-frontier-intelligence-for-the-enterprise-302920156.html
  • Morningstar carrying the PRNewswire release, October 27, 2026: https://www.morningstar.com/news/pr-newswire/20261027ny81742/ibm-introduces-identity-and-control-for-ai-agents-securing-frontier-intelligence-for-the-enterprise
  • Unite.AI, “IBM Brings Governed Identity and Credential Controls to AI Agents,” October 27, 2026: https://www.unite.ai/ibm-brings-governed-identity-and-credential-controls-to-ai-agents/
  • AI Parabellum, “IBM Launches AI Agent Identity With Short-Lived Credentials,” October 27, 2026: https://aiparabellum.com/ibm-agent-identity-vault-orchestrate-launch/

Last verified: October 27, 2026.

Shoaib Hassan

Shoaib Hassan is the founder and editor of AuTechWire, an independent technology publication covering broadband, mobile networks, privacy, startups, and consumer tech.

Related Stories

Leave a Comment