Closed sashashura closed 10 months ago
@chadaustin could you please review?
An example of a recent workflow run with unrestricted permissions:
@genevievehelsel has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
@genevievehelsel merged this pull request in facebook/watchman@5be84abb85f29076f7f21e83393e2ce6c6691d23.
This PR adds explicit permissions section to workflows. This is a security best practice because by default workflows run with extended set of permissions (except from
on: pull_request
from external forks). By specifying any permission explicitly all others are set to none. By using the principle of least privilege the damage a compromised workflow can do (because of an injection or compromised third party tool or action) is restricted. It is recommended to have most strict permissions on the top level and grant write permissions on job level case by case.