Skip to content

Commit 32d7607

Browse files
authored
Add SHA 384 and ECC 256
1 parent b8e2158 commit 32d7607

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/security/fundamentals/encryption-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Whenever Azure Customer traffic moves between datacenters-- outside physical bou
110110

111111
Microsoft gives customers the ability to use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) protocol to protect data when it’s traveling between the cloud services and customers. Microsoft datacenters negotiate a TLS connection with client systems that connect to Azure services. TLS provides strong authentication, message privacy, and integrity (enabling detection of message tampering, interception, and forgery), interoperability, algorithm flexibility, and ease of deployment and use.
112112

113-
[Perfect Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS) protects connections between customers’ client systems and Microsoft cloud services by unique keys. Connections also use RSA-based 2,048-bit encryption key lengths and support AES 256 data encryption. This combination makes it difficult for someone to intercept and access data that is in transit.
113+
[Perfect Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS) protects connections between customers’ client systems and Microsoft cloud services by unique keys. Connections also support RSA-based 2,048 bit key lengths, ECC 256 bit key lengths, SHA 384 message authentication, and AES 256 data encryption. This combination makes it difficult for someone to intercept and access data that is in transit.
114114

115115
### Azure Storage transactions
116116

0 commit comments

Comments
 (0)