A security architect is reviewing an Azure AI Foundry deployment. The AI hub uses a user-assigned managed identity. The architect discovers the managed identity has 'Owner' rights on the resource group. What is the security risk and recommended remediation?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — b is correct because an 'Owner' role includes the ability to manage role assignments (it includes Microsoft.Authorization/roleAssignments/write). If the managed identity is compromised through the AI workload, an attacker could use it to grant additional permissions to other identities, enabling privilege escalation attacks.
Full explanation below image
Full Explanation
B is correct because an 'Owner' role includes the ability to manage role assignments (it includes Microsoft.Authorization/roleAssignments/write). If the managed identity is compromised through the AI workload, an attacker could use it to grant additional permissions to other identities, enabling privilege escalation attacks. The remediation is to follow least-privilege and assign only the specific roles the AI hub needs for its operations. A is incorrect because 'Contributor' still provides broad resource modification rights and the more important concern with 'Owner' is the role assignment capability. C is incorrect because while resource locks prevent deletion, they do not address the privilege escalation risk. D is incorrect because managed identities are not exposed to the internet in the traditional sense; the risk is about permission scope.