IBM is giving every AI agent an identity, a short-lived password and a kill switch
IBM used TechXchange 2026 to announce something that reads like plumbing and is actually the next layer of the agent story: every agent gets a governed identity, short-lived credentials scoped to its job, and a way to cut it off mid-action. Four pieces shipped together. Identity Each agent gets a r
Posted on Oct 27 • Originally published at voxahq.in
IBM used TechXchange 2026 to announce something that reads like plumbing and is actually the next layer of the agent story: every agent gets a governed identity, short-lived credentials scoped to its job, and a way to cut it off mid-action.
Each agent gets a record: who owns it, whether it is live, and what authority it has been granted. The identity sits next to the credentials, so permission and identity cannot drift apart.
HashiCorp Vault now issues short-lived credentials to agents and can revoke a session in real time if the agent tries something outside its approved scope. Vault 2.2 adds per-agent accounts, automatic renewal and post-quantum encryption.
watsonx Orchestrate can find agents built on Amazon Bedrock, Microsoft Foundry and Google Gemini, run them in isolated sandboxes, and shut any of them down with a kill switch. The same console tracks model and token use per agent, so the bill can be traced to one agent rather than to "AI".
Gartner expects the average Fortune 500 company to run more than 150,000 agents by 2028. IBM's more useful line: only 13 percent of organisations believe they have the right agent governance in place.
That gap is the product. Agents are being deployed faster than they can be verified, and the failure mode is always the same: a credential with more access than the task needs, held longer than the task runs.
Through October, US banks moved to block third party agents from operating inside customer accounts after reports of agents acting outside user instructions. Twenty one agent incidents became public between July and October across the major labs.
Nobody is arguing agents should stop. The argument is about authority. An agent should be able to prove who it is, reach only what its job requires, and lose access the moment it steps outside that line.
One agent, one identity, one scope, a credential that expires, and a revocation path you have actually tested. That is the whole checklist, and it costs nothing on the free tiers most teams already use.
Originally published at voxahq.in. Sources: IBM press release, TechXchange 2026, 27 October 2026; Gartner agent sprawl research, April 2026.