Brightmetrics has deprecated support of TLS 1.0 and TLS 1.1 encryption. If your server running the Brightmetrics Agent Service currently doesn't support TLS 1.2, Brightmetrics will no longer work for you. Here are the details you need to know.
- Who does this affect?
- Brightmetrics customers running the Brightmetrics Agent Service on a server with a .Net Framework version below 4.5. Brightmetrics requires .Net Framework version to be 4.5 or higher.
- Brightmetrics customers using agent versions 3.2 or below
- Not sure which version you're on? This article will show you how to find out, and how to update it.
- When did Brightmetrics disable TLS 1.0 and TLS 1.1?
- We no longer support TLS 1.0 or TLS 1.1 as of December 31, 2022.
- We understand certain Mitel versions only support TLS 1.0. You can leave TLS 1.0 enabled for Mitel, and also enable TLS 1.2 for us.
- Why did Brightmetrics making this change?
- Brightmetrics takes data protection seriously, so we will occasionally need to make security improvements in order to maintain the highest level of security for your data.
- What do I need to do?
- Update the server (.NET Framework, TLS settings and/or content filters) your Brightmetrics agent is installed on to support TLS 1.2 (See Microsoft's blog about TLS 1.2 support added to Windows Server 2008). We recommend using the utility IISCrypto to manage TLS configuration. Generally, you just want to click "Best Practices," but consult with the appropriate application, server, and/or network management technical resource(s) before making any changes to a server's communications protocols. Please make sure to reboot the server after making changes.
-
Please note that TLS 1.0 does not need to be disabled in order for TLS 1.2 to be enabled.
-
- Update the server (.NET Framework, TLS settings and/or content filters) your Brightmetrics agent is installed on to support TLS 1.2 (See Microsoft's blog about TLS 1.2 support added to Windows Server 2008). We recommend using the utility IISCrypto to manage TLS configuration. Generally, you just want to click "Best Practices," but consult with the appropriate application, server, and/or network management technical resource(s) before making any changes to a server's communications protocols. Please make sure to reboot the server after making changes.
Have questions? Contact our team at support@brightmetrics.com.
Comments
Article is closed for comments.