You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub security good practices documentation says you should use the commit hash instead of the version
`Pin actions to a full-length commit SHA
Pinning an action to a full-length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.`
Approach
Review all actions and replace all versions with commit hashes as this is best practice and covers Cloud Platform for the future
Background
GitHub security good practices documentation says you should use the commit hash instead of the version
`Pin actions to a full-length commit SHA
Pinning an action to a full-length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.`
Approach
Review all actions and replace all versions with commit hashes as this is best practice and covers Cloud Platform for the future
Steps to get the hash: Getting Release Hash for GitHub Actions
Definition of done
Reference
Security Guide
The text was updated successfully, but these errors were encountered: