The Chrome browser has almost become synonymous with security. Google is now increasing measures to keep users informed of unsafe browsing. The next phase of “Not secure” notifications will soon make their way to Chrome in an update expected to roll out in October.
Last September, Google announced that they would begin labeling HTTP sites as “Not secure” if they contained credit card or password fields. In January the first implementation these updates rolled out and users began seeing the new warnings.
Then next evolution of secure browsing will begin to label sites “Not secure” if they are HTTP and require users to type data of any type into a text field. The update will come in October of this year with the release of Chrome 62. Additionally, any incognito session on an HTTP site will result in a “Not secure” warning. Here’s an example of what to expect in the update.
According to the Google Security Blog:
there has been a 23% reduction in the fraction of navigation to HTTP pages with password or credit card forms on desktop, and we’re ready to take the next steps.
I do want to take a moment to clarify, these features do not by themselves a safer web make. This is Google’s way of making more clear the security of the sites that you browse. Whether or not you chose to share data with an non-secured webpage is ultimately in your hands.
If you doubt the security of your personal information on a given site I would recommend better safe than sorry. That’s the whole purpose behind these enhancements to Chrome, to help its users browse safer. Nothing is 100% secure but this is a big step in the direction of transparency on the web.
Stay safe and happy browsing. 🙂
Source: Google Security Blog
