{"id":5519,"date":"2017-12-08T10:15:08","date_gmt":"2017-12-08T15:15:08","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=5519"},"modified":"2020-12-09T13:43:19","modified_gmt":"2020-12-09T18:43:19","slug":"security-changes-in-chrome-63","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/security-changes-in-chrome-63\/","title":{"rendered":"Security Changes in Chrome 63: TLS 1.3, Site Isolation Security & More"},"content":{"rendered":"

What are the new security changes in Chrome 63? Let\u2019s find out.<\/h2>\n

There are myriad security changes in Chrome 63 – a host of updates & improvements, and of course, the much-awaited TLS 1.3. This new version of Chrome is likely to be rolled out in the upcoming days\/weeks. As far as the security changes go, there are lots of them. Whether it\u2019s security patches, UI changes, or developer features, Chrome has taken strides in almost every department. Unsurprisingly, two of these enhancements have grabbed the most attention \u2013 Site Isolation Security<\/strong> and TLS 1.3<\/strong>. Let us hash out these features for you.<\/span><\/p>\n

Site Isolation: One Process for One site<\/h2>\n

One of the biggest security changes in Chrome 63 is Site Isolation. The Site Isolation feature is exactly what it sounds like \u2013 it isolates a site. Admins will be able to activate this feature for one or more sites to ensure that these sites run on separate processes. Once activated, Chrome processes each open website\u2019s content as a separate process.<\/p>\n

Or, to put it more simply, every tab you open will now be running independently, rather than sharing resources.<\/p>\n

Because it treats each site as an individual process, the chances of one site crashing your browser are almost eliminated. If one tab crashes, your operations in other tabs will remain unaffected<\/strong>, so no more banging your head against your desk when you get that error and your browser freezes.<\/p>\n

The main reason behind introducing this feature (apart from maintaining your head symmetry) is the security needs of Chrome\u2019s enterprise\/corporate users where security is of paramount importance. Site Isolation<\/a> creates a \u201cwall\u201d between the pages that doesn’t let two or more pages communicate with each other (Yes, they do gossip!). As a result, attacks that target Chrome\u2019s renderer process by infusing malevolent code in Chrome\u2019s Sandbox process can be circumvented.<\/p>\n

Every good thing comes at a price and Site Isolation is no different. Enabling it may increase your Chrome\u2019s memory usage by 10-20 percent<\/a>.<\/p>\n

An excellent feature nonetheless!<\/p>\n

TLS 1.3 is finally here (Well, almost!)<\/h2>\n

Another big security change in Chrome 63 – the biggest as it pertains to us – is support for TLS 1.3.<\/p>\n

Yes sir, after a long wait<\/a>, TLS 1.3 is finally ready to go public. Granted, there were some platforms already running TLS 1.3, but it\u2019s a whole new ball game when a platform as popular as Chrome adopts it. For now, Google is rolling out TLS 1.3 only for Gmail as of right now.<\/p>\n

In 2018, Google will roll out TLS 1.3 to the entire web, making encrypted communications faster and more secure.<\/p>\n

If you\u2019re just hearing about TLS 1.3, it\u2019s the long-awaited successor to TLS 1.2 (duh) and it should improve security and performance considerably over its predecessors. We\u2019ll likely have additional coverage and advice as we see wider TLS 1.3 adoption.<\/p>\n

TLS 1.3 improves performance, efficiency, and security by removing support for older broken cryptographic protocols, ciphers and algorithms such as:<\/p>\n