I'm a software engineer tasked with upgrading the open-source containers my team relies on. We run security scans through BlackDuck, but each scan reports over 50 new CVEs, which is quite tedious to triage and often requires extensive time spent on resolving issues like upgrading dependencies and libraries. I'm looking for strategies or tools that can make this process more efficient. What approaches do you recommend?
6 Answers
Currently, this is a challenging issue in our field. A lot of scanners just list every CVE without context, leading to a flood of alerts that might not be relevant. Dependabot can assist with some of the management, but it's still a lot of manual effort. I think it should be a team-wide responsibility rather than just one person's job.
Switching to Chainguard images has brought our vulnerability count down significantly. They provide images for most tools we use, though it’s a bit on the pricey side, it’s absolutely worth it for the security and peace of mind.
Adopting smaller base images helps reduce vulnerabilities significantly. Utilizing tools like RenovateBot or Dependabot can also streamline upgrades. This makes the update process feel less like a constant chore and more manageable overall.
Absolutely! Smaller images mean fewer potential issues to deal with.
We've paired Dependabot with Trivy and stayed committed to using minimal images. Although we recently faced issues related to "musl" in Alpine, the continuous updates make managing vulnerabilities feel less burdensome. It's a constant cycle, but tools are definitely easing the workload.
If Chainguard is out of reach budget-wise, consider building from their base image, wolfi, using apko. There are also flexible building options with tools like melange. But just be aware that if you're only using standard open-source images, it may require significant effort to get everything properly built and secure.
Using tools like Renovate or Dependabot can really help automate some of the dependency updates. Regularly rebuilding, retesting, and redeploying will keep your containers secure. Just remember to incorporate a cooldown period between updates to mitigate any risks from sudden changes.
Good point! It's all about balancing updates and keeping a secure environment.

I feel you. It's frustrating when scans flag issues that aren't even in the container.