CISO
CIO
Enterprise Architect
Industry relevance
Financial Services
Healthcare
Government
OCTOBER 27, 2026
IBM announced its own agent identity record, credential vault, and cross-platform agent discovery. Enterprises with agents from several vendors now face competing records of who owns each agent.

On October 27, 2026, IBM announced identity and control products for AI agents at TechXchange 2026 in Atlanta. IBM says Agent Identity keeps the authoritative record for each agent, including its owner, lifecycle status, and granted authority, and works with HashiCorp Vault, which will issue short-lived, least-privilege credentials to agents. IBM lists Vault 2.2, Agent Identity, watsonx Orchestrate Evaluate, IBM Concert, and Terraform policy as generally available. It lists Secure Hub, the Terraform Developer Portal, the Terraform remote MCP server, and IBM Z Atlas as public preview, and the IBM Integration Intelligence Hub plus Orchestrate Discover and Contain as tech preview. IBM says Orchestrate Discover finds agents, models, and MCP servers built on Amazon Bedrock, Microsoft Foundry, and Google Gemini.
GOVERNANCE IMPLICATION
Platform vendors are shipping their own records of which agents exist and who owns them, and each record describes only the agents that vendor can see. IBM's release is one more example: its Agent Identity record holds owner, lifecycle status, and granted authority, and its Orchestrate Discover capability, which IBM lists as tech preview, is described as finding agents built on Amazon Bedrock, Microsoft Foundry, and Google Gemini. An enterprise that adopts several of these gains several registries and no rule for which one prevails when they disagree. That rule is a governance decision, not a product setting. It also needs to say who reconciles the records and how often. Availability differs by capability, so the GA and preview labels in the release should be checked against any tenant before it is relied on.
SCENARIO
Hypothetical: An enterprise runs a customer-service agent registered in one vendor's console and discovered by a second vendor's tool. The two records list different owners after a reorganization. When the agent issues an incorrect refund, the incident team finds the two registries disagree and no policy says which one counts.
THE GOVERNANCE QUESTION
When an enterprise runs agents from several vendors, which one agent record is the authoritative one for owner, lifecycle, and granted authority?
CONTROL GAP
Several agent registries can each hold a different owner and authority for the same agent. Unless a policy says which record governs an audit or incident, the choice is made during the incident.
PRIMARY SOURCE
IBM Introduces Identity and Control for AI Agents, Securing Frontier Intelligence for the Enterprise
IBM Newsroom (no individual byline)
October 27, 2026
Read the primary source ->(opens in new tab)CONTINUE READING

OCTOBER 19, 2026
Agent SecurityOn October 19, 2026, Microsoft published a post by Nadim Abdo, Corporate Vice President, Identity and Network Access, that treats AI agents already inside the enterprise as insiders. Microsoft says it is expanding discovery to 35 additional types of local agents, for a total of 60 supported local agents, including Claude Code, OpenAI Codex, and GitHub Copilot. Microsoft says agents should begin with no authority and describes Dynamic Permissions scoped to the task and time-bound, with organization-wide policy setting the outer boundary. It also describes Dynamic Agent Risk, Dynamic Conditional Access, and Guardian Agents in Project Perception. The post says people define policy, approval boundaries, and delegation rules. It gives no availability dates for any capability.

MAY 1, 2026
AgentsMicrosoft's May 1, 2026 What's New in Agent 365 announcement introduced registry sync, allowing organizations to connect the Agent 365 registry to external agent platforms. Initial preview connections include Amazon Web Services and Google Cloud, with additional partner platforms planned. When connected, agents built on those platforms appear in the Agent 365 unified registry with governance actions including agent deletion available directly from the registry interface. Without registry sync connections configured, Agent 365 shows only Microsoft-hosted agents.