{"slug": "ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls", "title": "IBM and Nvidia link AI agent identity to runtime access controls", "summary": "IBM and Nvidia announced an integration linking IBM's Agent Identity solution, in public preview since September 1, 2026, to Nvidia's Open Agent Safety Platform (OASP), pairing scoped, temporary agent credentials with hardware-level runtime enforcement. The integration, highlighted on September 28, 2026, uses HashiCorp Vault for dynamic short-lived credentials and Red Hat OpenShift for multi-cloud infrastructure, while IBM Identity Protection discovers undocumented \"shadow agents\" and Nvidia's Sentry verifies agent identity and enforces policies within milliseconds even on a compromised host. More than 100 organizations are reportedly working with Nvidia's OASP technologies.", "body_md": "Photo: Ivan Chumak / Pexels\n\n# IBM and Nvidia link AI agent identity to runtime access controls\n\nIBM's Agent Identity now plugs into Nvidia's Open Agent Safety Platform, pairing software credentials with hardware-level enforcement\n\nAI agents are getting jobs. Now they are getting ID badges, too.\n\n[IBM](https://cryptobriefing.com/markets/ibm/) and [Nvidia](https://cryptobriefing.com/markets/nvidia/) have announced an integration between IBM’s Agent Identity solution and Nvidia’s Open Agent Safety Platform, known as OASP. The goal is simple to describe and hard to pull off: make sure every autonomous AI agent is identified, scoped and watched while it works.\n\n## What IBM and Nvidia are actually building\n\nIBM’s Agent Identity entered public preview on September 1, 2026. The integration with Nvidia was highlighted on September 28, 2026, less than a month later.\n\nThe basic idea treats each AI agent like a new employee. It gets registered, receives a unique identity, and is handed only the access it needs for a specific task.\n\nThat access does not last forever. The system issues scoped, temporary tokens, so permissions expire instead of piling up quietly in the background.\n\nFor the credentials themselves, the integration uses HashiCorp Vault. Vault generates dynamic, short-lived credentials for agents, which means a stolen key is only useful for a narrow window.\n\nRed Hat OpenShift handles the infrastructure side. It manages heterogeneous cloud environments, the messy mix of platforms most large companies actually run on.\n\n## The shadow agent problem\n\nOne of the more interesting pieces involves what the companies describe as shadow agents. These are unknown or undocumented AI entities running inside an organization’s systems.\n\n### AI, tech, and the markets they move—in one daily briefing.\n\nDaily. Free. Join 34,000+ readers across crypto, finance, and policy.\n\nIBM Identity Protection is designed to discover and monitor all agents, including those shadow agents. You cannot set rules for software you do not know exists, so finding it comes first.\n\nOnce an agent is found and registered, its actions can be audited and controlled. That is the core promise: every action traces back to an identity, and every identity traces back to a policy.\n\n## Where Nvidia comes in\n\nIBM supplies the identity layer. Nvidia supplies the enforcement muscle underneath it.\n\nNvidia contributes isolated runtime environments and hardware-level monitoring. Put plainly, agents run in walled-off spaces, and the hardware itself keeps an eye on what they do.\n\nA key component is Nvidia’s Sentry. It can verify an agent’s identity and enforce policies within milliseconds, even when a host is compromised.\n\nMore than 100 organizations are reportedly working with Nvidia’s OASP technologies.\n\n## Why identity is the new perimeter for AI\n\nThe IBM and Nvidia approach is layered. Software-defined identity management decides who an agent is and what it may do. Hardware-based enforcement makes sure those decisions hold at runtime.\n\nThe companies also frame the effort around human accountability. Every agent, in this design, ultimately answers to someone, which is a reasonable expectation for software that can move data or trigger transactions without asking first.\n\nThe partnership builds on prior work from both companies. It also fits a broader push toward consolidating governance across AI applications rather than bolting security onto each one separately.\n\n**Disclosure:** This article was edited by Diego Almada Lopez. For more information on how we create and review content, see our\n\n[Editorial Policy](https://cryptobriefing.com/editorial-policy/).", "url": "https://wpnews.pro/news/ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls", "canonical_source": "https://cryptobriefing.com/ibm-nvidia-ai-agent-identity-access-controls/", "published_at": "2026-10-26 17:37:19+00:00", "updated_at": "2026-10-26 17:44:35.082959+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-policy", "ai-infrastructure"], "entities": ["IBM", "Nvidia", "IBM Agent Identity", "Open Agent Safety Platform", "HashiCorp Vault", "Red Hat OpenShift", "IBM Identity Protection", "Nvidia Sentry"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls", "markdown": "https://wpnews.pro/news/ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls.md", "text": "https://wpnews.pro/news/ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls.txt", "jsonld": "https://wpnews.pro/news/ibm-and-nvidia-link-ai-agent-identity-to-runtime-access-controls.jsonld"}}