Optimizing Secure Session Testing via Cryptographic Handshake Bypass

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for testing secure communication devices are computationally intensive due to the need for real-time cryptographic handshakes and verifications, making it impractical to generate test loads of desired magnitudes within constrained test resources.

Innovation Solution

Optimizing cryptographic and secure handshakes by bypassing certain verification steps, reusing security mechanisms, and generating content contrary to standard-based protocols, allowing for faster and more efficient secure communication session setup between emulated servers and clients during testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If real-time cryptographic handshakes and verifications are performed during testing, then security protocol compliance is ensured, but computational resources and processing time are excessively consumed

Engineering Contradiction:
Improvesecurity protocol complianceVSAvoidtest generation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The testing system segments the testing process into two distinct phases: a setup phase where full cryptographic handshakes and verifications are performed to ensure protocol compliance, and a test execution phase where pre-established secure channels are reused without repeating the cryptographic operations. This segmentation allows the system to maintain security compliance while dramatically improving test generation speed during the actual testing phase.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary cryptographic handshakes and security verifications during the setup phase before actual testing begins. By completing these computationally intensive operations in advance, the system establishes secure channels that can be reused during test execution, eliminating the need to repeat cryptographic operations and thereby significantly reducing computational resource consumption during productivity-critical test generation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If full cryptographic verification steps are executed for each secure communication session, then security standards are met, but processing time increases significantly

Engineering Contradiction:
Improvesecurity standard complianceVSAvoidsession setup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements periodic cryptographic verification where full security handshakes are performed only once during the setup phase, and then the established secure channels are reused for multiple subsequent test sessions. This periodic approach ensures security standard compliance is maintained while dramatically reducing the time required for session setup during actual testing operations.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system creates copies of pre-established secure communication channels and reuses them across multiple test sessions. Instead of recreating cryptographic handshakes for each session, the system replicates and reuses the security context from the initial setup, maintaining security compliance while minimizing session setup time.

Inventive Principle:
Principle #26Copying

3Reliability

If computationally intensive cryptographic operations are performed for each test session, then security is maintained, but test resource constraints are exceeded

Engineering Contradiction:
Improvesecurity maintenanceVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system extracts the computationally intensive cryptographic operations from the regular test execution flow and isolates them to a separate setup phase. By taking out these resource-intensive operations from the productivity-critical test generation process, the system maintains security requirements while staying within computational resource constraints during actual testing.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system discards the need to repeatedly perform cryptographic operations during test execution by recovering and reusing the security context established during setup. This approach maintains security maintenance while dramatically reducing computational resource consumption during test generation by avoiding redundant cryptographic computations.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS11374973B2Streamlining cryptographic processes in a test environment
Publication Date: 2022.06.28 VIAVI SOLUTIONS LICENSING LLC
  • US11374973B2 patent drawing
  • US11374973B2 patent drawing
  • US11374973B2 patent drawing

AI summary

The technology disclosed is a method of testing handling of secure communication sessions of clients with servers by device or system under test (DUT). The method includes (i) establishing a secure communication session between the client and the server while the client and the server transitions past a standards-required verification step or validation step without performing the required verification or validation, (ii) establishing a secure communication session between the client and the server while the client and the server reuse standards-required security mechanisms without generating or obtaining new standards-required security mechanisms, or (iii) establishing a secure communication session between the client and the server while the client and the server generate and transmit content contrary to an established standard-based procedure that poses certain requirements of the content.