External Service: Container Vulnerability Scanning #203
Labels
enhancement
New feature or request
P1
P1 label is used for this that we see of highest priority. Critical bugs, security issues, etc
Milestone
A container vulnerability scanning service would really compliment OpenRegistry. It really helps to have such service and an option to toggle it on/off. This service can use an existing tool, any once from the following would do:
Grype
Pros - Grype is amazing. It's actively maintained by a security focused company. Default output looks clean as well, plus on the comparison, Grype listed out mode vulnerabilities.
Cons - Doesn't have an HTTP Server/Client model as of now and they don't wish to support it, just to keep the project simple and tight knit
The upside is, extending this would be dead simple and adding HTTP support for it would only take a medium effort (probably a 5-7 days of fulltime work)
Trivy by AquaSecurity
Pros - Trivy is basically the best tool out there for our use case. It's maintained by arguably the best security company in the container and cloud native space, offers more than container vulnerability scanning like
FS, Container Images, AWS, k8s, etc
plus has a plugin system to extend the base functionality.Another very big feature is that they already have an HTTP Server/Client model.
Cons - Didn't detect some vulnerabilities? Grype detected few, as seen above but in case of Trivy, it showed the following for the same container image:
The text was updated successfully, but these errors were encountered: