Google has gone full speed in its effort to ensure that every website is HTTPS compliant, as it releases a roadmap for signaling encryption in Chrome browser.

Beginning from October, Google will start marking HTTP sites (non-encrypted websites) as "affirmatively non-secure" in Chrome's address bar. While Chrome will also tag the pages with a red "Not Secure" marker when users enter any kind of data.

According to the Chrome security team, marking all HTTP pages as 'not secure' is a step towards removing Chrome's positive security indicators so that the default unmarked state is secure.

Formerly, HTTP sites were still on the high side to warrant marking all the sites with a strong red warning, but recently the number of HTTPS compliant pages far out number the non-secure sites.

So users should expect that the web is safe by default, and they’ll be warned when there’s an issue, as Chrome’s default unmarked state is now secure. Chrome will roll this out over time, starting by removing the “Secure” wording and HTTPS scheme in September 2018 (Chrome 69).

Albeit, Google had previously announced its signage changes, but now it's taking several more steps along this path.

Google's roadmap for signaling encryption in Chrome browser



Google has gone full speed in its effort to ensure that every website is HTTPS compliant, as it releases a roadmap for signaling encryption in Chrome browser.

Beginning from October, Google will start marking HTTP sites (non-encrypted websites) as "affirmatively non-secure" in Chrome's address bar. While Chrome will also tag the pages with a red "Not Secure" marker when users enter any kind of data.

According to the Chrome security team, marking all HTTP pages as 'not secure' is a step towards removing Chrome's positive security indicators so that the default unmarked state is secure.

Formerly, HTTP sites were still on the high side to warrant marking all the sites with a strong red warning, but recently the number of HTTPS compliant pages far out number the non-secure sites.

So users should expect that the web is safe by default, and they’ll be warned when there’s an issue, as Chrome’s default unmarked state is now secure. Chrome will roll this out over time, starting by removing the “Secure” wording and HTTPS scheme in September 2018 (Chrome 69).

Albeit, Google had previously announced its signage changes, but now it's taking several more steps along this path.

No comments