Question 340
At the Greystone transportation operator, a GitHub Actions workflow builds documentation but its default token can write to unrelated repository content. What should the team review routinely to prevent this problem?
Explanation
Correct Answer
After the immediate fix, the priority is to review token permissions and third-party actions whenever workflows change. This reinforces the control against the original weakness: excess token authority increases damage if workflow code or an action is compromised. This directly addresses the reported issue at the Greystone transportation operator.
Incorrect Answers
This routine applies to multi-repository checkout, but it does not maintain the specific correction needed for the problem at the Greystone transportation operator.
That practice helps control a different risk: consumers may assume compatibility from an unchanged major version and fail after upgrading. The recurring control here should be to review token permissions and third-party actions whenever workflows change. For the Greystone transportation operator, the priority is to set job-level permissions on GITHUB_TOKEN to only the API actions required.
The alternative suggests that the team run side-by-side tests and formally retire classic definitions after verification; it would not directly prevent the observed issue from returning. For the Greystone transportation operator, the priority is to set job-level permissions on GITHUB_TOKEN to only the API actions required.