I. Overview 

%%{init: { 'theme': 'base', 'themeVariables': { 'edgeLabelBackground': '#fff' }}}%%
flowchart LR
    A["Plaintext comms and\nweak legacy SSL"] -- "Confidentiality, integrity, and\nhandshake overhead optimized" --> B["Hardened, high-performance\nTLS (especially 1.3)"]
    style A fill:#f9f9f9,stroke:#333,stroke-width:3px
    style B fill:#e1f5fe,stroke:#01579b,stroke-width:3px

Definition: A transport-layer security protocol ( RFC 8446 ) that establishes an encrypted channel between a client and a server to guarantee the confidentiality, integrity, and authentication of data in internet communications.

Features:
( Hybrid Cryptosystem ) Uses public-key cryptography ( Asymmetric ) to safely exchange a symmetric key, then transmits the actual data using fast symmetric-key encryption ( Symmetric ).
( Integrity Assurance ) Uses a message authentication code ( MAC ) or HMAC to verify in real time whether data has been tampered with in transit.
( Strong Authentication ) Uses digital certificates ( X.509 ) and the PKI system to verify the identity of the communicating party and prevent man-in-the-middle attacks ( MITM ).
( Performance Optimization ) The latest TLS 1.3 shortens the handshake ( 1-RTT, 0-RTT ), achieving both security and speed.

II. Mechanism & Components

TLS 1.3 Handshake Flow (1-RTT) 

sequenceDiagram
    participant C as "Client"
    participant S as "Server"

    Note over C,S: "1. Client Hello (supported algorithms, Key Share)"
    C->>S: "Client Hello"

    Note over S,C: "2. Server Hello (algorithm confirmed, Certificate, Finished)"
    S-->>C: "Server Hello + Encrypted Extensions + Certificate + Finished"

    Note over C,S: "3. Certificate verification and start of data transmission"
    C->>S: "Finished (Encrypted)"

    Note over C,S: "4. Secure Application Data Exchange"
    C->>S: "Application Data (Encrypted)"
    S->>C: "Application Data (Encrypted)"

The Four Sub-Protocols That Make Up TLS

ProtocolDetailed DescriptionPrimary Role
HandshakeNegotiates the encryption algorithm ( Cipher Suite ) and generates the session keyMutual authentication and agreement on security parameters
Change Cipher SpecNotifies that subsequent messages will be sent using the negotiated cipher specNotification of the switch to encrypted mode
AlertCommunicates errors or risk conditions that occur during communicationError handling and session termination control
RecordThe basic unit that fragments, compresses, and encrypts actual data for transmissionData encapsulation and integrity protection

III. Advanced Topics & Comparison

TLS 1.2 vs. TLS 1.3 Key Differences

ComparisonTLS 1.2TLS 1.3
Handshake Speed2-RTT (requires two round trips)1-RTT / 0-RTT (substantially faster)
Encryption AlgorithmsIncludes RSA, Static DH (vulnerabilities exist)Allows only algorithms that support PFS (e.g. ECDHE)
SecurityPart of the handshake is exposed in plaintextNearly all of the handshake is encrypted from the start
Cipher SuitesDozens of varied combinations (complex to manage)Simplified to five secure combinations
  • PFS (Perfect Forward Secrecy): Essential adoption of one-time session keys so that even if the server’s private key is later leaked, past communications cannot be decrypted.
  • HSTS (HTTP Strict Transport Security): Forces browsers to use only HTTPS connections, defending against protocol downgrade attacks.
  • SNI Encryption (ESNI / ECH): Encryption technology introduced to solve the problem of the Server Name Indication ( SNI ) being exposed in plaintext, revealing the connection destination.

Key Point: TLS is the foundation of modern web security, and adopting TLS 1.3 in particular — eliminating security weaknesses while maximizing communication performance — is an essential security strategy.

Edit this page

Last updated 18 Aug 2026, 00:00 UTC. history