Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Improved Vulnerability Scanner #1761

Open
1 of 5 tasks
Vad1mo opened this issue Apr 5, 2018 · 5 comments
Open
1 of 5 tasks

Improved Vulnerability Scanner #1761

Vad1mo opened this issue Apr 5, 2018 · 5 comments

Comments

@Vad1mo
Copy link
Contributor

Vad1mo commented Apr 5, 2018

Abstract

The first phase of the vulnerability scanner allowed the general scanning of repositories. In order to make better and more precise conclusions out the results it is desired to improve the vulnerability scanner.

This issue here is intended to track all the effort related to deliver an improved version of the vulnerability scanner.

The issue #1658 targets some of the features

Related Tasks

  • Store vulnerabilities in a more clever way #1669 Store vulnerabilities in a more clever way.

  • Periodic scanning of images:
    Scanning should not only happen once after an image is pushed. Images should be scanned on a regular basis. There should be an option to control the scheduler. (Examples: How Often, Scan only Latest, Newest, SemVer newest, Tag RegEx and so forth.)

  • Better Vulnerability overview and reporting.
    Overview of images the vulnerable. (Examples: Sort images by vulnerability. All vulnerabilities of latest images)

  • Add vulnerability results to audit trail.
    See if Pushed images are vulnerable

  • Vulnerability Notifications.
    Get Notification if Vulnerable images becomes vulnerable. (Example: All, Only Latest)

You are invited to make suggestions

@mssola
Copy link
Collaborator

mssola commented Apr 5, 2018

Thanks a lot for this 👏

@hamid-elaosta
Copy link

I'd like to add a suggestion. It would be useful for a feature to run a full-rescan of a registry. I have many, many images in Portus/Registry prior to configuring Clair and I now cannot rescan those images it seems.

@rikkuness
Copy link

Will this include updating to use the Clair V3 API too?

@mssola
Copy link
Collaborator

mssola commented Oct 9, 2018

Will this include updating to use the Clair V3 API too?

I see that this version of the API is only included in the master branch (so it has not been released yet). Meaning that it may change, I guess. So, I'd say that we should take a look at it, but I wouldn't say it's top priority.

That being said, I remember that there were some changes on the v1 of the API for some versions of Clair (or at least Portus failed for some versions of Clair so we pinned a specific version). So, I'd say that it's important to check more versions of Clair (master and v3 included).

Thanks for the heads up 👍

@sharkymcdongles
Copy link

Is there any way to have it run the scan against the entire registry once you enable clair?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants