Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/42 of 115

3.5Ensure that 'Public access level' is set to Private for blob containers

Control family: Storage Accounts

Control description

Disable anonymous access to blob containers and disallow blob public access on storage account.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A blob container with anonymous access lets anyone who knows or guesses its address read its data, which is how many cloud data leaks start. Anonymous access is turned off for the whole account, so no container can be made public by mistake.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree that no storage account allows anonymous access, and record any account that must serve public content, with its approver.

Evidence

  • The storage access standard and the list of approved public accounts

On Azure the tasks disallow anonymous access on each storage account, set existing containers to private, and keep it checked with the CIS standard.

Task 1Turn off anonymous access for the account

  1. Sign in to the Azure portal at portal.azure.com and open Storage accounts, then the account.
  2. Select Settings > Configuration.
  3. Set Allow Blob anonymous access to Disabled.
  4. Select Save.
  5. Check it: opening a blob's URL in a private browser window without a SAS is refused.

Task 2Set existing containers to private

  1. Select Data storage > Containers.
  2. Select each container whose access level isn't Private, then Change access level.
  3. Choose Private (no anonymous access) and select OK.
  4. Check it: every container shows Private.

Task 3Keep it checked with the CIS v1.4.0 standard in Defender for Cloud

  1. Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
  2. Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
  3. Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 3.5.
  4. Open the assessment for Storage account public access should be disallowed and fix the resources it lists as non-compliant.
  5. Check it: every resource under recommendation 3.5 shows as passing after the next evaluation.

Evidence

  • Configuration of each account, showing anonymous blob access disabled
  • The CIS v1.4.0 standard, with recommendation 3.5 passing

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.