Docker changed the way applications are built and helps developers simplify their workflows by integrating containers into the dev pipeline. Docker makes development and testing faster and fits well in DevOps practices, but containers require application teams to handle additional aspects of application security. In containers, developers are now responsible for system configuration and security - traditionally the realm of dedicated system administrators. This new accountability together with the pace in which new vulnerabilities are published and need to be addressed, has the potential to undo the speed benefits that come with Docker and containers..
Docker and Snyk have teamed up to solve this challenge. With the new Snyk <> Docker integration, container owners can now use a simple docker scan <image-name> command and get early visibility into vulnerabilities with the Docker CLI. The scan, powered by Snyk, provides you with not only the security issues, but also directs you to the exact place where you can fix them, without requiring you to track down each vulnerability individually.
This is partly due to one of the unique features of the Snyk-powered scan, which allows you to include the Dockerfile as part of the scan. Doing so not only helps you fix vulnerabilities much faster, , but can also present you with recommendations for alternative base images. These recommendations go hand-in-hand with Docker’s best practices to use minimal images, further helping you reduce security risks.
In this talk we will cover:
- How to scan container images and get Snyk intel directly from Docker Desktop
- The different use cases for using `docker scan` in your pipeline
- How you can integrate Snyk and Docker for continuous integrated security scanning, in your command line and throughout the SDLC
