To align with modern security best practices and ensure the highest level of data protection, Quest Rapid Recovery is removing support for Transport Layer Security (TLS) 1.0 starting with version 6.11. Going forward, the Rapid Recovery Core will require more secure cryptographic protocols (such as TLS 1.2 or higher) for all communications.
Why is TLS 1.0 being removed?
TLS 1.0 is an outdated protocol first introduced in 1999. Over the years, it has become vulnerable to several well-known cryptographic exploits (such as POODLE and BEAST).
Because TLS 1.0 no longer meets modern compliance standards (including PCI-DSS) or security benchmarks, it is being deprecated to safeguard your backup environments from potential interception or tampering.
When upgrading to or installing Rapid Recovery 6.11, any connection relying strictly on TLS 1.0 will fail. This impacts:
Core-to-Agent Communications: Older protected machines running legacy operating systems that do not support TLS 1.2 out of the box.
Core-to-Core Replication: Target or source Cores running older versions that rely on TLS 1.0.
Management Console Access: Older web browsers or API integrations that do not support modern TLS protocols.
To ensure a seamless upgrade to version 6.11 and avoid any interruption in your backup schedules, please take the following steps:
1. Verify Operating System Compatibility
Ensure that all machines hosting the Rapid Recovery Core and Agents are running operating systems that natively support and have TLS 1.2 enabled.
Note: For older legacy systems (like Windows Server 2008 R2 or Windows 7), you may need to manually install Microsoft patches and edit the registry to enable TLS 1.2.
2. Update Modern Browsers
Ensure that administrators accessing the Rapid Recovery Core Console are using updated, modern web browsers with TLS 1.2 or TLS 1.3 enabled.
3. Plan Your Upgrade Environment
If you utilize Core-to-Core replication, ensure that both the source and target Cores are upgraded to versions that support modern TLS protocols to prevent replication failures.
