Isolating Web Browsers

How does isolation prevent HEAT attacks?

Isolation technologies create a protective layer between the user and the Internet by moving all web requests to a remote browser inside an isolation platform. This remote browser would make the request on the user’s behalf, download the code, and execute all active content inside of the isolated container and send only a clean, sanitized visual layer down to the endpoint. This effectively cuts off all attempts to deliver any form of HEAT attacks. Without access to the network or endpoints, malware cannot spread laterally through the network in search of valuable targets and are unable to deliver its final payload.

How does isolation technology impact the end user experience?

Isolation technology shouldn’t impact the native user experience at all. Latency should not increase. Users shouldn’t have to use a custom browser. And basic web functionality such as print, cut and paste should not be impacted. In fact, most users shouldn’t be aware that they are being protected by isolation technology. Unfortunately, some isolation technologies do impact the native user experience and are a drain on user productivity.

What are three features should buyers consider when buying an isolation solution?

Isolation solutions should have built-in architecture components that preserve bandwidth, scale across the entire organization and preserve the native browser experience for users. Many isolation technologies consume an enormous amount of bandwidth, forcing customers to limit isolation policies to certain traffic type, users or locations. DOM mirroring minimizes bandwidth usage inside the isolation browser—allowing organizations to employ an isolate everything policy scaled across the entire organization. In addition, users need to use the Internet like they’ve always done before. Isolation shouldn’t mean slow experience, limited functionality or a new browser to learn.