Rogue agents are dangerous, but eliminating them is never easy.\u00a0<\/p>\n
Jason Bourne, Ethan Hunt, and James Bond have each run afoul of their governance at various junctures, yet stopping them takes sequel after sequel until all the loose ends are tied up and they eventually die or retire, only to get rebooted.\u00a0<\/p>\n
It\u2019s not so different in the world of AI agents.\u00a0<\/p>\n
Okta leaders, citing the company’s own research, say enterprises are deploying AI agents faster than they are securing them, with 92 percent<\/a> of executives reporting moderate or widespread use of autonomous AI agents, but only 22 percent saying their organizations have identities tied to those agents.<\/p>\n \u201cThat is a real problem,\u201d Okta president and chief operating officer Eric Kelleher said during the company’s earnings call on Thursday. \u201cIt’s a measurable, quantifiable exposure customers have right now within their companies, and they need to invest to fix it.”\u00a0<\/p>\n In short, when agents go sideways, someone has to handle the dirty work.\u00a0<\/p>\n Okta CEO Todd McKinnon told investors that\u2019s what ServiceNow<\/a> was asking for when the ITSM market leader came calling.\u00a0<\/p>\n \u201cWhat they were really interested with Okta was this kill switch capability,\u201d McKinnon said during earnings. \u201cWhen agents go awry and agents aren’t following the policy, how do you shut them down? \u2026 The one thing we do really well, and that they wanted from us, is the ability to sever the connections, the access tokens, the actual logical connection at the authorization layer to the backend resources, and we’re really good at that.\u201d\u00a0<\/p>\n ServiceNow has previously said<\/a> its acquisition of Veza could provide that capability. In a statement to The Register, a ServiceNow spokesperson said\u00a0Okta serves as the logical connection to backend resources at the identity layer, while Veza gives ServiceNow visibility and control over the permissions graph. <\/p>\n “To clarify how the pieces fit together: ServiceNow’s AI Control Tower is the orchestration and governance layer that monitors risk and detects when an agent is behaving outside policy. When that happens, the platform can trigger remediation actions across multiple identity and access systems, including Okta, which handles token revocation at the authorization layer,” the spokesperson said.\u00a0<\/p>\n Veza, which ServiceNow acquired earlier this year, operates at a different layer, the spokesperson said, mapping permissions across human, machine, and AI identities at scale, and it lets ServiceNow revoke agent permissions directly within the ServiceNow platform, which is its own “kill switch.”\u00a0<\/p>\n \u00a0<\/p>\n McKinnon said that he has spent the past six months meeting Okta’s largest customers in person, reaching roughly 75 of the company’s top 100 accounts. The pattern he saw across those conversations was that agents are widely deployed, but the controls around them are immature.<\/p>\n \u201cYou\u2019ll have a development team that\u2019s using Claude Code, but it’s connected to GitHub and their Jira system with static tokens in the local developer box,\u201d he said. \u201cSo that company is using agents, but they\u2019ve really done it in a haphazard, non-secure way.\u201d\u00a0<\/p>\n He said the company\u2019s two leading products for controlling AI agents \u2013 Okta for AI Agents and Auth0 for AI Agents \u2013\u00a0 are not yet contributing substantially to the company\u2019s revenue, but Okta sees an industry in need just over the horizon.\u00a0<\/p>\n \u201cIt\u2019s going to be big. We\u2019re pouring a lot of R&D effort into this and focused on it. The interest is super high and unlike anything we\u2019ve ever seen,\u201d he said.\u00a0<\/p>\n McKinnon said that there are several ways to control rogue agents, whether it’s stopping them from running or quarantining them at a network level, but all of that relies on observability and permissions that need to be set from the beginning.\u00a0<\/p>\n Okta’s proposed answer is to apply the model it already uses for employee and customer access to the AI agents themselves. McKinnon said Okta can identify the agents operating inside an organization, maintain a record of them, and set rules governing what systems each agent may reach.<\/p>\n “We tell you who your agents are. There’s a directory of agents,” he said. “We can scan multiple platforms and multiple systems and give you that source of truth of where your agents are, and we can help you set a policy on what they can connect to.”<\/p>\n For large enterprises running thousands of applications, he said, rewiring each one to accommodate agents is not practical, so Okta instead places an authorization layer around the agents to control their permissions and connections.\u00a0<\/p>\n Rival identity platform Microsoft Entra also boasts that it has similar capabilities. Autonomous agents authenticate directly with the Microsoft Entra ID platform using their agent identity and the client credentials flow, Microsoft says<\/a>.\u00a0<\/p>\n Entra assigns identities to agents, autodiscovers them across an organization, applies Conditional Access rules and permissions, and lets customers disable entire classes of agents in a single operation, Redmond says.\u00a0<\/p>\n McKinnon said that, while the market is busy hunting for winners and losers in the AI agent race, customers want a secure experience regardless of the vendor. In addition to its work with ServiceNow, Okta partnered with Salesforce last year and AWS this month.<\/p>\n