Question 100
During a migration readiness assessment at Blue Haven Media, the SOC analyst identifies this issue: A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected. This is the relevant proof because it tests whether the selected corrective action (Integrate with a trusted identity provider and validate issued authentication tokens before accepting a sign-in) addressed the initiating problem (A development team generates homegrown proof-of-login strings instead of trusting the organization's designated identity provider) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.
Incorrect Answers
An unauthorized credential or context is blocked even when the requesting device can reach the application endpoint. This is useful evidence for a different situation (A hybrid company protects only its physical network edge although employees sign in to cloud services from unmanaged networks) and action (Treat identity as a primary security perimeter and enforce appropriate authentication and authorization at cloud application access). For the reported issue at Blue Haven Media, it does not establish the required outcome: A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.
A partner user signs in with the home identity while access to the application remains governed by local authorization rules. This is useful evidence for a different situation (Two independent organizations share a web application but require users to create duplicate local passwords because no trust relationship exists) and action (Evaluate identity federation to accept authentication assertions from an approved external identity provider). For the reported issue at Blue Haven Media, it does not establish the required outcome: A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.
A user account removal in the managed identity system removes its ability to sign in to integrated departmental applications. This is useful evidence for a different situation (An application stores a separate password list for every department instead of relying on the organization's managed directory) and action (Use a suitable directory and identity provider to centralize identity records and lifecycle control). For the reported issue at Blue Haven Media, it does not establish the required outcome: A properly signed and audience-matched identity token is accepted while an altered or wrong-audience token is rejected.