We talk a lot about security here in our blog, but we can’t stress it enough. Online security is such a huge talking point now as more and more things that we use on a daily basis are connected to the internet. For sometime now Google, and other browser providers, have been making a push to make the web a more secure place. Well, here comes a big change to that effect.
Coming this month (January 2017), with the release of Google Chrome 56, any website that has a password field or collects credit card information, and is not protected with an Secure Socket Layer (SSL) already, will be flagged by Google as insecure.
What does this mean for you and your website?
If you have a website that utilizes a login with a password or collects credit card information, this means that the browser will denote your website as Not Secure, when viewing pages on your site that invoke these functions. To the end user they will see a notation in the url bar that the site is Not Secure. This will not however effect the functionality of your website. Users will still be able to login to your site and use it as they always have. That said, when collecting sensitive information like credit cards or social security numbers, then you should have an SSL no matter what.
What can you do about this?
To prevent your site from being shown as insecure, you can get an SSL for it. A SSL is a layer of security that is laid over your site to encrypt any communication with the server. This helps to keep passwords, credit cards, and other information secure when transmitting it between the browser and the server.
SSLs are usually a paid for service. The cost usually depends on the provider that you choose, how many years you get the SSL for, and the type of SSL you choose. Some common SSL providers are: Comodo, GoDaddy, SSLs.com, but there are plenty to choose from, so do your research and pick the best option for your business.
Are you are Sephone customer? We can help get an SSL for your website. Give us a call today, or email us at firstname.lastname@example.org to get started.
For more information, you can read how Google is moving toward a more secure web here.