Question 160
Following the issue — An application owner grants a tenant-wide Graph permission to troubleshoot a 403 error without confirming which API action is actually missing. — the team takes this action: Inspect failed API scope or role requirements and grant only verified additional permissions. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Require permission-specific evidence before approving changes to application grants. This mitigates the control weakness because: A forbidden API response can arise from role, scope, or resource authorization mismatches. Keep the intervention, Inspect failed API scope or role requirements and grant only verified additional permissions., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Monitor legacy authentication trends and retire unsupported client dependencies” addresses a different recurring failure: Authentication method and client-app conditions determine whether modern enforcement is evaluated. For the condition in this question, maintain “Require permission-specific evidence before approving changes to application grants” because a forbidden API response can arise from role, scope, or resource authorization mismatches.
That review protects the control associated with: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. It does not directly prevent the stated recurrence, which concerns: A forbidden API response can arise from role, scope, or resource authorization mismatches. The appropriate guardrail is “Require permission-specific evidence before approving changes to application grants”.
“Audit sensitive management actions such as listKeys in role design reviews” addresses a different recurring failure: Resource roles can include operations that expose credentials outside the immediate work requirement. For the condition in this question, maintain “Require permission-specific evidence before approving changes to application grants” because a forbidden API response can arise from role, scope, or resource authorization mismatches.