Jump to content

Browser isolation

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Monkbot (talk | contribs) at 01:54, 17 December 2020 (Task 18 (cosmetic): eval 18 templates: del empty params (1×); hyphenate params (1×); cvt lang vals (1×);). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Browser isolation is a cybersecurity model which aims to physically isolate an internet user's browsing activity (and the associated cyber risks) away from their local networks and infrastructure. Browser isolation technologies approach this model in different ways, but they all seek to achieve the same goal, effective isolation of the web browser and a user's browsing activity as a method of securing web browsers from browser-based security exploits, as well as web-borne threats such as ransomware and other malware.[1] When a browser isolation technology is delivered to its customers as a cloud hosted service, this is known as remote browser isolation (RBI), a model which enables organizations to deploy a browser isolation solution to their users without managing the associated server infrastructure. There are also client side approaches to browser isolation,[2] based on client-side hypervisors, which do not depend on servers in order to isolate their users browsing activity and the associated risks, instead the activity is virtually isolated on the local host machine. Client-side solutions break the security through physical isolation[3] model, but they do allow the user to avoid the server overhead costs associated with remote browser isolation solutions.

Mechanism

Browser isolation typically leverages virtualization or containerization technology to isolate the users web browsing activity away from the endpoint device - significantly reducing the attack surface for rogue links and files. Browser isolation is a way to isolate web browsing hosts and other high-risk behaviors away from mission-critical data and infrastructure. Browser isolation is a process to physically isolate a user's browsing activity away from local networks and infrastructure, isolating malware and browser based cyber-attacks in the process while still granting full access.[4]

Market

In 2017, the American research group Gartner identified remote browser (browser isolation) as one of the top technologies for security.[5][6] The same Gartner report also forecast that more than 50% of enterprises would actively begin to isolate their internet browsing to reduce the impact of cyber attacks over the coming three years.

According to Market Research Media, the remote browser isolation (RBI) market is forecast to reach $10 Billion by 2024, growing at CAGR 30% in the period 2019-2024.[7]

Comparison to other techniques

Unlike traditional web security approaches such as antivirus software and secure web gateways,[8][9] browser isolation is a zero trust approach[10] which does not rely on filtering content based on known threat patterns or signatures.[11] Traditional approaches can't handle 0-day attacks[12][13][14] since the threat patterns are unknown. Rather, browser isolation approach treats all websites and other web content that has not been explicitly whitelisted as untrusted, and isolates them from the local device in a virtual environment such as a container or virtual machine.

Web-based files can be rendered remotely so that end users can access them within the browser, without downloading them. Alternatively, files can be sanitized within the virtual environment, using file cleansing technologies such as Content Disarm & Reconstruction (CDR), allowing for secure file downloads to the user device.[15]

Effectiveness

Typically browser isolation solutions provide their users with 'disposable' (non-persistent) browser environments, once the browsing session is closed or times out, the entire browser environment is reset to a known good state or simply discarded.[16] Any malicious code encountered during that session is thus prevented from reaching the endpoint or persisting within the network, regardless of whether any threat is detected. In this way, browser isolation proactively combats both known, unknown and zero-day threats, effectively complementing other security measures and contributing to a defense-in-depth, layered approach[17] to web security.

History

Browser isolation began as an evolution of the 'security through physical isolation' cybersecurity model and is also known as the air-gap model by security professionals, who have been physically isolating critical networks, users and infrastructures for cybersecurity purposes for decades. Although techniques to breach 'air-gapped' IT systems exist, they typically require physical access or close proximity to the air-gapped system in order to be effective. The use of an air-gap makes infiltration into systems from the public internet extremely difficult, if not impossible without physical access to the system . The first commercial browser isolation platforms[18] were leveraged by the National Nuclear Security Administration at Lawrence Livermore National Laboratory, Los Alamos National Laboratory and Sandia National Laboratories in 2009, when browser isolation platforms based on virtualization were used to deliver non-persistent virtual desktops to thousands of federal government users.

In June 2018, the Defense Information Systems Agency (DISA) announced a request for information for a "cloud-based internet isolation" solution as part of its endpoint security portfolio.[19] As the RFI puts it, "the service would redirect the act of internet browsing from the end user’s desktop into a remote server, external to the Department of Defense Information Network." At the time, the RFI was the largest known project for browser isolation, seeking "a cloud based service leveraging concurrent (simultaneous) use licenses at ~60% of the total user base (3.1 Million users)."[20]

See also

References

  1. ^ Miller, Daniel. "Cyber Threats Give Rise to New Approach to Web Security". Retrieved 2018-01-23.
  2. ^ "Remote Browser Isolation Market". Secjuice Infosec Writers Guild. 2018-06-28. Retrieved 2019-05-21.
  3. ^ "Security Isolation - an overview | ScienceDirect Topics". www.sciencedirect.com. Retrieved 2019-05-21.
  4. ^ "How Does Browser Isolation Work?". Expert Insights. 2019-09-19. Retrieved 2020-10-22.
  5. ^ "Canvas". Retrieved 10 May 2019.
  6. ^ "Gartner Identifies the Top Technologies for Security in 2017". Retrieved 2018-01-28.
  7. ^ "Browser as a Service Market Forecast 2019-2024". MarketAnalysis.com. 2018-09-12. Retrieved 2019-05-17.
  8. ^ "secure Web gateway - Gartner IT Glossary". www.gartner.com. Retrieved 2019-05-17.
  9. ^ Inc, Gartner. "Secure Web Gateways Reviews". Gartner. Retrieved 2019-05-17. {{cite web}}: |last= has generic name (help)[permanent dead link]
  10. ^ Pratt, Mary K. (2018-01-16). "What is Zero Trust? A model for more effective security". CSO Online. Retrieved 2019-05-21.
  11. ^ "Validating the Known: A Different Approach to Cybersecurity". www.idc.com. Archived from the original on 2018-01-23. Retrieved 2018-04-03.
  12. ^ Goodin, Dan (2016-11-30). "Firefox 0-day in the wild is being used to attack Tor users". Ars Technica. Retrieved 2019-05-17.
  13. ^ "Unpatched Zero-Days in Microsoft Edge and IE Browsers Disclosed Publicly". The Hacker News — Cyber Security and Hacking News Website. Retrieved 2019-05-17.
  14. ^ "Disclosing vulnerabilities to protect users across platforms". Google Online Security Blog. Retrieved 2019-05-17.
  15. ^ Toreini, Ehsan (2019). "DOMtegrity: ensuring web page integrity against malicious browser extensions". International Journal of Information Security. 18 (6): 801–814. doi:10.1007/s10207-019-00442-1. PMC 6777511. PMID 31632229.
  16. ^ "National Security Agency - Steps To Secure Browsing" (PDF). National Security Agency.
  17. ^ "What is Browser Isolation? - Definition from Techopedia". Techopedia.com. Retrieved 2019-05-22.
  18. ^ "Lawrence Livermore National Laboratory deploy disposable virtual desktops for browser isolation". Retrieved 2018-03-02.
  19. ^ [1]
  20. ^ [2]