Topic starter
11/08/2026 3:11 pm
TL;DR: Browser-based AI agents are widening an existing identity gap by acting inside unmanaged applications, where federation covers only 20 to 50 percent of enterprise apps according to Unixi. The real problem is delegated execution without task-level authority, attribution, or auditability, which makes browser-level governance essential.
Editorial analysis by NHI Mgmt Group, based on content published by Unixi: “Why SSO Alone Is Not Enough for Browser-Based AI Agents”.
By the numbers:
- Federation covers just 20 to 50 percent of enterprise applications, according to Unixi.
Key questions
Q: What breaks when AI agents run outside enterprise-controlled browsers?
A: What breaks is visibility, containment, and reliable accountability.
Q: Why do browser-based agents increase risk in unmanaged SaaS and legacy web apps?
A: They inherit the user’s existing access in places where identity teams often lack policy enforcement, central logs, or app onboarding.
Q: How can security teams tell whether delegated browser activity is actually governed?
A: Look for separate identity records, task-level approvals, short-lived delegated authority, and logs that show the human owner, the agent, and the exact action taken.
Practitioner guidance
- Inventory unmanaged applications first Build a list of supplier portals, legacy web apps, and SaaS tools that never entered federation so browser-based agents are not added into invisible workflows.
- Separate human and agent actors Create distinct identity records and audit evidence for the human principal and the browser-based agent so delegated actions do not collapse into one indistinguishable session.
- Scope delegated authority to tasks Limit browser-based agents to read, draft, export, update, or send actions only when the specific task requires it, and make the grant short-lived and revocable.
Bottom line: Browser-based agents do not create the unmanaged app problem, but they make it harder to ignore by operating through the same sessions humans use.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/08/2026 3:25 pm
Browser-mediated delegation is now an identity governance problem, not just an application usability problem. The unmanaged application gap existed before AI agents, but browser-based execution turns it into a dual-actor problem because the same session can now carry both human intent and machine action. That changes the governance question from “did the user log in?” to “which actor was authorised to do which task?” Practitioners should treat browser-level delegation as a first-class identity control surface.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should organisations do when browser-based agents need access to business applications?
A: They should bind authority to the task, not to the whole user session. That means narrowing permissions, revoking access independently of the human account, and adding approval gates for actions that change records, share data, or trigger irreversible workflows.
👉 Read our full editorial: Browser-based AI agents expose the unmanaged app identity gap