A healthcare organization is designing a cloud-based clinical trial platform. Patient health records are stored in an Azure Blob Storage container named `trials`. A third-party auditing firm requires read-only access to this container for a period of days. The security architecture must ensure that the access can be immediately revoked at any time without rotating the storage account access keys or impacting other applications. Additionally, all access requests must originate from the auditing firm's public IP range of .
Which access control strategy should you recommend to meet these requirements?
- Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token that references the policy and specifies the allowed IP address range.Answer
- BGenerate an ad-hoc service Shared Access Signature (SAS) token for the container with an expiry of days and the IP address constraint.
- CAssign the Storage Blob Data Reader role directly to each auditor's Microsoft Entra ID user account and configure a storage firewall rule targeting the IP address range.
- DCreate a Microsoft Entra ID group for the auditors, assign the Storage Blob Data Reader role to the group, and configure a Privileged Identity Management (PIM) active role assignment for the group.
Answer
Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token that references the policy and specifies the allowed IP address range.
The correct option recommends creating a stored access policy on the container and generating a service SAS token referencing it. A stored access policy provides a way to manage SAS tokens on the server side, allowing revocation by simply deleting or modifying the policy without rotating the storage account keys. It also supports specifying IP address constraints directly in the SAS token parameters.
Step-by-Step Solution
Key Concept
Stored Access Policies and Shared Access Signatures