Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Data Protection

Microsoft to Retire TLS 1.0/1.1 in Office 365 Starting October 15

Microsoft last week revealed plans to move forward with the retirement of the Transport Layer Security (TLS) 1.0 and 1.1 protocols in Office 365, starting October 15, 2020.

Microsoft last week revealed plans to move forward with the retirement of the Transport Layer Security (TLS) 1.0 and 1.1 protocols in Office 365, starting October 15, 2020.

Decades old, these protocol versions are considered obsolete, especially since the newer, safer TLS 1.2 and TLS 1.3 have been available for years. In fact, plans for their removal from major browsers and online services have been announced several years ago.

The deprecation of TLS 1.0 and 1.1 in major browsers has been delayed earlier this year, due to the COVID-19 pandemic, but others have already resumed plans in this direction, to ensure the security of their users.

In October 2018, Microsoft confirmed plans to remove support for the older protocols from its browsers, and also moved to deprecate TLS 1.0 and 1.1 for the Office 365 service.

Now, the company says it is ready to make the change in Office 365 clients as well, and plans to enforce the decision starting in the fall.

“We temporarily halted deprecation enforcement of TLS 1.0 and 1.1 for commercial customers due to covid-19, but as supply chains have adjusted and certain countries open back up, we are resetting the TLS enforcement to start Oct 15, 2020,” the company announced.

Advertisement. Scroll to continue reading.

The Office client can leverage TLS 1.2, as long as the web service of the machine supports it. Windows 8 and newer include support for TLS 1.2, but Windows 7 devices require the KB 3140245 update to use the TLS 1.1 and 1.2 protocols, Microsoft also explains.

Microsoft is also moving forth with the deprecation of TLS 1.0 and 1.1 in Office 365 GCC, citing known vulnerabilities in the TLS 1.0 implementation. The software giant also published a whitepaper to provide guidance on how organizations can identify and remove TLS dependencies in Windows applications.

Related: Chrome 84 Brings 38 Security Patches, Resumes CSRF Protection Rollout

Related: Browser Makers Delay Removal of TLS 1.0 and 1.1 Support

Related: Firefox 74 Patches Vulnerabilities, Disables TLS 1.0 and 1.1

Written By

Ionut Arghire is an international correspondent for SecurityWeek.

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Click to comment

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Today’s attackers are no longer breaking in — they’re logging in. Join this live webinar as we break down the modern identity attack chain and examine how recent breaches exploited weaknesses in authentication, identity verification, and access management processes.

Register

AI has accelerated both sides of the fight. Adversaries are weaponizing vulnerabilities faster, while defenders are racing to ship detections and configurations. Join this live webinar as we explore how to prove your controls actually hold against new threats, map your security maturity, and unite breach simulation with automated pentesting into a single, coordinated program.

Register

People on the Move

Stephen Garcia has been named Chief Information Security Officer at BreachRx.

Kasper Lindgaard has been appointed Vice President of Security Strategy at CoreView.

Chaim Mazal has been named Chief Information Security Officer at GitLab.

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.