{"id":68785,"date":"2017-06-20T09:00:46","date_gmt":"2017-06-20T16:00:46","guid":{"rendered":"http:\/\/blogs.microsoft.com\/microsoftsecure\/?p=68785"},"modified":"2023-05-15T23:11:17","modified_gmt":"2023-05-16T06:11:17","slug":"tls-1-2-support-at-microsoft","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2017\/06\/20\/tls-1-2-support-at-microsoft\/","title":{"rendered":"TLS 1.2 support at Microsoft"},"content":{"rendered":"

This post is authored by Andrew Marshall, Principal Security Program Manager, Trustworthy Computing Security<\/em>.<\/p>\n

In support of our commitment to use best-in-class encryption, Microsoft\u2019s engineering teams are continually upgrading our cryptographic infrastructure. A current area of focus for us is support for TLS 1.2, this involves not only removing the technical hurdles to deprecating older security protocols, but also minimizing the customer impact of these changes. To share our recent experiences in engaging with this work we are today announcing the publication of the \u201cSolving the TLS 1.0 Problem<\/a>\u201d whitepaper to aid customers in removing dependencies on TLS 1.0\/1.1. Microsoft is also working on new functionality to help you assess the impact to your own customers when making these changes.<\/p>\n

What can I do today?<\/h2>\n

Microsoft recommends customers proactively address weak TLS usage by removing TLS 1.0\/1.1 dependencies in their environments and disabling TLS 1.0\/1.1 at the operating system level where possible. Given the length of time TLS 1.0\/1.1 has been supported by the software industry, it is highly recommended that any TLS 1.0\/1.1 deprecation plan include the following:<\/p>\n