Skip to content

Conversation

@naveensrinivasan
Copy link

 Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)

Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
@varunsh-coder
Copy link
Contributor

Hi @naveensrinivasan, I just noticed this PR. I had created similar one few days back :). #1829

Are you creating these in specific repos? I am planning to create in top 100 most critical projects. If you are creating these regularly, would love to divide and conquer. Let me know.

@hargasinski
Copy link
Collaborator

I'm closing this in favour of #1829. Thanks for the contribution though!

@hargasinski hargasinski closed this May 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants