{"id":28451,"date":"2018-01-04T11:00:00","date_gmt":"2018-01-04T11:00:00","guid":{"rendered":"https:\/\/futurelab.digitalmachine.co.nz\/blog\/important-security-update\/"},"modified":"2018-01-04T11:00:00","modified_gmt":"2018-01-04T11:00:00","slug":"important-security-update","status":"publish","type":"post","link":"https:\/\/futurelab.digitalmachine.co.nz\/nz\/blog\/important-security-update\/","title":{"rendered":"Important Security Update"},"content":{"rendered":"\n

Dear FutureLab customer, this news is important, so please take time to read it<\/h2>\n\n\n\n

First of all, Happy New Year. We value your time, especially at this time of the year, and we understand that a lot of the news here will be very technical, which is why you\u2019ll find a handy summary at the end of the newsletter.<\/p>\n\n\n\n

A big bug has been discovered in every single computer<\/h2>\n\n\n\n

For the last couple of months, two separate teams have been investigating a potential security issue affecting every single computer, phone, tablet \u2013 every device that has a processor. They have discovered that with some technical tricks a hacker can access the information from any program that is currently processed on the machine. This means passwords, secure information, essentially anything. Most processors are affected.<\/p>\n\n\n\n

FutureLab were notified by our hosting supplier Amazon Web Services (AWS) in November, with AWS scheduling a software update for the 5th January. The reason that bugs are not publicly announced is to give software companies like AWS, Microsoft, Apple etc time to work on a fix before hackers have a chance to find out and exploit the bug. We have been patiently preparing for the update to arrive; however, news of the bug was leaked to the public domain on the 3rd of January, which meant we needed to work more urgently to get a fix in place.<\/p>\n\n\n\n

The team at Google that discovered the bug also prepared a website explaining both vulnerabilities.<\/p>\n\n\n\n

View the website with the bug details.<\/a><\/p>\n\n\n\n

What has happened since last night? Amazon has been updating underlying software for a while now and most of the servers are secure and up to date (more information<\/a>).<\/p>\n\n\n\n

We’ve been working hard to update all servers to the latest software, however, the distribution that we’re using has not yet released a security patch (more information<\/a>).<\/p>\n\n\n\n

There are two bugs, \u2018Meltdown\u2019 and \u2018Spectre\u2019. The updates we are referring to relate to the Meltdown bug. As far as we understand it, there is not yet a solution for Spectre as it is a much more complex issue to resolve. It has been estimated that the fix for the Spectre bug is going to slow down every machine by about 5%, but in some cases even up to 60%.<\/p>\n\n\n\n

What does the above mean for you? Our architecture is quite complex and looks like the below<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

This means your website is using a lot of servers for processing. Most importantly, each of those servers are in the cloud, which means that you won\u2019t get the same server processing your website each time \u2013 it\u2019s an \u2018on demand\u2019 service. Since AWS have already updated their underlying software, that means that all FutureLab customers are secure from any other processings on AWS. However, because there’s no solution for Ubuntu (the Operating System we’re using on our servers) as yet, there’s still a small internal risk for FutureLab customers. We’re monitoring updates and as soon as they are ready we will get to work patching the machines.<\/p>\n\n\n\n

Lastly, since last night FutureLab and AWS have both performed a lot of work to ensure that the software is updated to the most recent and most secure version. We needed to make a lot of restarts and updates on our hosting machines. Our updates were completed around 11am this morning. What this means is that your website may<\/strong> have been offline anytime between 11pm last night to 11am this morning.<\/p>\n\n\n\n

If there are any issues with your website, please let us know.<\/p>\n\n\n\n

Summary<\/h3>\n\n\n
\n