Question 560
At the Quayford financial cooperative, a GitHub workflow uses a permanent subscription owner secret to deploy only one resource group. How should the team reduce the chance of the issue recurring?
Explanation
Correct Answer
For the Quayford financial cooperative, the control should be maintained by having the team review federated credentials, audience and role scope when workflow identity changes. It reduces the chance that persistently stored privileged credentials grant more authority than required and increase compromise impact.
Incorrect Answers
This routine applies to iac destroy safeguards, but it does not maintain the specific correction needed for the problem at the Quayford financial cooperative.
The alternative suggests that the team update scanning policies and retire expired exception approvals; it would not directly prevent the observed issue from returning. For the Quayford financial cooperative, the priority is to use federated workload identity and narrowly scoped role assignments for infrastructure deployment.
This maintenance work is reasonable for pipeline test result publishing. The continuing exposure described here is that persistently stored privileged credentials grant more authority than required and increase compromise impact. For the Quayford financial cooperative, the priority is to use federated workload identity and narrowly scoped role assignments for infrastructure deployment.