SAINTCON 2016 - Kevin Stultz - Docker Container Security

Discover the challenges and implications of container security in the post-traditional world, and learn how to adapt to the new realities of Docker and DevOps environments.

Key takeaways

Container security is different from traditional security approaches
Docker introduced a new way of packaging software, making it easier to deploy and manage applications
Containers have been widely adopted, with 12% of the Internet now running in containers
The traditional approach to security doesn’t work in a containerized environment
Containers are becoming more popular, especially in DevOps and cloud environments
The role of the security team has changed, as they need to adapt to the new technologies and ways of doing things
Containers are perceived as “stateless” and “unpatchable”, but this isn’t true
Docker provides some security features, such as Docker Hub and Docker Registry, but more work needs to be done
The limit registry access to sanctioned servers is a common and effective security practice
Enforce internal registry use is another important security practice
Isolating the containers from the host is critical for security
BusyBox is a set of Unix tools that is commonly used in containers, but it’s not a registry like one would think of on Windows
Non-Docker solutions and tools are emerging, such as DockerRun and a variety of other open-source tools
The security best practices for containers are different from those for traditional systems
The importance of driving adoption and acceptance of container security is crucial
Docker has released a tool to manage containers on top of containers
There is a growing need for container security tools that can work seamlessly with DevOps and automation
The future of container security is exciting, with many new tools and solutions on the horizon

SAINTCON 2016 - Kevin Stultz - Docker Container Security

More talks