An agent can have a name in a registry and still hold more access than its next task needs.
IBM’s October 27 agent-control announcement combines identity, credentials, and operational management across several products. Agent Identity and HashiCorp Vault 2.2 are among the generally available offerings.
IBM separately announced Agent Identity general availability on October 26. Its broader portfolio announcement includes a mix of released products and previews, so you need to check the release status at the product level.
What is available and what remains a preview
| Release status | Named capabilities |
|---|---|
| Generally available | Agent Identity; Vault 2.2; watsonx Orchestrate evaluate; IBM Concert; Terraform policy. |
| Public preview | Secure Hub; Terraform Developer Portal; Terraform remote MCP server; IBM Z Atlas. |
| Technology preview | IBM Integration Intelligence Hub; watsonx Orchestrate discover and contain. |
Follow authority from the owner to the action
IBM describes Agent Identity as a way to coordinate registration, delegation, enforcement, and governance. For a team deploying agents, the practical question is who owns each agent and which authority it uses for a particular action.
A registry entry answers which agent exists. Delegation records explain whose permission it carries. A credential lets it reach a service, while revocation determines how that access ends. Treating those as separate checks makes missing controls easier to identify.
Evaluate how access ends
For a controlled pilot, create one test agent with permission to perform a harmless operation on a test record. Record the owner, allowed action, and credential lifetime. Then withdraw the relevant authority and retry the same operation.
Observe which layer refuses the request and how the refusal appears in logs. Also check the fate of work already in progress. This is a proposed evaluation, not a test of IBM’s products or a claim that every product handles each case identically.
Short-lived credentials can reduce how long a credential remains useful. They do not prove that every delegated action is appropriate or that a compromised agent cannot act before expiry.
Use IBM’s full release-status list and Agent Identity overview when choosing a pilot. The required workflow should determine which released controls and preview dependencies are acceptable.
