Here's How to Enable Chrome "Strict Site Isolation" Experimental Security Mode By

[Solarquest]

Google Chrome 63, which shipped yesterday evening, arrived with a new experimental feature called Strict Site Isolation that according to Google engineers is an additional security layer on top of Chrome's built-in sandboxing technology.

While Google engineers have not explained the intricate differences between the default Chrome sandbox and Site Isolation, according to Google, the Strict Site Isolation feature puts "even stronger security boundaries between websites than Chrome’s existing sandboxing technology."

This is how Google describes the Strict Site Isolation feature in a support page:

Google’s site isolation feature improves security for Chrome browser users. When you enable site isolation, content for each open website in the Chrome browser is always rendered in a dedicated process, isolated from other sites. This creates an additional security boundary between websites.
The feature is not enabled for all users by default. The reason is that Google is still working on improving Site Isolation, and says that if users turn it on in Chrome 63, they "will increase memory usage by approximately 10–20%."

If this is not an issue for some of our readers, these are the two easiest ways to enable Site Isolation right now.
...
...

 

[vtqhtr413]

Google Chrome 63, which shipped yesterday evening, arrived with a new experimental feature called Strict Site Isolation that according to Google engineers is an additional security layer on top of Chrome's built-in sandboxing technology.

While Google engineers have not explained the intricate differences between the default Chrome sandbox and Site Isolation, according to Google, the Strict Site Isolation feature puts "even stronger security boundaries between websites than Chrome’s existing sandboxing technology."

This is how Google describes the Strict Site Isolation feature in a support page:

Google’s site isolation feature improves security for Chrome browser users. When you enable site isolation, content for each open website in the Chrome browser is always rendered in a dedicated process, isolated from other sites. This creates an additional security boundary between websites.
The feature is not enabled for all users by default. The reason is that Google is still working on improving Site Isolation, and says that if users turn it on in Chrome 63, they "will increase memory usage by approximately 10–20%."

If this is not an issue for some of our readers, these are the two easiest ways to enable Site Isolation right now.
...
...

For me a 10 to 20% memory hit right now is a deal breaker but I'm sure google will improve that. Appreciate their software and your postings.

Will give it a while before I turn it on so don't need the invisible instructions you posted.
Just pulling your leg Solorquest, big fan.

 

[Deleted member 178]

the invisible instructions you posted.

 

[Deleted member 178]

@BryanB click the link above the OP

Personally i have enabled it since quite a while now (maybe v61-62)

 

[vtqhtr413]

You made me have to edit my post to solorquest.:devil:

 

[DeepWeb]

Just checked to enable it and apparently I already had it enabled? Is this really a new feature or just a rebranding of something that has been there already?

Also they changed the design of the chrome://flags. That should be the bigger news.