A TLS session ticket lets a client resume a previously established encrypted connection without repeating the full handshake. The server issues the ticket, typically protected with a server-side key, and the client presents it when reconnecting. Resumption can reduce latency and server workload.
Ticket handling is security-sensitive: if ticket-protection keys are exposed, reused unsafely, or rotated incorrectly, attackers may be able to misuse tickets or undermine session security, depending on the TLS implementation and configuration. In real deployments, defenders should keep TLS software updated, protect ticket keys, and follow vendor guidance for key rotation and ticket sharing across servers. A ticket is not the same as a certificate, and its use does not by itself prove that a connection was compromised.