Will It Vibe?Azure storage account allows public blob access
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
allow_blob_public_access = true (or allow_nested_items_to_be_public = true) lets containers be configured for anonymous public read, exposing blobs to the internet.
Why it matters
allow_blob_public_access = true (or allow_nested_items_to_be_public = true) permits containers in the storage account to be set for anonymous public read. That opens the door to exposing blobs to the internet, and it only takes one container configured for public access to leak data. The safe default is to disallow public access at the account level.
How to fix it
Set allow_nested_items_to_be_public = false (the current argument name; allow_blob_public_access on older provider versions) on the azurerm_storage_account. Serve any genuinely public content through a CDN or a SAS-tokened URL rather than anonymous container access. Audit existing containers for public access levels after tightening the account.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo