Follow

Upcoming Decommission of TLSv1.0 and v1.1 for Public Cloud Customers - February 9, 2017

Due to a series of vulnerabilities in Secure Sockets Layer (SSL) and Transport Layer Security (TLS) over the past few years, as well as to meet the PCI Council’s requirements, we are scheduling security upgrades to our platform.   

Late last year, we dropped support for the SSL v3.0 protocol. On Wednesday, March 15, 2017, we will be dropping support for the TLSv1.0 and v1.1 protocols in our default configuration, and will be supporting only TLSv1.2 going forward. What this means for you is that your customers using older web browsers–especially browsers older than Internet Explorer 11, Safari 7, and Android 5, may not support TLSv1.2, and would not be able to access your sites.  

If you have concerns about your domains supporting only TLSv1.2, please contact Distil no later than Tue, Feb. 28, 2017 to request that your company be placed on the “Deferred Upgrade” list. You will then have until March 31st, 2017 to determine a date you would like to migrate on, which can be no later than June 15th, 2017. 

If you have no concerns about this change in TLS protocol support and wish to proceed with the upgrade as currently scheduled, then no action will be required on your part, and Distil will make the necessary changes on March 15th, 2017.

Customers Wishing to Upgrade on Distil’s Schedule

Date

Actions Required by You

Actions Required by Distil

March 15th, 2017

None

Upgrade your account to use TLSv1.2 only

 

Customers Wishing to Defer Upgrade

Date

Actions Required by You

Actions Required by Distil

No Later Than

Feb 28th, 2017

Notify Distil Support of your request for deferral of the TLS upgrade

Place your company on the “Deferred Upgrade” customer list

No Later Than

March 31st, 2017

Notify Distil Support with your company’s desired date of upgrade

Update your company information on the “Deferred Upgrade” list with your desired date

Chosen Upgrade Date

or

June 15th, 2017

None

Upgrade your account to use TLSv1.2 only

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments