Question 80
Following the issue — A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. — the team takes this action: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Automate time-bound access review and revoke emergency permissions at incident closure. This mitigates the control weakness because: Least privilege includes duration as well as actions and scope. Keep the intervention, Provide a temporary scoped assignment with a defined end date or eligible elevation workflow., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Workload identities reduce secret distribution only when applications actually use the identity flow. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.
This safeguard is for the dependency described by: OAuth delegated permission granularity is controlled by the resource API's published scopes. The continuing risk here is determined by: Least privilege includes duration as well as actions and scope. The targeted safeguard is “Automate time-bound access review and revoke emergency permissions at incident closure”.
That review protects the control associated with: OAuth token issuance differs between interactive delegated sign-in and confidential client credentials. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.