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.

Via a Chrome flag

Step 1: Type chrome://flags and press Enter.
Step 2: Scroll down the page and find “Strict site isolation” and press the Enable button. Alternatively, copy and access the following URL to take you to the Site Isolation flag directly: chrome://flags/#enable-site-per-process
Step 3: Restart the Chrome browser.

Via a command line flag

Step 1: Find your Google…

Continue ….