Support Suite
TLS 1.2 - Transfer Layer Security - Can My Organization Stay Compliant?
Posted by Robert Joseph on 11 February 2019 05:35 PM
|
|
Many IT administrators wonder if they can stay compliant with changing TLS requirements. With the known security issues for TLS 1.0 and TLS 1.1, we can configure EIOBoard to use the most secure TLS available by installing version 10 or higher. The .NET Framework v4.6.2 makes these accommodations for clients to auto negotiate which version of TLS to use. Version 4.7.x of .NET removes this feature but adds support for TLS 1.2, and is included in version 10.3.x or higher.
Cloud-Hosted EIOBoard cloud servers use .NET Framework 4.7.2 as of version 10.1.5. In addition, we leverage SSL with RSA-2048 and multiple cipher suites supported at the client.
Customer-Hosted Customers that strictly require TLS 1.2 or higher for compliance requirements should install or upgrade to the latest version of EIOBoard (10.1.5 or higher). If the administrator disables TLS 1.0 or TLS 1.1 at the webserver, the EIOBoard clients can only connect through TLS 1.2 or higher so older client versions will no longer connect.
Force Outlook to Use TLS 1.2 for Customer-Hosted v10.1.5 or earlier Suppose an administrator cannot upgrade the customer-hosted EIOBoard server. In that case, we can supply a replacement DLL for the Outlook Add-In using a static requirement for TLS 1.2 connections. Please contact support for a download link.
This method works for one machine. However, when administrators have hundreds of devices requiring this change, we suggest using Microsoft Endpoint Configuration Manager or another automation tool.
Additional Resources https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls | |
|