not secure message...but if nothing is being protected it's not really an issue, is it?

In late July, 2018, Google Chrome started displaying a prominent ‘NOT SECURE’ message in the browser with the release of version 68 for any webpage not using HTTPS.

For most websites, the Chrome ‘NOT SECURE’ warning is not much of a cause for concern, just like an unlocked garden shed isn’t much of a security concern if there’s nothing in the shed.

But to better understand how much of a security risk is involved with Chrome’s ‘NOT SECURE’ warning, we need to explain how to make websites secure and what ‘being secure’ means.

How HTTP and HTTPS Work

When you connect to a website with regular HTTP, your browser looks up the IP address that corresponds to the website. Then, it connects to that IP address and assumes it’s connected to the correct web server. Data is sent over the connection in clear text. An eavesdropper on a Wi-Fi network, your internet service provider, or government agencies can see the web pages you’re visiting. In addition, they can see the data you’re transferring back and forth. Problems with HTTP include no actual verification that you’re connected to the correct website. That information can actually be read by someone who with access to it. Credit card numbers should never be sent over an HTTP connection as an eavesdropper could steal them.

These problems occur because insecure HTTP connections are not encrypted whereas HTTPS connections are encrypted. HTTPS connections require an SSL certificate in which an independent 3rd party verifies that the website is who it says it is.

Chrome and Firefox already warn when web pages ask for login or credit card information without using HTTPS. However, after this release, all web pages that load without HTTPS will display the warning.

Previous versions of Chrome notified users of HTTP-only sites by displaying an exclamation point next to the URL. Google believes this new  ‘NOT SECURE’ warning will help users understand that HTTP sites are not secure and continue to move the web towards a secure web.

Chrome of old without not secure warning on http website
Older Chrome without not secure warning on http
New Chrome with not secure warning on http website
New Chrome with not secure warning on http website

What Does This Change Mean?

After  released  of this browser version, many website now display this Chrome ‘not secure’ warning.  This Chrome ‘not secure’ warning should not be a major cause for concern. On a webpage that is NOT requesting any sort of user input has minimal risk of anything malicious happening. The warning alerts people that any data that they enter on a webpage that does not use an SSL could potentially be compromised.  HTTPS encrypts the data that is sent from your computer to the web server.

So, if you currently have a website that is not using HTTPS, the big question is: Do you need to be HTTPS?  In order for a website to be HTTPS, you must acquire and install an SSL certificate. In addition, some work is involved to re-configure the website to use them. However, the question of whether or not you will decide to use one going forward is individual preference for both you and your users. If your users are security conscience  then you might want to make your site secure.

And in the Future?

Google is leading the way to make the entire web secure. Thus, making your site secure is something you’re probably going to have to do. New sites should certainly consider being secure and any site requesting confidential information need to be secure. Beyond that, being secure is certainly a good idea for industries where security is important. This can range from web developers to medical and insurance.

At Bower Web Solutions we’d be glad to discuss your security issues and needs. Feel free to contact us to discuss.