Anchore Blog
anchore.com · Company blog · on HN since 2016
The blog of Anchore, a company that makes container image and software supply chain security tools, covering CVE scanning, Grype and Docker security.
What HN saysHN links it for explanations of vulnerability scanning with Grype and for its reporting on the NIST National Vulnerability Database falling behind on CVEs.
19HN people shared it
3linked it in comments
41stories submitted
75story points
7 months agolast shared
2016people per year2026
Most-shared posts
- 1Extending Anchore Container Image Analysis with Lynis Scanning Tool2 people · 5 points · first shared 2016 · discussion on HN
- 2NIST NVD hasn't enriched CVEs for over a month2 people · 2 points · first shared 2024 · discussion on HN
- 3Build Your Own Grype (vuln) Database2 people · 1 points · first shared 2023 · discussion on HN
- 4Using Anchore to scan for CVEs and vulnerabilities in docker images1 people · 7 points · first shared 2019 · discussion on HN
- 5An open policy hub for Docker security and compliance1 people · 6 points · first shared 2019 · discussion on HN
- 6Integrating Anchore OSS container image validation engine with Jenkins1 people · 4 points · first shared 2016 · discussion on HN
- 7The Anchore open source project1 people · 3 points · first shared 2017 · discussion on HN
- 8Anchore 1.1 is here with image subscription and support for Ruby Gems/Alpine Linux1 people · 3 points · first shared 2017 · discussion on HN
- 9Docker Security Best Practices: Part 3 – Securing Container Images1 people · 3 points · first shared 2018 · discussion on HN
- 10Keeping Secrets – Our approach to secrets management and docker image security1 people · 3 points · first shared 2017 · discussion on HN
- 11Certifying container images isn't 1 size fits all. Do it on your own terms1 people · 3 points · first shared 2017 · discussion on HN
- 12Is Docker More Secure Than VM's?1 people · 2 points · first shared 2016 · discussion on HN
- 13Using Anchore Open Source CLI Tool for Container Image Management and Analysis1 people · 2 points · first shared 2016 · discussion on HN
- 14We're giving away a full conference pass to DockerCon 2017 in Austin1 people · 2 points · first shared 2017 · discussion on HN
- 15Docker Security Best Practices: Part 4 – Runtime Security1 people · 2 points · first shared 2018 · discussion on HN
What HN people wrote when they linked it
eadmund · 2025-04-16
> I wonder what level of compartmentalisation inside DHS means they didn't see this as having sufficient downsides?
The National Vulnerability Database has been unable to keep up with the flow of CVEs for over a year now:
- https://anchore.com/blog/national-vulnerability-database-opaque-change…
- https://www.cyberreport.io/news/cve-backlog-update-the-nvd-struggles-a…
- https://www.ibm.com/think/insights/cve-backlog-update-nvd-struggles-at…
- and many, many, many others
It has been a complete disaster for months. At this point, perhaps the thinking is to radically change approaches?
paolomainardi · 2023-07-10
This is a very interesting point, the vulnerability scan tool used on the article is this one: https://github.com/anchore/grype-db/blob/main/DEVELOPING.md and here you can see how it works: https://anchore.com/blog/build-your-own-grype-database
As you can see there is a database specifically designed for Debian to take in charge the naming convention.
vmarquet · 2017-09-19
In addition to the "minimalist" aspect, this image seems to offer better practices on a security level than official Debian images. From their README: "The images are built daily and have the security release enabled, so will contain any security updates released more than 24 hours ago."
A recent analysis showed that the debian:latest image is "updated roughly every month" https://anchore.com/blog/look-often-docker-images-updated/