Section 10.4 4C’s of Cloud Native Security
When reflecting on how to secure an application running in the cloud, a common tactic is to look at the four Cs involved:
-
Code: How secure is the code of the application? Is it configured correctly? Is it subject to buffer overflows or other issues? If the code isn’t secure, the application never will be
-
Container: How secure is the container itself? Are there limits to what the container has access to? Does the Linux distribution on the container have known vulnerabilities? Is the code running as a privileged user on the container?
-
Cluster: The container orchestration system is going to run on a cluster, how secure is this cluster? Has the container orchestration system been configured correctly? Is the virtual network being used secure? Are its ingress and egress points mapped and monitored?
-
Cloud: Is the cloud provider you are using secure? If they have been compromised everything within them is compromised. Can you trust this computing base?
You have attempted 1 of 1 activities on this page.
