From the course: Microservices Security Workshop: From Build to Production

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Container scanning

Container scanning

From the course: Microservices Security Workshop: From Build to Production

Start my 1-month free trial Buy for my team

Container scanning

“

- [Instructor] Okay, I have to come clean. When I said we were done with scanners, there's actually two more kinds of scanning. The most common type of artifact used in microservice environments is the container. While containers make application delivery fast and predictable, they also introduce a ton of security considerations. One of the most common points of confusion for teams is figuring out where and how to scan containers for vulnerabilities. There are multiple scanning points: development, build, deployment, runtime. Each one of these scanning points introduces different issues. So in this lesson, we'll first break down what a container is made of and then explain what each scanning location reveals. At a basic level, a container starts with a base image. In our example microservices, we've been using the Python:3.x-slim image, which is a pared down version of Debian Slim, designed to keep container sizes manageable. This slim variant is common for microservices because it…

Contents