Controlling and monitoring your cloud environments is vital to secure your data. In this article, we will compare the tools to monitor and control your cloud environments for Azure, AWS and Google Cloud Platform. Additionally, learn how Cloudockit can help you ensure your environments are conform with your plans.
Cloudockit’s Compliance Rule features allows you control but stay agile instead of blocking and preventing users from working in the cloud. With Cloudockit, you will have the ability to create advanced rules yourself instead of being constraint to Azure, AWS or GCP limited rules. In addition, you will be able to make all your changes in Cloudockit’s Graphical User Interface (GUI) instead of having to manipulate JSON files.
Finally, Cloudockit is a true Multi-Cloud Management tool, therefore you will not have to define rules individually for each cloud provider.
Let’s have a look at the different options that we offer with the compliance rules in Cloudockit.
You can access this section clicking on the Compliance Tab
As you can see, there are some built-in rules. Click on one of them to see how it is structured:
I am text block. Click edit button to change this text. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.
A Compliance Rule is mainly compound of two parts:
In the previous, screenshot, the rule CDK-AppService-RemoteDebuggingEnabled objective is to ensure that App Services do not have Remote Debugging Activated.
The trigger is as follow:
With this rule, you want to ensure that no Virtual Machine should contain a NIC that has an NSG that contains a rule whose address prefix is *. Notice that you can build even more complex rules by using Group and AND/OR Conditions.
These rules are available to AWS, GCP and Azure so you do not need to learn multiple syntaxes.
Additionally, Cloudockit will gives you the warnings that you want but it will also automatically generate your Azure, AWS and Google Cloud Platform Documentation & Diagrams to ensure your environment is compliant. Indeed, compliance is not only a matter of ensuring that some technical best practices are met but it is also ensuring that what has been architected is what is deployed: that’s where automatic document & diagrams generation comes into play.