The Google Chrome 63 released yesterday, brought a new experimental feature called Strict Site Isolation.
According to Google developers it is an additional level of security in its built-in sandboxing technology Chrome.
Google developers have not explained the intricate differences between the Chrome sandbox and Site Isolation, but the company says Strict Site Isolation sets "even stronger security boundaries between websites and Chrome sandboxing technology."
This feature, however, is not enabled by default. The reason is that Google is still working on improving the feature. He states that those of the browser users who activate the function in Chrome 63, "will increase the memory usage by about 10-20%".
If using the above memory is not a problem for you, below we will see two ways to activate Strict Site Isolation.
Via Chrome flags
Type chrome: // flag and press Enter.
Find the "Strict isolation site" and press the Enable button. Alternatively, copy and paste the following URL into the Chrome address bar:
chrome: // flags / # enable-site-per-process
Restart Chrome.
Via Shortcut
Find the Google Chrome icon or shortcut and double-click it click get him
Select Properties
From the Shortcut tab, in the Destination field, add the following text “–site-per-process” at the end of the shortcut path and click Apply and OK.
See the picture
Strict Site Isolation is part of a wider range of features included in Chrome 63 specifically for business use.
Other new business features for Chrome are:
- Domain administrators can now whitelist or blacklist to the extensions that Chrome users use based on the required permissions. For example, one Admin domain can issue a company-wide group policy and block all Chrome extensions that request permission to use the PC camera.
- Chrome 63 now supports the latest TLS 1.3 standard
- Chrome 63 supports NTLMv2 authentication protocol.
Password Managers locally or in the cloud?
