Question 170
During a cloud security review, the operations team observes: A service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag. Which underlying control gap is responsible for the issue?
Explanation
Correct Answer
The described technical condition is: A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The appropriate corrective action is: Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations. Confirm with: Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.
Incorrect Answers
PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.
“Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls” responds to this separate finding: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. This question instead needs “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations”, so the alternative does not meet the stated condition.
Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is a service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag; choosing this alternative would address the wrong failure mode.