From the course: Kubernetes and Cloud Native Security Associate (KCSA) Cert Prep
Join today to access over 23,400 courses taught by industry experts.
The four Cs of cloud native security
“
All right. The four Cs of cloud native security. Now, this isn't just Kubernetes-specific, although what you're going to see is a lot of these topics of course fall under the Kubernetes realm. So first, we have cloud, we have clusters, containers, and code, okay? So the cloud. What does this mean? Well, it's everything that you control. So in many ways, the cloud or co-located server in a cloud provider or corporate data center, whatever it is, is the trusted computing base of a Kubernetes cluster. If the cloud layer is vulnerable or configured in a vulnerable way, then there is no guarantee that the components built on top of this base are secure. So each cloud provider makes security recommendations for running workloads securely in their environment and to cause a bit more confusion, each cloud is going to have its own product or tool. From a security perspective, this isn't necessarily a bad thing because they're kind of all the same at the end of the day, but every cloud provider…
Contents
-
-
What is cloud native security?
1m 52s
-
OWASP Kubernetes Top 10
2m 7s
- (Locked)
What is infrastructure security?
1m 26s
- (Locked)
The four Cs of cloud native security
3m 29s
- (Locked)
Cloud provider and infrastructure security
4m
- (Locked)
Isolation techniques
1m 42s
- (Locked)
Artifact repo and image security
1m 39s
- (Locked)
Workload and app code security
4m 38s
-
