Question 180
At the Willowford analytics division, a public repository lets untrusted fork pull requests read production deployment secrets during validation. What continuing safeguard is most appropriate?
Explanation
Correct Answer
After the immediate fix, the priority is to review trigger and token permissions after workflow changes. This reinforces the control against the original weakness: untrusted pull request code can abuse secrets or privileged runner contexts if not separated. This directly addresses the reported issue at the Willowford analytics division.
Incorrect Answers
This routine applies to signed commit policy, but it does not maintain the specific correction needed for the problem at the Willowford analytics division.
That practice helps control a different risk: long-running divergent branches increase merge conflict and inconsistent code behavior. The recurring control here should be to review trigger and token permissions after workflow changes. For the Willowford analytics division, the priority is to isolate fork-triggered jobs and restrict privileged secrets until reviewed trusted workflows run.
The alternative suggests that the team include back-merge confirmation in emergency release closure; it would not directly prevent the observed issue from returning. For the Willowford analytics division, the priority is to isolate fork-triggered jobs and restrict privileged secrets until reviewed trusted workflows run.