Discontinuation of Outdated Security Protocols TLS 1.0, TLS 1.1, and RSA+SHA1

To ensure the highest level of security for our company's services, we need to discontinue the use of older security protocols and weak encryption methods. Specifically, we must stop using TLS 1.0, TLS 1.1, and the RSA+SHA1 cipher suite.
What is Happening?
  • TLS 1.0 and TLS 1.1: These are older versions of the Transport Layer Security (TLS) protocol, which is used to secure communications over the internet. They have known vulnerabilities that can be exploited by attackers.
  • RSA+SHA1: This is an encryption method that uses the RSA algorithm combined with the SHA1 hashing function. It is no longer considered secure due to weaknesses that can be exploited to break the encryption.
Why Must We Take Action?
  • Security Risks: Continuing to use these outdated protocols and weak encryption methods exposes our company to potential security breaches. Attackers could intercept and manipulate sensitive data, leading to financial losses, reputational damage, and legal consequences.
  • Compliance: Many industry standards and regulations now require the use of stronger encryption methods. By discontinuing the use of TLS 1.0, TLS 1.1, and RSA+SHA1, we ensure compliance with these standards and avoid potential penalties.
  • Future-Proofing: Upgrading to more secure protocols and encryption methods, such as TLS 1.2 or later and stronger cipher suites, helps future-proof our services against emerging threats and ensures that we are using the best available security practices.
Schedule of Deprecation:
  • Support for these protocols will end on August 31, 2025

Taking these steps will enhance the security of our services, protect our customers' data, and maintain our company's reputation as a trusted and responsible organization.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article