CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/43 of 115
3.6Ensure Default Network Access Rule for Storage Accounts is Set to Deny
Control family: Storage Accounts
Control description
Restricting default network access helps to provide a new layer of security, since storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
By default a storage account accepts connections from any network, relying only on keys and tokens. Changing the default network rule to deny means only the virtual networks and address ranges you list can reach it, so a leaked credential is useless from anywhere else.
Before you start
The same on every cloud, before the steps in the tabs.
- List which networks and services need each storage account, so nothing breaks when the default changes to deny.
Evidence
- The list of networks and services allowed to reach each storage account
On Azure the tasks restrict public network access in each storage account's networking settings, then keep it checked with the CIS standard.
Task 1Allow only selected networks
- Sign in to the Azure portal at portal.azure.com and open Storage accounts, then the account.
- Select Security + networking > Networking.
- Under Public network access, choose Enabled from selected virtual networks and IP addresses (or Disabled if only private endpoints are used).
- Add the virtual networks and subnets, and the public address ranges, that must reach the account.
- Select Save.
- Check it: a request from an address not on the list is refused.
Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 3.6.
- Open the assessment for Storage accounts should restrict network access and Storage accounts should restrict network access using virtual network rules and fix the resources it lists as non-compliant.
- Check it: every resource under recommendation 3.6 shows as passing after the next evaluation.
Evidence
- Networking of each account, showing access limited to selected networks
- The CIS v1.4.0 standard, with recommendation 3.6 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
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.