Azure Storage Account HTTPS Not Enforced
Data can be read and written over plain HTTP, exposing both the contents and the access key used to reach them.
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: Enforce HTTPS-only 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 Secure transfer required (labeled
Require secure transfer for REST API operationsin current Portal copy) = Enabled. - Set Minimum TLS version = 1.2 (or 1.3 where supported).
- Audit any app, SDK, or pipeline that still uses http://. They will start failing once HTTPS is required.
- Save; the change is online but in-flight HTTP requests will be rejected immediately.
- Verify with
curl -I http://‹name›.blob.core.windows.net/. It should return 400 InsecureTransferNotAllowed.
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-1322- 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.