Question 200
Which test or documented result best shows that the underlying issue was properly addressed? An enterprise API passes external supplier identities directly to backend services without validating issuer and audience claims.
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: An enterprise API passes external supplier identities directly to backend services without validating issuer and audience claims. It demonstrates that the proposed response, implement gateway token validation with audience, issuer, expiry, and least-privilege backend claims checks., produces the measurable result forged or wrong-audience tokens fail and approved requests retain auditable identity context. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
“Policy tests prevent office-to-controller access outside approved management gateways” would verify “Design compensating isolation, passive monitoring, and controlled management paths around the legacy asset” for the situation “An acquired facility's unsupported embedded controller cannot run modern endpoint agents but can communicate freely with office networks”. Here the required evidence is “Forged or wrong-audience tokens fail and approved requests retain auditable identity context” after “Implement gateway token validation with audience, issuer, expiry, and least-privilege backend claims checks”; the alternative observation does not test that control.
Observation “Nonapproved personnel cannot view sensitive prompt content while security-relevant metadata remains observable.” would be useful for “An AI data service exposes training logs containing raw user prompts to every engineer with cloud console access”, but it does not prove that the response to “An enterprise API passes external supplier identities directly to backend services without validating issuer and audience claims” achieved the relevant outcome, forged or wrong-audience tokens fail and approved requests retain auditable identity context.
In the problem “An enterprise API passes external supplier identities directly to backend services without validating issuer and audience claims”, evidence “A test compute job outside the approved perimeter cannot read restricted training data.” is not decisive because it tests “A data science environment handles restricted data in a shared cluster but policy is enforced only at the internet edge”; the requested validation is forged or wrong-audience tokens fail and approved requests retain auditable identity context.