Policy-as-Code in the new cloud matrix

As we now build the cloud-native era of virtualised and abstracted architectures that run from datacentres to desktops and through the middle-ground network mesh of interconnectivity that joins every node and endpoint together, we can control cloud infrastructure and system health through policy-as-code.


In cloud, we build with code, of code and as-code. That truism obviously holds outside of cloud computing and predates any notion of cloud datacentre virtualisation. Software application development has always relied upon a core construction process where code is built, tested and deployed, but the way we talk about various digital entities as-code has evolved in cloud. This is largely as a result of the move to abstract every working element of the new IT stack as a software-based device, driver or dataset.

Figuring out misconfigurations

If there is a buzzword surrounding the global cloud advocate and evangelist community right now, then it is either hyperautomation or misconfiguration. Leaving the much-hyped area of hyperautomation aside for now, let’s think more practically about cloud misconfiguration.

Analyst house IDC estimates that some 67% of breaches in the cloud are caused by misconfigured applications or infrastructure. Clearly this means that while security remains a core concern for companies adopting cloud-native technologies, the need to control clouds in a more policy-enforced fashion is critical.

To continue reading this article register now