To help our customers and partners understand the upcoming TLS 1.0 and 1.1 deprecation, we've compiled this FAQ. It covers the most common questions and provides guidance on ensuring a smooth transition to more secure connections.
General Questions
What is TLS? TLS, or Transport Layer Security, is a security protocol that encrypts communication over the internet. It ensures that when your device connects to our servers, the data exchanged is private and secure, preventing unauthorized access or tampering.
Why are you deprecating TLS 1.0 and 1.1? TLS version 1.0 and TLS version 1.1 are older encryption protocols with known security vulnerabilities. They are no longer considered compliant with current industry security standards, such as those recommended by NIST. By deprecating them and requiring TLS 1.2 or TLS 1.3, we're significantly enhancing the security of your data and providing a more robust, modern, and performant connection. This protects your information from potential risks.
When will TLS 1.0 and 1.1 be deprecated? TLS 1.0 and 1.1 will be deprecated on October 30, 2025. After this date, all connections to our services will require TLS 1.2 or TLS 1.3.
What will happen if I don't update my systems? If your systems or applications are still using TLS 1.0 or 1.1 after [Date], you will lose access to our services. Your connections will fail, preventing you from accessing your data or using our product.
Impact & Actions
How do I know if I'm using TLS 1.0 or TLS 1.1? Most modern web browsers, operating systems, and applications automatically use TLS 1.2 or TLS 1.3. You are likely already using a compliant version. However, if you are using older operating systems (i.e., Windows 7 without updates, Windows Server 2008 R2), older browsers, or custom/legacy applications, you might still be relying on TLS 1.0 or TLS 1.1. Check your system's or application's documentation for details on its TLS support.
What do I need to do to prepare for this change? You'll need to ensure that any systems, applications, or devices that connect to our services are configured to use TLS 1.2 or TLS 1.3. This may involve:
Updating your operating system: Ensure your OS is up to date.
Updating your web browser: Use the latest version of browsers like Chrome, Firefox, Edge, or Safari.
Updating your applications: If you use specific software to access our services, ensure it's updated to a version that supports TLS 1.2/TLS 1.3.
Updating development libraries: If you're a developer connecting via APIs, ensure your programming language and libraries support and are configured to use TLS 1.2/TLS 1.3.
Will this change affect my service performance? No, in fact, newer TLS versions (1.2 and 1.3) often offer performance improvements over their predecessors due to more efficient handshake processes and cryptographic algorithms.
Technical Guidance
How do I enable TLS 1.2 or TLS 1.3 on my system? The steps vary depending on your operating system and software:
For Windows Users:
Windows 8.1/10/11: TLS 1.2 is enabled by default. Ensure your OS is fully updated.
Windows 7: TLS 1.2 is supported but may not be enabled by default for all applications. Ensure all Windows Updates are installed. You might need to make specific registry changes for .NET applications or Internet Explorer. (Refer to Microsoft's documentation for detailed steps).
Windows Server (2008 R2 and later): TLS 1.2 is generally supported but might need to be explicitly enabled or ensured through updates.
For macOS Users:
Modern macOS versions support TLS 1.2 and TLS 1.3 by default. Ensure your macOS is updated to the latest version.
For Linux Users:
TLS support is dependent on your distribution and installed libraries (i.e., OpenSSL). Most modern Linux distributions use OpenSSL, which supports TLS 1.2/TLS 1.3. Ensure your system packages are up to date.
For Web Browsers:
Simply update your browser to the latest version. Most modern browsers automatically prefer TLS 1.2 or TLS 1.3.
For Custom Applications/APIs:
Consult the documentation for your specific programming language, framework, or API client library. Ensure they are configured to use the highest available TLS version.
Specific Software/User Agents
If you are using any of the following software or user agents to connect to our services, please consult their respective documentation or support channels for specific guidance on enabling TLS 1.2 or 1.3, especially if you encounter connection issues after the deprecation date.
Veeam:
Veeam Backup & Replication and Veeam Agents generally support TLS 1.2 and TLS 1.3. Ensure your Veeam software is updated to a recent version, and that the underlying Windows OS has TLS 1.2 enabled (especially on older Windows versions like Server 2008 R2/Windows 7, often requiring specific Microsoft KBs and registry settings).
Where to look: Veeam Help Center, Veeam Knowledge Base.
Cloud NAS (NetApp Cloud Volumes, Qumulo, etc.):
Specific configuration steps will vary by vendor and product version. Most modern Cloud NAS solutions are built to use current TLS standards.
Where to look: Your Cloud NAS vendor's documentation or support.
Tiger Technology (Tiger Bridge):
Tiger Technology solutions typically rely on the underlying operating system's TLS capabilities for secure connections. Ensure your OS and any relevant client components are configured for TLS 1.2/1.3.
Where to look: Tiger Technology support documentation or contact their support team.
Mozilla (Firefox):
Modern versions of Mozilla Firefox automatically support and prefer TLS 1.2 and TLS 1.3. Ensure your browser is updated to the latest stable release.
Where to look: Firefox Help (about:config security.tls.version.min should be set to 3 for TLS 1.2, but defaults usually handle this).
MSP360 (formerly CloudBerry Lab):
MSP360 (CloudBerry Backup) agents require TLS 1.2. If you are running older Windows operating systems (i.e., Windows 7, Windows Server 2008 R2), you will need to ensure TLS 1.2 is explicitly enabled at the OS level and your backup agent is updated to the latest version. Windows Server 2008 (non-R2) and Windows Vista do not support TLS 1.2 and would require an OS upgrade.
Where to look: MSP360 documentation on "Supported TLS Versions" or their support forum.
AWS-SDK (Amazon Web Services Software Development Kit):
AWS SDKs in various programming languages (Java, Python, .NET, etc.) generally support TLS 1.2 and TLS 1.3. The behavior can depend on the SDK version and the underlying JVM/runtime environment. Older SDK versions or older JVMs might require specific configuration or updates.
Where to look: AWS SDK documentation for your specific language (i.e., AWS SDK for Java Developer Guide, AWS SDK for Python (Boto3) documentation). Look for sections on "SSL/TLS," "HTTP client configuration," or "enforcing TLS versions."
If your specific third-party software is not listed above, please reach out to support@wasabi.com.
For Our Partners
How should I communicate this to my customers? We recommend informing your customers about this change well in advance of the October 30, 2025 deadline. Emphasize the security benefits and provide them with the TLS Depreciation KB article (https://docs.wasabi.com/v1/docs/enhancing-your-security-an-important-update-on-tls-10-and-11-deprecation) for instructions. Offer your own support for specific integration questions they might have related to their use of Wasabi hot cloud storage services.
What if my customer needs help that I can't provide? If your customers encounter issues that you cannot resolve, please direct them to our support channel at support@wasabi.com for assistance. We are ready to help ensure a smooth transition for all.