fix: update README.md file to list explicit secure practices to apply#356
Merged
fix: update README.md file to list explicit secure practices to apply#356
Conversation
Update README.md to explicitly list secure practices for updating GItHub Actions taken from GitHub security documentation and examples from a few security blogs. When GeoNet migrated to GitHub Actions it was noted at the time to use the full-length commit SHA value to securely use external 3rd-party code to avoid the sort of supply chain attaks seen with Trivy scanner and malicious overwriting of all version tags for Trivy scanner GitHub actions.
ardrigh
force-pushed
the
clarify_security_policy
branch
from
61f2542 to
df0e298
Compare
ThomasFuller
approved these changes
Mar 30, 2026
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
2 participants
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.
Update README.md to explictly list secure practices for updating GItHub Actions taken from GitHub security documentation and examples from a few security blogs.
When GeoNet migrated to GitHub Actions it was noted at the time to use the full-length commit SHA value to securely use external 3rd-party code to avoid the sort of supply chain attaks seen with Trivy scanner and malicious overwriting of all version tags for Trivy scanner GitHub actions.
Disbles the trivy-action which is currently blocked due to the supply chain attack.