Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Condition-Based Vulnerability Scanner #21249

Open
Vad1mo opened this issue Nov 26, 2024 · 0 comments
Open

Condition-Based Vulnerability Scanner #21249

Vad1mo opened this issue Nov 26, 2024 · 0 comments

Comments

@Vad1mo
Copy link
Member

Vad1mo commented Nov 26, 2024

Many harbor instances have Terabytes of data and, 10000 thousand artifacts.
This results in vulnerability scans that run for days or weeks.

Describe the solution you'd like
The user should be able to do policy-based regular vulnerability scans, where the user can decide based on criteria what images should be rescanned.

Here are some examples:

include/exclude

  • Artifacts pulled within the last [n] days?
  • Artifacts pushed [n] days ago
  • All matching [rx] regex
  • All with label [l]

Describe the main design/architecture of your solution
So instead of having a huge job that is running across the whole registry, there should be a policy in place the allow to run multiple smaller jobs for different types of images.

Additional context

The idea is to have a similar use experience as with retention, immutability and replication polices.

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

No branches or pull requests

1 participant