The Record Issue 13: Summer 2019

63 tool can interact with the underlying stack if desired, report back to it and even offer inde- pendent, automatic remediation of the problems it finds, including compliance, configuration or human errors. Why is this important? Well, the cloud is dif- ferent. The architecture is different. The under- lying planes have been deployed independently, unlike the traditional datacentre method. The deliberate separation of control, management and data planes allows for the fast performance that started the original cloud message. We now need a tool that can keep up with the pace and streamline the original way in which we diag- nose issues in the dispersed configurations. The third layer is more focused on how to introduce deeper intelligence, utilise machine learning and analyse threat data before it becomes possible to gather data in a more detailed fashion. Basically, a silent voice giving you permission to continue or not. A management tool which acts as a helping hand for development testing is every develop- er’s dream. Developers can now query this layer of protection to help with areas such as code creation. For example, once the initial version is deployed, they can run checks to make sure it is safe for the environment while checking for errors, taking guidance on corrections and even implementing the suggestions into the following version. Check again. Build. Check. Fix. Repeat. Change happens fast in the cloud, but speed is not necessarily the answer when it comes to the next layer of cloud security. Getting the best from the tools available today, and then layering new technology on top that complements the solid foundation, is a way of staying current, knowing you have a helping hand keeping the defensive walls in place, and being able to utilise tools that you don’t necessarily have the internal skills to benefit from. Chris Hill is regional vice president, Public Cloud International at Barracuda Networks