Support for TLS 1.3 Now Available — Deprecation of TLS 1.0 and 1.1.
Effective date: 2 September 2025
Announced: 2 June 2025
To maintain the highest standards of security and compliance, we at Hub88 are updating the Transport Layer Security (TLS) protocol requirements.
What’s new?
Hub88 now fully supports TLS 1.3 for all API connections. TLS 1.3 offers significantly enhanced encryption, reduced handshake latency, and improved overall efficiency — aligning with industry best practices for secure communication.
What’s changing?
Beginning 2 September 2025, TLS 1.0 and TLS 1.1 will be permanently disabled across all Hub88 services. These legacy protocols are no longer considered secure and will be blocked at the network level. Any attempted connections using these versions will be rejected.
Action required by 2 September 2025
Failure to transition away from TLS 1.0 and 1.1 by this date will result in connection failures and potential service disruption. If you require assistance reviewing or updating your integrations, please contact your Hub88 technical representative.
What you should do?
Review your system configurations and identify any endpoints or services that still use TLS 1.0 or 1.1.
Ensure that all API traffic is conducted over TLS 1.2 or TLS 1.3.
We strongly recommend migrating to TLS 1.3 where possible, as it offers better performance, security, and forward compatibility.
Why this matters?
Deprecating outdated protocols is a necessary step in safeguarding data integrity, maintaining regulatory compliance, and preventing vulnerabilities from legacy encryption methods. Upgrading ensures uninterrupted service and aligns your systems with modern security standards.
Last updated
Was this helpful?