AI browsers and enterprise identity controls: are you ready?

TL;DR: OpenAI’s Atlas turns the browser into an active AI layer that can navigate, act, and mediate data, but Cyera notes it still lacks SSO, MFA, auditability, region controls, and enterprise governance needed for regulated workflows. The lesson is that browser security is now an identity and data-governance problem, not just a monitoring problem.

NHIMG editorial — based on content published by Cyera: Atlas and the Future of the Enterprise Browser

By the numbers:

• 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation.
• Only 5.7% of organisations have full visibility into their service accounts.
• 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.

Questions worth separating out

Q: How should security teams govern AI browsers that can act on enterprise content?

A: They should govern them as access intermediaries, not just as user interfaces.

Q: Why do AI browsers create new identity and access risk?

A: Because they turn the browser from a passive display layer into a system that can interpret content and execute actions.

Q: What breaks when an AI browser has no SSO, MFA, or audit trail?

A: Enterprise accountability breaks first.

Practitioner guidance

• Define browser access classes by data sensitivity Classify which information may be exposed to an AI browser, and block regulated, confidential, or administrative content unless governance controls are in place.
• Require enterprise federation before rollout Do not allow production use until the browser can integrate with SSO, MFA, and enterprise identity policy so that access can be revoked, attributed, and audited like other governed sessions.
• Demand exportable telemetry and incident evidence Insist on session logs, event export, retention rules, and SIEM-compatible telemetry so security teams can reconstruct browser actions after prompt injection, misuse, or data exposure.

What's in the full article

Cyera's full analysis covers the operational detail this post intentionally leaves for the source:

• How Atlas handles consumer versus enterprise login flows, including the current identity limitations that affect rollout decisions.
• Cyera's breakdown of auditability, retention, and jurisdiction concerns for regulated workflows.
• The article's discussion of prompt injection, context mixing, and other AI-specific browser failure modes.
• Operational questions around billing, logging ownership, and expected service boundaries for enterprise deployments.

👉 Read Cyera's analysis of Atlas and enterprise browser identity risk →

AI browsers and enterprise identity controls: are you ready?

Explore further

View Full Forum →  |  NHI Foundation Course →