Analyst
Forrester: Enterprise Browser Market Now Has Real Tremors
Key Finding
Once the analysts converge on a category, the procurement clock starts. Identity teams that have not formed a view on enterprise browser get the decision made for them by procurement.
Forrester's enterprise-browser coverage matured through 2024 into early 2026. Analyst commentary — including Paddy Harrington's "Tremors Originating From A California Ripple In The Enterprise Browser Market" and follow-on Forrester blog posts in the same category — moved the segment from horizon-watching to category formation. The market consolidation accelerated with Palo Alto Networks' acquisition of Talon, Island's funding growth, and a measurable customer-deployment base across financial services, healthcare, manufacturing and government.
For identity teams this changes the conversation in three ways.
The browser is now a procurement category. When the analysts converge on a segment, RFPs follow. If your identity architecture does not have a position on where the browser sits — as an identity-aware PEP, as a last-mile DLP control, as a contractor-access pattern — the position will be assigned to it by whoever runs the RFP. We have seen identity teams discover that the enterprise browser was already procured and rolled out to a third of the workforce before they were asked how it should federate.
The use-case set is broader than the demo. Most enterprise-browser pilots start with one use case: contractor access, third-party developer access, or unmanaged-device productivity. The category research makes clear that the same platform absorbs VDI replacement, GenAI governance, M&A integration, and service-access restoration. Identity architects who only model the contractor use case underestimate the surface area.
The integration model matters more than the feature checklist. Browsers that consume identity from your IdP, post-events into your SIEM, respect your conditional-access decisions, and recover cleanly when the IdP is unavailable are architecturally different from browsers that try to be a parallel identity plane. The difference does not show up in a feature matrix; it shows up the first time the identity team tries to use the browser as part of an incident response.
Forrester's category formation is a useful trigger for the architecture conversation. It is not the answer to it.
Need help with your identity architecture?
Every incident on this page was preventable with the right architecture. Let's talk about yours.
Book a Conversation