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 didn't explain the complex differences between Chrome sandbox and Site Isolation, but according to company, the Strict Site Isolation feature puts "even stronger security boundaries between websites and Chrome's sandboxing technology."
However, this function is not activated by defaultchoice. The reason is that Google is still working on improving the feature. It also states that those of the browser users who activate the function in Chrome 63, "will increase memory usage by approximately 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
Select Properties
From tab Συντόμευση, στο πεδίο Προορισμός, προσθέστε το ακόλουθο κείμενο “–site-per-process” στο τέλος της διαδρομής της shortcut and press 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 have whitelist or blacklist in extensions used by Chrome users based on required permissions. For example, a domain administrator might 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 the protocol control NTLMv2 identity.
Password Managers locally or in the cloud?
