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

Support ignoring different policies for Trivy #1

Open
wants to merge 1 commit into
base: 1.16.0
Choose a base branch
from

Conversation

toanhminh0412
Copy link
Collaborator

Set trivy.ignorePolicy to none, basic or advanced to have Trivy ignore certain policies when reporting vulnerabilities. basic and advanced levels are from Trivy's example policies

@toanhminh0412 toanhminh0412 requested a review from dleske December 13, 2024 00:06
@toanhminh0412 toanhminh0412 self-assigned this Dec 13, 2024
@dleske
Copy link

dleske commented Dec 16, 2024

The README should be updated to document the new options, but is there a way to customize the actual policies? They are specific and I believe will have to be updated by knowledgeable administrators/infosec. How could we customize the policy/policies?

@toanhminh0412
Copy link
Collaborator Author

toanhminh0412 commented Jan 9, 2025

Yes, this PR will need a further implementation to customize the policies. A design I have in mind is to add a custom option to trivy.ignorePolicy and a trivy.customIgnorePolicies field or something similar to values.yaml that will create a config map that contains the custom policies.

Before doing this, I'm waiting on a review on my PR to the Harbor Helm official repo

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

Successfully merging this pull request may close these issues.

2 participants