Breaking Isolation: Is browser isolation sacrilege or a shrewd choice?

Technology often mirrors models found in the physical world.  Browser isolation brings the self-quarantine model to mind.  Both are about maintaining Zero Trust and never breaking the barrier between two things.  Self-quarantine isolates you from other people protecting the general population until you know if you are infected.  Browser isolation separates your web browsing from your local network, so nothing harmful can touch your endpoints.  In theory, rigorously following browser isolation will keep you safe. But what about times when a web app isn’t good enough and you need to work on your desktop?  Should you succumb to temptation and take an easier route to completing your work or stay safe yet unproductive?

Why would one ever need to break isolation?  Browser isolation solutions enable users to view and edit documents in the browser without downloading native files to the endpoint.  But there will always be some users who need to use tools that don’t run in a web browser. When users work on files on their desktop, it breaks isolation and puts them and their organization at risk.  Even with administrative controls managing the document downloads and uploads, there is a risk that the files that touch the endpoint will contain a known or unknown threat.

What’s the solution?  Integrating a threat detection service with browser isolation mitigates this risk while enabling end-users to do their work in the most productive environment.  A threat detection service scans content and files for threats, including unknown threats and Zero-day attacks, before they leave browser isolation and touch the endpoint.  The integration is seamless to the customer while providing the best of both worlds for endpoint protection.

Learn more about threat detection services integrated into remote browser isolation solutions here.

The post Breaking Isolation: Is browser isolation sacrilege or a shrewd choice? appeared first on Blog.

*** This is a Security Bloggers Network syndicated blog from Blog authored by John Klassen. Read the original post at: