Free Trial
Schedule Demo
Comments
Linux Containers, such as LXC & Solaris zones, have existed since the mid 2000s. However, containers weren’t widely used outside of large tech companies such as Google until Docker was first released at PyCon in March 2013 followed by the replacement of LXC with libcontainer as the default execution environment in March 2014. According to the 2017 Docker Adoption survey by Datadog, containers started seeing adoption for the building of cloud native apps and microservices starting in 2014. So naturally, organizations are in various stages of Docker adoption:
As with the introduction of any new technology, a majority of organizations fall into the “early adopter” or “intermediate” maturity categories for deploying Dockerized apps in production. In addition to development and deployment best practices, these organizations are also trying to determine how to meet the security and compliance requirements for Docker images and containers. And as the Docker security and Containers do not contain articles highlight, there are several security issues that container adopters need to solve.
As a security professional, I can say from experience that security is never perfect. You can’t do everything, so solutions to security issues need to be prioritized according to risk, cost of implementation and impact. With that in mind, if you are an early or intermediate adopter of Docker containers, be sure to focus on these five areas when formulating your security and compliance programs:
If none of the above comes as a surprise to you then stay tuned. In the coming month we’ll be discussing the top tips to secure containers for advanced adopters.