Chrome for business added security—Isolated websites – Research Snipers

Chrome for business added security—Isolated websites

Google is continuously improving its products in terms of security and performance, the search engine giant has added more security controls to its G suite admins in July. Google also announced adding free antivirus to Chrome in October. Blocking auto-play videos in Chrome browser was another security and performance improvement by Google in September, but that would take effect from January according to Google.

In September, Google also took a decision to end Google Drive and Google Photos in September and replace them with something better, faster, reliable and more secure on the internet.

Yesterday, Google has started rolling out Chrome 63, with site isolation feature, Transport Layer Security (TLS) 1.3 for Gmail and granular settings for extensions. Google has rolled out 37 security fixes in the latest update.

With the site isolation feature, Chrome would now render the content for open sites in an individual process which is kept separate from other pages. If you do not want a blanket approach then you can easily create a list of sites that you wish to isolate.

Google recommends using it for your company intranet, the cost of the extra layer of protection will increase memory usage by 10 to 20 percent. As Chrome has been improved to the next level lately this offers much of a control to admins. Chrome 63 takes one step further it allows admins to restrict the number of extensions based on the permissions required such as access to mic or webcam.

The latest version of Chrome also includes TLS 1.3 for Gmail, a protocol for secure communications on the internet. Google said the previous standard version in 2008 needs an overhaul and TLS 1.3 would be faster and more secure, Google also has plans to bring it to the entire web in 2018. Google recommends admins to visit the feedback forum in order to ensure it’s running smoothly on your system.

In future, Google also has plans to include support for the NTLMv2 authentication protocol, which is default in Windows browser, according to the sources it would be default in Chrome 65 update as well.