Remote Browsers vs Browser Isolation

Written by Guise Bule, Editor at Secjuice

Remote Browsers vs Browser Isolation

Browser isolation is a cybersecurity model that physically isolates an internet users web browser, along with the associated cyber risk, away from their local machine. Remote browsers are an application of the browser isolation model, a remote browser is a web browser that has been isolated onto a server and delivered to the user over the internet.

When Gartner named 'remote browsing' as one of their top security technologies and started to recommend browser isolation as one of the most effective ways that an organization can reduce web based cyberattacks, the browser isolation space started to heat up. But because some are mixing the terms 'remote browser' and 'browser isolation' interchangeably, its worth covering the difference in these two models and explaining why and how they are different.

Browser isolation is a cybersecurity model underpinned by the principle of security through physical isolation, it is a model that enables its users to physically isolate themselves from malware, ransomware and web based cyberattacks by physically isolating their browsing activity. There are a number of different approaches to browser isolation and the model has spawned a number of different technologies, one of which is WEBGAP the browser isolation technology that underpins our remote browsing platform. But some technologies are client-side solutions that do not deliver remote browsers.

Remote browsers are browser isolation seen from the perspective of the end user.

Remote Browsing is really browser isolation, but seen from the perspective of the end user, or a customer consuming a hosted browser isolation service. Remote browsing platforms are hosted on servers by a third party remote browser provider and then delivered to the customer as a service. When browser isolation is delivered in this way, the users browse the internet using a 'remote browser' but the browser isolation technology and platform is managed buy the provider.

Although WEBGAP has its own remote browsing platform we do not think of our technology as 'remote browsing tech' because we develop the underlying browser isolation technology. A lot of remote browser service providers do not have their own proprietary technology underpinning their platforms which is why they think of what they do as remote browsing instead of browser isolation.

Browser isolation technology underpins remote browsing platforms unless you have built your remote browser platform on top of virtualization software, in which case it only pretends to be browser isolation.

WEBGAP offer a proprietary browser isolation technology that they can run on their infrastructure themselves OR a fully hosted and fully managed remote browser platform as a service. You can host our browser isolation technology yourself, or we can host it for you and deliver remote browsers to your users.

Hopefully you can now see the difference between the two terms, but if you have any more questions about either browser isolation or remote browsing, please get in touch. We have plenty of experience to bring to the table and can talk you through all of the different browser isolation technologies on the market.

Like the things we write? Follow @WEBGAP on Twitter for more!