Binding Digital Certificates to Sessions for Man-in-the-Middle Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data security techniques, such as SSL/TLS, face challenges in detecting unauthorized man-in-the-middle attacks, particularly in complex network configurations where computational resources are strained and latency is introduced, and sophisticated attacks can intercept and reencrypt communications, making it difficult to ensure secure data access.

Innovation Solution

The solution involves securely echoing digital certificates during encrypted communications sessions to verify the authenticity of the certificate received by the client, using cryptographic keys registered outside the handshake process to prevent tampering, and binding requests to sessions through session-specific information to prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If SSL/TLS protocols are used for secure communications, then data security is improved, but computational resources are consumed and latency is introduced

Engineering Contradiction:
Improvedata securityVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary actions by establishing encrypted sessions and obtaining digital certificates before actual data transmission. The client obtains a digital certificate from the server during session establishment, and both parties bind this certificate information to the session. This preliminary binding allows for efficient verification later without requiring additional computational resources during data transmission, as the security framework is already in place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the digital certificate information and binds it to the session identifier. The client receives a digital certificate from the server, creates a binding between this certificate and the session, and sends this bound information back to the server. This copying and binding mechanism allows for efficient verification of session authenticity without requiring the server to store or process the entire certificate during each data transmission operation.

Inventive Principle:
Principle #26Copying

2Reliability

If conventional SSL/TLS techniques are used, then data security is provided, but detection of man-in-the-middle attacks is difficult

Engineering Contradiction:
Improvedata securityVSAvoidman-in-the-middle attack detection
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements feedback by having the client send bound certificate information back to the server after receiving the digital certificate during session establishment. The server then verifies this bound information to confirm that the client actually received the correct certificate and that a man-in-the-middle did not intercept or substitute it. This feedback loop provides active verification of session authenticity and enables detection of man-in-the-middle attacks.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary verification actions by binding the digital certificate to the session identifier before any data transmission occurs. The client binds the received certificate to the session and sends this binding to the server for verification. This preliminary binding ensures that any subsequent data transmission can be verified against the authenticated session, making it possible to detect if a man-in-the-middle has established a separate unauthorized session.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If digital certificates are echoed during session establishment, then authenticity verification is improved, but session management complexity increases

Engineering Contradiction:
Improvecertificate authenticity verificationVSAvoidsession management
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system extracts only the essential certificate binding information and binds it to the session identifier, rather than managing entire certificate objects. The client obtains a digital certificate, extracts the relevant binding information, and associates it with the session identifier. This extraction approach simplifies session management by working with compact binding data rather than complex certificate structures, while still maintaining the ability to verify certificate authenticity.

Inventive Principle:
Principle #2Taking out (Extraction)

4Reliability

If cryptographic keys are registered outside the handshake process, then tampering prevention is improved, but key management complexity increases

Engineering Contradiction:
Improvetampering preventionVSAvoidkey management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary key registration actions by establishing cryptographic key associations between clients and servers before the actual data transmission session begins. The cryptographic keys are registered and bound to session identifiers in advance, creating a secure foundation that prevents tampering during the handshake and data transmission processes. This preliminary key establishment separates key management from the time-critical handshake process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10142111B2Binding digitally signed requests to sessions
Publication Date: 2018.11.27 AMAZON TECH INC
  • US10142111B2 patent drawing
  • US10142111B2 patent drawing
  • US10142111B2 patent drawing

AI summary

A client establishes an cryptographically protected communications session and determines information usable to distinguish the session from other sessions. The client digitally signs the information using a cryptographic key that is independent of the session to enable a server to check whether the information matches the session that it established and whether the digital signature is correct. The server may perform mitigating operations if either or both of the information or the digital signature is/are invalid.