Phase 4: add Trivy CI security gate#2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a CI security gate so the pipeline scans every push and PR automatically.
What this does
.github/workflows/security.ymlruns on every push and pull request.Dockerfile.v4-distroless), then scans it withaquasecurity/trivy-action.exit-code: 1) on any CRITICAL or HIGH vulnerability.ignore-unfixed: trueso the gate only blocks on CVEs that actually have a fix available — unfixable base-OS DoS CVEs don't create permanent red builds.Why
Turns the project from a one-time hardening exercise into an enforced policy: no image with a fixable critical/high vuln can merge to main without the check going red.