Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
FAQShort answer
Each TLS version has removed the weak algorithms of the previous one and simplified the handshake. TLS 1.0 and 1.1 have been deprecated; TLS 1.2 is the most widely supported version today and is secure with strong cipher suites; TLS 1.3 contains only strong cipher suites, provides forward secrecy on every connection and reduces the full handshake to a single round trip. In TR7, the accepted version range is determined by the Min. SSL Version and Max. SSL Version fields on the TLS Security Profiles screen; Default Profile uses TLSv1.1 as the lower bound and sets no upper bound.
| Where | Field / label | What for |
|---|---|---|
| Certificates & PKI → TLS Security Profiles | Min. SSL Version (on in a new profile, TLSv1.1), Max. SSL Version (off; TLSv1.3 when turned on) | The accepted version range |
| HTTP and L7 TCP vService → Details | SSL Security | Assigning the profile to the vService; the profile that comes preselected is Default Profile |
| Backend Service | Backend SSL Security Profile | The version range TR7 accepts when connecting to the Backend Service |
| Load Balancer → Conditions (Policy Match) | SSL Version | A decision based on the version the client connected with |
| Version | Release | Status |
|---|---|---|
| SSL 3.0 | 1996 (RFC 6101) | Deprecated in 2015 by RFC 7568 |
| TLS 1.0 | 1999 (RFC 2246) | Deprecated in 2021 by RFC 8996 |
| TLS 1.1 | 2006 (RFC 4346) | Deprecated in 2021 by RFC 8996 |
| TLS 1.2 | 2008 (RFC 5246) | Widespread; recommended with cipher suites that provide forward secrecy and AEAD (RFC 9325) |
| TLS 1.3 | 2018 (RFC 8446) | Current; only AEAD cipher suites, forward secrecy on every connection, full handshake in a single round trip |
How it is done in the documentation

Reach us for your questions and support requests.
This document is digitally signed and timestamped.