What Is The Difference Between Browser Isolation & Remote Browsing?

Browser isolation is a cybersecurity model that physically isolates an internet users browsing activity away from their local machine and network, it is the underlying model and technology that supports a remote browsing platform.

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 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 we at WEBGAP have our own remote browsing platform, we do not think of our technology as 'remote browsing tech', primarily 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, or their own teams of developers working on it, partly why they think of what they do as remote browsing instead of browser isolation.

Browser isolation technology and the browser isolation model is what underpins a remote browsing platform.

WEBGAP is able to offer our customers and partners 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. My team and I were present at the birth of the browser isolation space and helped the US federal government develop the first commercial browser isolation platforms, 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.

If you are looking for a cost-effective way to physically isolate your users browsers and internet browsing activity, have a browse through our website and check out our browser isolation technology and our remote browsing solution.

EDITORIAL NOTE: What’s that? You like the things we write? Follow @WEB_GAP on Twitter for more!

Previous PostThe WEBGAP Engine
Next PostWhat Is Remote Browsing?