Security update — TLS v1.1 deprecation

TomasH@kentico.com[email protected] Member, Kentico Staff mod
edited June 2017 in Announcements

As part of our ongoing efforts to enhance security and protect your sensitive data, Kentico Cloud has decided to upgrade the information sharing protocol to the TLS v1.2.

Effective immediately, it is required to use the Transport Layer Security v1.2 (TLS12) protocol to establish SSL connections with Kentico Cloud services.

Our technology service providers are changing the TLS support as well. You can read about the TLS upgrade for Fastly—the Content Delivery Network that Kentico Cloud uses under the hood.

How Can You Keep Your Application up to Date?

To make your application compatible with the TLS v1.2 protocol, you should update your environment. The steps needed to keep your environment up to date depend on the framework that you use. Below, you can learn more about the steps needed for .NET framework versions.

.NET Framework 4.6 or Higher

No steps are needed. .NET 4.6 or newer is fully compatible with TLS v1.2 by default.

.NET Framework 4.5 to .NET Framework 4.5.2

These versions of .NET do not enable TLS v1.2 by default, but you can enable it either by configuring your application to support TLS (by modifying your Startup

public partial class Startup
{
  public void Configuration(IAppBuilder app)
  {
    ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12; 
   }
 }

or by changing supported runtime to 4.6.1 or newer in your config file:

.NET Framework 4.0

To keep your integrations compatible with the latest standards, it is recommended to upgrade to the latest .NET framework version.

.NET framework 3.5 and below

These .NET versions are not compatible with TLS v1.1 or higher. To keep your integrations compatible with the latest standards, it is recommended to upgrade to the latest .NET framework version.

If you have any questions about how to make .NET or other languages work regarding TLS, don't hesitate to reach out to us.

Tagged:

Comments

  • mattnieldmattnield Witney, UKMember, MVP MVP

    Umm - did you send anything prior to this out as a warning?

  • TomasH@kentico.com[email protected] Member, Kentico Staff mod
    edited May 2017

    @MattNield, regrettably, we needed to update the TLS version immediately, because we missed the announcement made by our Content Delivery Network — Fastly. We reacted as soon as possible by notifying all developers and project managers who use Kentico Cloud. We are very sorry for any inconveniences this may have caused you. Looking ahead, we want to assure you that we guarantee the timeliness of all such announcements in the future. We will reach out to you on your email, or you could read them on http://status.kenticocloud.com/ where you can subscribe to updates. Anyway, don't hesitate to reach out to us any time, we're always here to help.

Sign In or Register to comment.