What do we mean by GEN II security?
Many of the earlier adopters of public cloud took a lift and shift approach to migration. This means that the traditional security applications that we saw in the on-premise world have often found their way to public cloud environments. Because controls have been applied that were not designed with cloud in mind, there have been numerous breaches. This is partly because the challenge of securing the cloud wasn’t yet mature, but also because the tools to do it properly didn’t exist.
It is fair to say that attackers have been thriving in the past few years. Wherever there is uncertainty and complexity, attackers flourish. And that is certainly true in the cloud. Over the last 18 months, we have seen a vast array of both new attacks and new breaches.
Some attacks are born from attacker ingenuity – think Tesla’s, Aviva and Gemalto’s Amazon account getting cryptojacked. Some are born from companies struggling to successfully implement new ways of working and modernise their software development process securely, like Heartbleed. And others breaches are born from a combination of the two. For example, the all too common AWS storage misconfigurations like Lion Air.
We are now reaching a point where we are seeing security applications that are born in the cloud. But don’t let the “marketing jargon” fool you. The reason these exist is to address the quickly evolving but specific cloud security risks that we face.
I want to talk about a few examples that we’re seeing and why I believe they’re worth consideration. In true security language, all three are acronyms – don’t shoot the messenger.