Storage Account: Vulnerabilities Reported by Encryption Algorithms — Investigating TLS Protocol Detection

John Avilán - CSE 0 Reputation points
2026-11-17T21:00:24.71+00:00

Descripción del problema

I am concerned about reported vulnerabilities related to encryption algorithms in my storage account. Specifically, security scans have indicated the presence of TLS 1.0 and 1.1 protocols, which are deprecated. I need to verify whether these vulnerabilities are genuine or false positives, considering my storage account is configured to require TLS 1.2 and enforce HTTPS.

Entorno

The affected service is Storage Account Management, region East US

Lo que ya he probado

I have verified that the minimum TLS version and HTTPS transfer settings are correctly configured to TLS 1.2 and enabled, respectively. I also reviewed public documentation indicating that TLS 1.0 and 1.1 are no longer supported and that Private Endpoints do not alter the TLS policy of the storage account.

Estado actual

I am seeking guidance to confirm whether the security scan results are accurate, and if not, how to demonstrate that my storage account configuration is compliant with security standards. I also want to understand the correct procedures to validate TLS negotiation with Azure Storage, considering private endpoints and DNS configurations.

Azure Storage
Azure Storage

Globally unique resources that provide access to data management services and serve as the parent namespace for the services.

0 comments No comments

1 answer

Sort by: Most helpful
  1. SHOUMIK CHAKRAVARTY 1,625 Reputation points
    2026-11-18T02:05:47.5166667+00:00

    Hi @John Avilán - CSE - welcome to the Microsoft Azure QnA.

    A scanner reporting TLS 1.0 or 1.1 does not necessarily mean your storage account accepts those versions. Azure Storage enforces the minimum TLS setting after the connection is established, while many protocol scanners only look at the handshake.

    From Enforce a minimum required version of TLS:

    “The minimum TLS version setting is checked after the connection is established. If the request uses an earlier version of TLS than that specified by the setting, the connection will continue to succeed, but the request will eventually fail.”

    “Tools that attempt to determine TLS support at the protocol layer may return TLS versions in addition to the minimum required version when run directly against the storage account endpoint.”

    The TLS handshake can succeed even when the account requires TLS 1.2. Azure Storage enforces the minimum TLS setting when the request is processed, so a scanner that only looks at the handshake can report older TLS versions. The same symptom came up in an earlier Q&A thread.

    Test it properly

    curl -v --tls-max 1.0 https://<account>.blob.core.windows.net/
    curl -v --tls-max 1.2 https://<account>.blob.core.windows.net/
    

    A request below the minimum returns HTTP 400 saying the TLS version is not permitted for this storage account. A 400 on the first and a normal response on the second confirms enforcement. If a TLS 1.0 request succeeds and the storage service processes the request successfully, then the finding needs further investigation. Also check the scanner is hitting your storage endpoint and not a proxy in front of it.

    On weak ciphers

    If the scan also flags 3DES, that is not tunable:

    “It is not possible to configure a storage account to block the use of specific ciphers, other than by requiring a minimum TLS version.”

    Use Application Gateway if you need cipher control.

    Evidence for the audit

    az storage account show --name <account> --resource-group <rg> --query minimumTlsVersion --output tsv
    
    StorageBlobLogs
    | where TimeGenerated > ago(7d) and AccountName == "<account-name>"
    | summarize count() by TlsVersion
    

    This shows every TLS version used against the account over the period. If anything below 1.2 appears, add | project TlsVersion, CallerIpAddress, UserAgentHeader against those rows to identify the clients. The same page also has an Azure Policy audit rule for a compliance report across accounts

    If this helps resolve your question, please accept the answer or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.