Skip to content

Commit a87b67d

Browse files
Merge pull request #270019 from normesta/networking-2
Making clear that Azure Storage does not use OpenSSL
2 parents 94f9256 + 117b1d9 commit a87b67d

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/storage/common/transport-layer-security-configure-minimum-version.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: normesta
77

88
ms.service: azure-storage
99
ms.topic: how-to
10-
ms.date: 12/30/2022
10+
ms.date: 03/22/2024
1111
ms.author: normesta
1212
ms.reviewer: fryu
1313
ms.subservice: storage-common-concepts
@@ -21,6 +21,9 @@ Communication between a client application and an Azure Storage account is encry
2121

2222
Azure Storage currently supports three versions of the TLS protocol: 1.0, 1.1, and 1.2. Azure Storage uses TLS 1.2 on public HTTPS endpoints, but TLS 1.0 and TLS 1.1 are still supported for backward compatibility.
2323

24+
> [!TIP]
25+
> Azure Storage relies on Windows implementation of SSL that is not based on OpenSSL and therefore is not exposed to OpenSSL related vulnerabilities.
26+
2427
Azure Storage accounts permit clients to send and receive data with the oldest version of TLS, TLS 1.0, and above. To enforce stricter security measures, you can configure your storage account to require that clients send and receive data with a newer version of TLS. If a storage account requires a minimum version of TLS, then any requests made with an older version will fail.
2528

2629
This article describes how to use a DRAG (Detection-Remediation-Audit-Governance) framework to continuously manage secure TLS for your storage accounts.

0 commit comments

Comments
 (0)