Site Isolation for web developers
Website : Site Isolation for web developersPosted by Sapna Pandey on July 13,2018
Site Isolation for web developers | on July 16,2018
Chrome 67 has a new feature called site Isolation enabled by default on desktop. In this blog post I have explained what site Isolation is all about. Why it is required and why web developers should be aware of it.
Site Isolation is a defensive feature in chrome that offers an additional strategy of defense to make attacks less likely to succeed. It helps to block the process from receiving certain types of data from other sites. With the help of site Isolation it's much more difficult for malicious website to use speculative side-channel attacks like steal data from other sites. Site Isolation will also help when an attacker's page can break some of the rules in its own process.
When you enable site isolation, chrome aims to provide more security feature for your browser.
The extra security feature will help stop the site from stealing your data from another website.
Site isolation will increase chrome's memory use by approximately 10% and makes harder for untrustworthy websites to access or steal information from your accounts on ther websites. Site isolation reduces the amount of valuable cross-site information in a web page's process, and helps limit what an attackers could access.
HOW TO CONFIGURE
There are two ways to enable Site Isolation
1) Isolating All Sites
It is enabled by default for 99% of as of chrome users on windows, linux and chrome 67.
It can be enabled by following ways
Visit chrome: //flags#enable-site-per-process, click Enable, and restart. Or use command line flags to start chrome with site-per-process.
2) Isolating Certain Sites:- The main objective of this mode is to use less memory than isolating all sites. It is enabled by following ways start chrome with – isolate – origins followed by a comma- separated list of origins to isolate.
