If you ask most people who work in our industry to describe the difference between HTTP and HTTPS, they might say the latter is the secure version. They may even go further and explain that HTTPS uses an SSL certificate to secure the connection between the user’s web-browser and the web-server hosting the web-page.

But surprisingly, many do not know the details of how an SSL certificate works; the reliance on third-party trust, and why we will soon be facing a wave of problems with root certificates expiring.

Whether you’re trying to increase revenue, reach, engagement or simply integrate systems, Application Programming Interface (API) utilisation is a must. We are in the age of big data, AI and machine learning, and there is no better way to exploit these data sources across multiple platforms and services than through the utilisation of APIs. APIs are no longer created just to meet a technical requirement, they are published with specific business goals in mind. With all of the big players out there offering a vast range of APIs, coupled with its wide spread adoption, the security implications were always going to be significant.

Big network breaches are becoming the norm with little resistance seemingly being placed in the attackers path. Is this the world we must become accustomed to living in? or can technology be part of the solution rather than just the problem?

It is the stuff of legend that at the advent of the internet, there were no IT security advocates present to argue the case against a future such as ours and the character S was deemed an unnecessary inclusion to protocols such as HTTP (Hyper Text Transfer Protocol).