With Browser Isolation, you can define policies to dynamically isolate websites based on identity, security threats, or content.
When an HTTP policy applies the Isolate action, the user’s web browser is transparently served an HTML compatible remote browser client. Isolation policies can be applied to requests that include
Accept: text/html*. This allows Browser Isolation policies to co-exist with API traffic.
The following example enables isolation for all web traffic:
If instead you need to isolate specific pages, you can list the domains for which you would like to isolate traffic:
Do Not Isolate
You can choose to disable isolation for certain destinations or categories. The following configuration disables isolation for traffic directed to
|Host||In||Do Not Isolate|
The following optional settings appear in the Gateway HTTP policy builder when you select the Isolate action. Enable these settings to when users interact with untrusted websites in the remote browser.
Disable copy / paste
Prohibits users from copying and pasting content between a remote web page and their local machine.
Prohibits users from printing remote web pages to their local machine.
Prohibits users from performing keyboard input into the remote web page.
Prohibits users from uploading files from their local machine into a remote web page.
Prohibits users from exporting files from the remote browser to their local machine.
Isolate all security threats
Isolate security threats such as malware and phishing.
|Security Risks||In||All security risks||Isolate|
Isolate high risk content
Isolate high risk content categories such as newly registered domains.
|Content categories||in||Security Risks||Isolate|
Isolate news and media
Isolate news and media sites, which are targets for malvertising attacks:
|Content categories||in||News and Media||Isolate|
Isolate uncategorized content
Isolate content that has not been categorized by Cloudflare Radar:
|Content categories||not in||All content categories||Isolate|