Chrome 63 is now officially released and it fixes multiple security issues.
The latest technical aspect behind the browser’s release is site isolation where enterprise IT administrators can now make it so Chrome renders content for each open website in a separate process, isolated from other websites.
In addition, the update includes 37 security fixes, according to a Google security advisory.
Site isolation can end up enabled for all websites, or for a list of specific websites, said Matt Blumberg, product manager for Chrome Enterprise at Google in a blog post.
If they choose not to enable either of these two isolation policies, Chrome will continue with its old policy: One tab, one process.
The goal of site isolation is to create an additional security boundary between websites, so it makes sure a new process is started each time a new domain is visited.
This increased security, however, comes with a price: Site isolation will increase Chrome memory usage by up to 20 percent.
In addition to whitelisting and blacklisting specific extensions, IT admins will, from now on, be able to block the use of Chrome extensions based on which permissions they ask.
“For example, through policy, IT can now block all extensions that require the use of a webcam or microphone, or those that require access to reading or changing data on the websites visited,” Blumberg said.
Chrome 63 also comes with support for TLS 1.3, the most recent version of the Transport Layer Security cryptographic protocol.