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

feat(misconf): Ensure policy bundles are compatible #4938

Closed
simar7 opened this issue Aug 4, 2023 · 0 comments · Fixed by aquasecurity/defsec#1421
Closed

feat(misconf): Ensure policy bundles are compatible #4938

simar7 opened this issue Aug 4, 2023 · 0 comments · Fixed by aquasecurity/defsec#1421
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Milestone

Comments

@simar7
Copy link
Member

simar7 commented Aug 4, 2023

As part of #4197 we came to the conclusion that policy bundles must be forward and backwards compatible.

For this to guaranteed, we need to ensure each generated bundle is compatible with the existing version of Trivy. We can ensure the following such as:

  1. Build new defsec bundle with each defsec commit
  2. Load this bundle in via a unit test in Trivy using the --policy-bundle-repository flag.
  3. Ensure proper operation
@simar7 simar7 added scan/misconfiguration Issues relating to misconfiguration scanning target/cloud Issues relating to cloud account scanning labels Aug 4, 2023
@simar7 simar7 added this to the v0.45.0 milestone Aug 10, 2023
@simar7 simar7 self-assigned this Aug 10, 2023
@itaysk itaysk added kind/feature Categorizes issue or PR as related to a new feature. and removed target/cloud Issues relating to cloud account scanning labels Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants