From the course: Microservices: Security
Unlock the full course today
Join today to access over 24,900 courses taught by industry experts.
Container runtime security
From the course: Microservices: Security
Container runtime security
- [Instructor] To receive the full benefits of a microservice architecture, it takes a flexible execution environment that allows for rapid yet stable deployments. This is why the majority of developers choose to deploy microservices inside of containers. And in most cases, that means Docker. Like each new technology in the stack, containers have their own attack surface and expose new attack vectors. When running microservices on containers, security measures can be applied to harden various components within the architecture, including the host and the container runtime. The host where the container engine is installed is a starting point for securing the container platform. It should have a very limited number of users that can access it directly. If you're using a container orchestrator like Kubernetes, this number should be even smaller, because the need to access the host is diminished. When choosing an operating…
Contents
-
-
-
-
-
-
-
Throttling and rate limiting4m 37s
-
(Locked)
Container runtime security4m 19s
-
(Locked)
Image security5m 4s
-
(Locked)
Audit container security3m 44s
-
(Locked)
Secrets management3m 49s
-
(Locked)
Secure pipelines4m 57s
-
(Locked)
Prevent leaked credentials2m 39s
-
(Locked)
Keep secrets with Key Vault6m 53s
-
-