Pre-authentication Service for TLS Handshake Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network security protocols, such as TLS 1.3, are vulnerable to resource denial of service attacks and reconnaissance for vulnerabilities, as they do not adequately authenticate clients before the handshake process, allowing adversarial devices to exploit server resources and compromise communication security.

Innovation Solution

Implementing a pre-authentication service that includes an authentication string with a message authentication code (MAC) in the Client Hello message, allowing servers to authenticate clients before proceeding with the handshake, thereby preventing unauthorized access and resource exploitation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TLS 1.3 handshake is implemented without pre-authentication, then communication security is maintained, but server resources are wasted and DoS attacks are facilitated

Engineering Contradiction:
Improvecommunication securityVSAvoidserver resources
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by implementing pre-authentication before the TLS handshake. The server verifies the client's authentication string (containing MAC) before proceeding with the full handshake process. This preliminary verification prevents unauthorized clients from exhausting server resources during handshake operations, while still maintaining secure communication for authenticated clients.

Inventive Principle:
Principle #10Preliminary action

2Loss of energy

If pre-authentication with MAC verification is implemented, then resource wastage is reduced and DoS attacks are prevented, but authentication complexity increases

Engineering Contradiction:
Improveserver resourcesVSAvoidauthentication process
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The authentication process is segmented into distinct phases: (1) Client generates authentication string with MAC using its private key, (2) Server verifies MAC before handshake, (3) If verification passes, full TLS handshake proceeds. This segmentation separates the lightweight authentication verification from the heavier handshake process, reducing overall complexity while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication string containing MAC acts as an intermediary mechanism between the client and server. Instead of complex mutual authentication, the server simply verifies the MAC signature in the Client Hello message. This intermediary approach simplifies the server's burden while ensuring client authenticity before resource allocation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If client authentication is performed after handshake completion, then handshake process remains simple, but vulnerability reconnaissance and malicious access are enabled

Engineering Contradiction:
Improvehandshake processVSAvoidvulnerability reconnaissance
Core Design Contradiction:
Device complexityVSObject-affected harmful factors

Solution Approach 1:

The patent performs authentication verification as a preliminary action within the handshake process itself, specifically in the Server Hello phase before key exchange and data transmission begin. This timing allows the server to verify client authenticity early, preventing vulnerability reconnaissance and malicious access while maintaining a relatively simple handshake structure.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12003493B2Device pre-authentication
Publication Date: 2024.06.04 VERIZON PATENT & LICENSING INC
  • US12003493B2 patent drawing
  • US12003493B2 patent drawing
  • US12003493B2 patent drawing

AI summary

A method, a device, and a non-transitory storage medium are described in which an pre-authentication service is provided. The service may support a transport layer security handshake and determine authentication based on the initial message. The service may provide for the generation of a message that initiates a handshake between devices in which the message includes an authentication string used for authentication. The service may provide for the generation of another authentication string for comparison. The service may also support authorization of a device. The service may minimize potential malicious attacks and activities between the devices.