BreachcraftStandards
Baseline
Azure Storage accounts
Applies to: all storage accounts in scope. Derived from: CIS Microsoft Azure · Last reviewed: 2026-11-21.
ST-01 Public blob access disabled Critical
- Statement
allowBlobPublicAccess is false on every account, or a named exception exists for content that must be public.
- Why
- Anonymous read on a container removes every identity control from the path.
- Check
az storage account show -n <account> --query allowBlobPublicAccess
- Evidence
- Command output per account; where true, the container and its intended audience.
- Remediation
- Set the property false; publish public content through a front door or CDN instead.
ST-02 Shared key access disabled High
- Statement
allowSharedKeyAccess is false, except where a dependency requires keys, with a named owner.
- Why
- A key ignores roles, Conditional Access and MFA (wiki: storage keys vs role).
- Check
az storage account show -n <account> --query allowSharedKeyAccess
- Evidence
- Output per account; for exceptions, the dependency and owner.
- Remediation
- Move callers to identity, then disable. Rotate both keys after.
ST-03 Minimum TLS 1.2 High
- Statement
minimumTlsVersion is TLS1_2 or higher.
- Why
- TLS 1.0/1.1 are retired by browsers and by several auditors outright.
- Check
az storage account show -n <account> --query minimumTlsVersion
- Evidence
- Output per account.
- Remediation
- Set
TLS1_2; test older clients first if the account is shared.
ST-04 Network access restricted High
- Statement
publicNetworkAccess is Disabled, or the firewall default action is Deny with named allowances.
- Why
- A storage endpoint reachable from the internet is a password away from data even when the password is a key.
- Check
az storage account show -n <account> --query "{public:publicNetworkAccess,action:networkRuleSet.defaultAction}"
- Evidence
- Output per account; the allowed networks and their purpose.
- Remediation
- Private endpoints, or default-deny with the minimum service exceptions.
ST-05 Key rotation is automatic or dated (ours) Medium
- Statement
- The account's key policy rotates, or the last rotation date is recorded with a due date inside 180 days.
- Why
- A key older than the role that exposed it is the one that leaks.
- Check
az storage account keys list -n <account> --query "[].{key:keyName,created:creationTime}"
- Evidence
- Key names and creation times; the policy or the due date.
- Remediation
- Enable
keyPolicy rotation, or schedule it and record the owner.
ST-06 Soft delete and versioning on High
- Statement
- Blob soft delete (>= 7 days) and versioning are enabled; container soft delete where containers exist.
- Why
- Ransomware and a careless
azcopy sync --delete both end in deletion.
- Check
az storage account blob-service-properties show -n <account>
- Evidence
- Output per account.
- Remediation
- Enable both; raise retention for accounts holding sole copies.
ST-07 Diagnostic logging to a central workspace Medium
- Statement
- Storage read/write/delete logging is on and flows to the central Log Analytics workspace, not a local one.
- Why
- Without logs a key use is unattributable.
- Check
az monitor diagnostic-settings list --resource <account id>
- Evidence
- Diagnostic setting id and its destination.
- Remediation
- Add the diagnostic setting with the central workspace.
ST-08 Encryption with a customer-managed key where data is classified (ours) Medium
- Statement
- Accounts holding classified data use a CMK from Key Vault with soft-delete and purge protection.
- Why
- Platform-managed keys are fine until the data owner needs revocation.
- Check
az storage account show -n <account> --query encryption
- Evidence
- Key source, key vault and key id.
- Remediation
- Re-encrypt with a CMK; enable purge protection before the key is used.
ST-09 SAS lifetimes under 24 hours and user-delegation where possible (ours) Medium
- Statement
- No account SAS longer than 24 hours; new SAS are user-delegation.
- Why
- A stored SAS is a bearer credential with a fixed expiry, often a year.
- Check
- Inventory stored SAS in code and pipelines:
rg -n "sig=" <repo>
- Evidence
- Locations and their expiry settings.
- Remediation
- Reissue as user-delegation; shorten the lifetime; store in Key Vault where they must persist. ## Out of scope for this file Immutability (per-regulation), lifecycle rules (cost, not security), and cross-tenant replication. Each has its own decision record.
All baselines →
Elsewhere · Services · Academy · Labs · Tools
Breachcraft Security · Evilsaint Ltd · Terms · Privacy