Question 190
During a scheduled security audit at Brightstone Legal, the SOC analyst identifies this issue: A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is the relevant proof because it tests whether the selected corrective action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource) addressed the initiating problem (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) in Brightstone Legal's matter files and sensitive case records environment, not merely whether a task was marked complete.
Incorrect Answers
The function obtains a token without a committed secret and an unauthorized resource operation fails. This is useful evidence for a different situation (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) and action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.
An identity inventory lists application service principals separately from workforce user accounts and group memberships. This is useful evidence for a different situation (An administrator expects deleting an app registration to be equivalent to removing a user's account from the directory) and action (Distinguish application registrations, service principals and human user objects for accurate lifecycle management). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.
A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Brightstone Legal, it does not establish the required outcome: After resource deletion the old identity can no longer be used and its former permissions are reviewed.