THE WORLD IS NOT STANDING STILL.RSS
BIG CHANGE.
BIG CHANGE, one tap away
BIG CHANGE, one tap away

Make room for the big picture.

Add BIG CHANGE to your home screen or desktop. It opens in its own window, with the latest stories when you’re online.

iPhone & iPad
Open bigchange.ai in Safari. Tap Share, then Add to Home Screen. Turn on Open as Web App if shown, then tap Add.
Android
Open bigchange.ai in Chrome. In the browser menu, choose Install app or Add to Home screen.
Desktop
In Chrome or Edge, use the install icon in the address bar or the browser’s app menu. In Safari on Mac, choose File → Add to Dock.

Markdown edition

# IBM agent identity: GA controls and preview limits

> IBM Agent Identity, Vault 2.2 and Orchestrate Evaluate are GA; Discover and Contain remain previews.

By BIGCHANGE.AI Editorial

Published: 2026-10-27T13:41:40.584Z
Updated: 2026-10-27T13:41:40.584Z
Canonical: https://bigchange.ai/blog/ibm-agent-identity-vault-orchestrate-availability-boundaries

![A blank identity badge on an orange lanyard rests apart from a metal key in a shallow tray.](https://bigchange.ai/api/media/file/ibm-identity-credential-boundaries-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE.

An agent’s identity alone does not tell a security team what the agent can do. The authority to act must be traced through each system it touches.

**The big change**

- **What changed:** IBM’s [October 27 release](https://newsroom.ibm.com/2026-10-27-ibm-introduces-identity-and-control-for-ai-agents,-securing-frontier-intelligence-for-the-enterprise) lists Agent Identity, Vault 2.2 and watsonx Orchestrate Evaluate as generally available. Discover and Contain are tech previews; Secure Hub is a public preview.
- **Why it matters:** Vault’s registry, delegated policy ceiling and session claims narrow access at different points.
- **What to watch:** Cross-platform coverage and attack outcomes remain unverified.

## Availability is not one status

The version number needs care. HashiCorp’s [Vault release notes](https://developer.hashicorp.com/vault/docs/updates/release-notes) date 2.2.0 to October 15 and 2.1.0 to September 1. They say native agentic workflow support left beta and became generally available in Enterprise 2.1.0.

[Orchestrate’s TechXchange article](https://www.ibm.com/new/announcements/ibm-watsonx-orchestrate-advances-enterprise-ai-agent-management-with-new-capabilities-at-techxchange-2026) describes evaluation and trace inspection; preview discovery names Amazon Bedrock, Microsoft Foundry and Google Gemini.

## Follow the authority through Vault

HashiCorp’s [agentic IAM documentation](https://developer.hashicorp.com/vault/ai) identifies three different records. A Vault identity entity identifies the client; an agent registry record says whether that entity is an approved agent and carries governance constraints; an OAuth resource-server profile defines which external token issuers Vault trusts. Vault validates a presented OAuth JWT, resolves the entity, checks registration and evaluates policies on the request. It derives metadata from the JWT for each request rather than storing a lasting Vault token for that flow.

For an agent acting on behalf of a person, the [delegation documentation](https://developer.hashicorp.com/vault/ai/iam) describes an intersection: the person’s baseline Vault policies, the agent’s on-behalf-of ceiling and the session’s Rich Authorization Request constraints. The [RAR reference](https://developer.hashicorp.com/vault/ai/iam/concepts/rar) says its `vault:path_access` details can narrow a Vault path, operation and allowed parameters; they cannot add a permission denied by the baseline policy. This is an authorization decision at Vault.

IBM describes Verify as the delegation layer and Vault as a credential broker for targets that cannot accept delegated tokens. An operator should inspect both Vault’s decision and the target system’s rights and logs before treating an audit trail as complete. This is an inference from the documented boundary, not an observed integration result.

There are practical conditions behind the architecture. HashiCorp says agentic IAM is available in Vault Enterprise 2.1.0 or later and requires an appropriate Enterprise license; its [IAM overview](https://developer.hashicorp.com/vault/ai/iam) also names HCP Vault Dedicated. The [setup documentation](https://developer.hashicorp.com/vault/ai/iam/setup-agent) calls for a deployed Vault environment, a supported identity or OAuth provider and Vault administration rights. Its RAR documentation says a missing `authorization_details` claim is rejected by default, although operators can [make RAR optional](https://developer.hashicorp.com/vault/ai/iam/make-rar-optional), weakening that per-session constraint. The consulted sources give no combined price or full feature entitlement map.

## What a team can assess now

For Vault, inspect the registered agent, delegated subject, baseline policies, ceiling and session constraint. Then examine the credential and target permissions. HashiCorp’s [agent registry documentation](https://developer.hashicorp.com/vault/ai/iam/concepts/agent-registry) is explicit that a ceiling restricts delegated access and cannot enlarge the person’s permissions. These checks describe the documented control surfaces, not a test that BIG CHANGE ran.

## Sources

- [IBM agent control release (October 27, 2026)](https://newsroom.ibm.com/2026-10-27-ibm-introduces-identity-and-control-for-ai-agents,-securing-frontier-intelligence-for-the-enterprise) — Availability and integration claims; outcomes untested.
- [IBM Agent Identity (October 26, 2026)](https://www.ibm.com/new/announcements/ibm-agent-identity-is-now-generally-available-building-trust-for-the-agentic-era) — Verify delegation and broker architecture; vendor account.
- [IBM Orchestrate (October 27, 2026)](https://www.ibm.com/new/announcements/ibm-watsonx-orchestrate-advances-enterprise-ai-agent-management-with-new-capabilities-at-techxchange-2026) — Evaluation and discovery interfaces; vendor account.
- [HashiCorp, Vault 2.x release notes (accessed October 27, 2026)](https://developer.hashicorp.com/vault/docs/updates/release-notes) — Dates Vault 2.1.0 and 2.2.0; establishes that agentic IAM was GA in Enterprise 2.1.0.
- [HashiCorp, Vault + agentic AI (accessed October 27, 2026)](https://developer.hashicorp.com/vault/ai) — Documents Enterprise licensing, agent registration, OAuth token validation, policy checks and request-scoped token handling.
- [HashiCorp, What is agentic IAM? (accessed October 27, 2026)](https://developer.hashicorp.com/vault/ai/iam) — Explains the human baseline, agent ceiling and per-session constraint in delegated Vault access; also names HCP Vault Dedicated.
- [HashiCorp, Rich Authorization Requests (accessed October 27, 2026)](https://developer.hashicorp.com/vault/ai/iam/concepts/rar) — Specifies path, operation and parameter narrowing. The token's RAR claim cannot expand Vault ACL permission.
- [HashiCorp, agentic IAM setup and RAR optional configuration (accessed October 27, 2026)](https://developer.hashicorp.com/vault/ai/iam/setup-agent) — Lists deployed Vault, supported identity provider and admin prerequisites; optional RAR behavior is linked in the article.
- [HashiCorp, Agent registry (accessed October 27, 2026)](https://developer.hashicorp.com/vault/ai/iam/concepts/agent-registry) — Explains the delegated agent ceiling, which restricts rather than expands the person's permissions.