Question 200
Following the issue — A web service calls an API with an ID token and expects it to carry the API's delegated access scopes. — the team takes this action: Request an access token for the appropriate resource and validate its audience and permissions. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Inspect token purpose and audience in application security tests. This mitigates the control weakness because: ID tokens identify an authentication event whereas access tokens authorize resource API access. Keep the intervention, Request an access token for the appropriate resource and validate its audience and permissions., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The continuing risk here is determined by: ID tokens identify an authentication event whereas access tokens authorize resource API access. The targeted safeguard is “Inspect token purpose and audience in application security tests”.
“Audit Conditional Access authentication-strength settings after new methods are enabled” addresses a different recurring failure: Different multifactor methods can satisfy different phishing-resistance requirements. For the condition in this question, maintain “Inspect token purpose and audience in application security tests” because iD tokens identify an authentication event whereas access tokens authorize resource API access.
That review protects the control associated with: Location-based Conditional Access relies on network signals and explicit address-range membership. It does not directly prevent the stated recurrence, which concerns: ID tokens identify an authentication event whereas access tokens authorize resource API access. The appropriate guardrail is “Inspect token purpose and audience in application security tests”.