Question 180
During a scheduled security audit at Aspen Digital, the identity operations team identifies this issue: A scheduled Azure function stores a long-lived client secret in source code to access another Azure service. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
The function obtains a token without a committed secret and an unauthorized resource operation fails. This is the relevant proof because it tests whether the selected corrective action (Use a managed identity for the supported Azure workload and grant it the smallest appropriate role) addressed the initiating problem (A scheduled Azure function stores a long-lived client secret in source code to access another Azure service) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.
Incorrect Answers
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 Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.
Noninteractive API calls run under the application identity and stop working after its credential or permission is revoked. This is useful evidence for a different situation (A system integration uses a human administrator identity for app-only API calls and fails whenever the administrator changes their password) and action (Give the application an app registration and workload identity with the required API permissions). For the reported issue at Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.
After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Aspen Digital, it does not establish the required outcome: The function obtains a token without a committed secret and an unauthorized resource operation fails.