Add article: 12 Steps to Secure GitHub Actions After the Trivy Attack#4
Open
gebalamariusz wants to merge 1 commit into
Open
Add article: 12 Steps to Secure GitHub Actions After the Trivy Attack#4gebalamariusz wants to merge 1 commit into
gebalamariusz wants to merge 1 commit into
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 link to the Unofficial resources section:
A practical hardening checklist covering pin-by-SHA, OIDC, least-privilege tokens, and other defenses prompted by the 2025 Trivy supply chain incident.
The article provides an actionable 12-step checklist for hardening GitHub Actions workflows, written in response to the Trivy/aquasecurity supply chain compromise. It covers topics already represented in this list (pinning, scanning, OIDC) but ties them together into a single post-incident hardening guide.