Azure Storage Account Public Access Enabled
Blobs can be read anonymously, so anything in the container is effectively published.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Block anonymous blob access on storage account.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Storage Accounts on Azure
- The fix, by hand
- Storage account → the resource → Settings → Configuration.
- Set Allow Blob public access = Disabled (this is the account-level kill switch; even containers set to public become private).
- Containers that genuinely need anonymous read should move behind Azure CDN / Front Door with a SAS, or switch to Azure AD-authorized access.
- Review existing container public access levels under Data storage → Containers; flip any still set to Container or Blob back to Private.
- Save and confirm via
az storage container list --account-name ‹name› --auth-mode loginshows publicAccess = null everywhere.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1323- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.