Chapter 7. Supply Chain Security
Anyone deploying container images needs to have confidence that the software within each image is safe to run and has not been tampered with at any point. In this chapter, let’s look at how you can securely build and distribute container images along with information that reassures the user about its integrity and provenance.
Supply chain security is concerned with making sure that the software you deploy and run is what you expect it to be, having been built from source code that you trust, by a build system that you trust. There are various potential weak points in the chain, from building and storing an image to running the image, as shown in Figure 7-1.
Figure 7-1. Image attack vectors
Container Image Software Components
Container images can contain lots of different software components:
As you saw in Chapter 4, a container image includes a filesystem, often based on a Linux distribution, containing all the files and directories included in that distribution.
Distributions typically support a package manager like
aptoryum, and the container image might have some of these packages installed into it—ideally (but not necessarily) only the dependencies that are needed by the application.Depending on the language used, the application itself might be a compiled binary, or it might be a series of interpreted scripts.
There might well be some ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access