One of the major problems with setting up HTTPS is that adding the cert is just one aspect of what can be a long process. One of the hurdles is knowing which headers to use to help make the site as secure as possible. For that reason, I put together
There is a story doing the rounds that the US Government is pissed off at Intel because Intel kept quiet about Meltdown and Spectre, it seems that the disclosure only happened after the vulnerability became public which was some six months after Intel were first told about it. The US
One of the things I'm passionately in support of is HTTPS everywhere. That is, every single website using HTTPS. It doesn't matter if it's a simple text site or if it's a full blown corporate webpage, it should be using HTTPS.
I also promote going beyond HTTPS on websites which
2018 is certainly kicking off with an interesting set of security issues that affect all processors in use today, Intel, AMD, ARM and so on.
In short the three vulnerbilities are:
Azure and AWS have already patched their hosts. They were one
I think I may have invented a new phrase today “GDPR Hysteria”, it’s when a company/management team/data protection officer takes the requirements of GDPR and dials them up 11 and this is something I’ve seen a few times now and I’m quite at a loss