VentureBeat Mar 17, 03:35 PM
The authorization problem that could break enterprise AI When an AI agent needs to log into your CRM, pull records from your database, and send an email on your behalf, whose identity is it using? And what happens when no one knows the answer? Alex Stamos, chief product officer at Corridor, and Nancy Wang, CTO at 1Password joined the VB AI Impact Salon Series to dig into the new identity framework challenges that come along with the benefits of agentic AI.
"At a high level, it’s not just who this agent belongs to or which organization this agent belongs to, but what is the authority under which this agent is acting, which then translates into authorization and access," Wang said.
How 1Password ended up at the center of the agent identity problem
Wang traced 1Password's path into this territory through its own product history. The company started as a consumer password manager, and its enterprise footprint grew organically as employees brought tools they already trusted into their workplaces.
"Once those people got used to the interface, and really enjoyed the security and privacy standards that we provide as guarantees for our customers, then they brought it into the enterprise," she said. The same dynamic is now happening with AI, she added. "Agents also have secrets, or passwords, just like humans do."
Internally, 1Password is navigating the same tension it helps customers manage: how to let engineers move fast without creating a security mess. Wang said the company actively tracks the ratio of incidents to AI-generated code as engineers use tools like Claude Code and Cursor. "That's a metric we track intently to make sure we're generating quality code."
How developers are incurring major security risks
Stamos said one of the most common behaviors Corridor observes is developers pasting credentials directly into prompts, which is a huge security risk. Corridor flags it and sends the developer back toward proper secrets management.
"The standard thing is you just go grab an API key or take your username and password and you just paste it into the prompt," he said. "We find this all the time because we're hooked in and grabbing the prompt."
Wang described 1Password's approach as working on the output side, scanning code as it is written and vaulting any plain text credentials before they persist. The tendency toward the cut-and-paste method of system access is a direct influence on 1Password's design choices, which is to avoid security tooling that creates friction.
"If it's too hard to use, to bootstrap, to get onboarded, it's not going to be secure because frankly people will just bypass it and not use it," she said.
Why you cannot treat a coding agent like a traditional security scanner
Another challenge in building feedback between security agents and coding models is false positives, which very friendly and agreeable large language models are prone toward. Unfortunately, these false positives from security scanners can derail an entire code session.
"If you tell it this is a flaw, it'll be li