Container supply chain security: Securing IT supply chains
Container images need verified provenance, up-to-date components and a vulnerability process. The CRA and NIS2 impose different obligations.
Container images package application code with libraries and base components from different sources. A vulnerability or manipulation in one of these components can affect multiple applications at once. IT teams therefore need visibility into provenance and versions, as well as a process for checking and replacing components. Since September 2026, the Cyber Resilience Act has also imposed initial reporting obligations on manufacturers.
Key takeaways
- Container images must be checked throughout their lifecycle. This includes base layers, application components and renewed checks of images already in use.
- An SBOM provides visibility into software components. Comparing it with vulnerability information helps with assessment, but does not replace a security check.
- The CRA and NIS2 apply to different responsible parties. The CRA governs, among other things, manufacturers’ obligations for digital products. NIS2 requires entities within its scope to manage risks and report significant incidents.
Container images as part of the software supply chain
Alongside the application, a container image often contains a base image, runtime environments and other packages. Each of these layers must be considered during security checks. An image with no known vulnerabilities at build time may later be affected when new findings are published.
The NIST container security guide therefore recommends checks from build through registry to runtime. When components are updated, the image must be rebuilt and redeployed so that the change reaches the running containers.
Using SBOMs for vulnerability assessment
A software bill of materials, or SBOM, documents the components of a software product and their relationships. It gives IT teams a basis for identifying affected products and versions after a new vulnerability is reported. Whether a vulnerability found can be exploited in a specific deployment must be assessed separately.
For in-house images, the SBOM should be associated with the relevant build and updated when changes are made. For purchased software, teams can agree with the supplier on how they will receive information about components and security updates. An incomplete bill of materials leaves gaps in the assessment.
Securing images from build to operation
Regularly updated base images from trusted sources are a suitable starting point. The build pipeline should check both base layers and application components for known vulnerabilities and insecure configurations. Release rules can prevent images with risks above a defined threshold from being passed on.
Checks do not end after deployment: new vulnerability reports must be compared with the image versions in use. Those responsible then prioritise according to impact and deployment context, rebuild affected images and deploy them. Keeping container privileges as low as possible is also part of securing them.
CRA and NIS2 distinguish between manufacturers and operators
The Cyber Resilience Act covers products with digital elements within its scope. To handle vulnerabilities, manufacturers must, among other things, identify components and produce a machine-readable SBOM covering at least the top-level immediate dependencies. The main obligations generally apply from 11 December 2027. Exceptions or transitional rules apply to certain products and circumstances.
Since 11 September 2026, manufacturers have been required to report actively exploited vulnerabilities in their products and severe security incidents. An early warning is generally due within 24 hours of becoming aware of them, with a further notification due within 72 hours.
The NIS2 Directive requires entities within its scope to take appropriate measures for the security of their supply chain, among other things. For significant security incidents, it generally requires an early warning within 24 hours of becoming aware of them. Whether a company is within scope depends on its activities and other criteria, as well as national implementation.
Frequently Asked Questions
What does a software bill of materials contain?
An SBOM documents software components and their relationships. It can be compared with vulnerability information, but is not in itself a complete vulnerability assessment.
Does NIS2 affect every medium-sized logistics company?
No. The specific activity, the statutory entity type and other criteria are decisive. In Germany, Section 28 of the BSIG specifies at least 50 employees or both an annual turnover and an annual balance sheet total of more than 10 million euros for certain important entities. Special rules must also be considered.
How often should container images be checked?
Images should be checked at build time and again while in use because new vulnerabilities may become known. A fixed general monthly interval is no substitute for a risk-based response to a specific report.
Editor's Picks
cloudmagazinNIS2 and the SaaS supply chain: A compliance gapcloudmagazinHashiCorp gives machine images proof of provenancecloudmagazinKubernetes support ends, Amazon charges six times as muchMore from the MBF Media Network
SecurityTodayGlassWorm: 400+ developer tools compromisedMyBusinessFutureCyber Resilience Act: What manufacturers must doImage source: AI-generated (November 2026)
Translated from the German original using artificial intelligence. The German version is authoritative.

