Container security policy configuration
A traditional security policy model doesn’t work with containers. The hard part is applying those policies to different containers as they change in your infrastructure. We need a security policy model that can adapt dynamically to orchestration platforms like Kubernetes and Cloud Native apps.
Here are a few examples of what these policies might be protecting against:
- A database container opening an unexpected outgoing connection
- A privileged container trying to change the execution namespace
- A Kubernetes pod trying to read a secret after launch
Sysdig offers the first unified approach to container security, monitoring, and forensics. Sysdig Secure enables security teams to define a global policy to audit, enforce compliance and security best practices, while service owners are allowed to setup the specific security policy of their applications, detect anomalous activity and block threats.