Ephemeral Value Authentication for Application Code Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data authentication methods fail to effectively detect tampering or modifications of application code, especially in devices manufactured by adversarial entities, and do not efficiently validate unchanged components during software maintenance and upgrades.

Innovation Solution

The use of an ephemeral, unpredictable value for authenticating data, including application code, through digital signature generation and comparison, ensures that operational parts of application code remain unchanged, even in devices manufactured by potential adversaries, and reduces recertification efforts during software updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods are used to verify application code integrity, then the authentication process can be performed, but it fails to effectively detect tampering in devices manufactured by adversarial entities and requires extensive recertification during software updates

Engineering Contradiction:
Improveauthentication effectivenessVSAvoidrecertification efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The authentication system divides the application code into authenticated segments and unauthenticated segments. Only the authenticated segments (which remain unchanged) need to be verified, while unauthenticated segments (which may change during updates) are excluded from authentication requirements. This segmentation allows the system to maintain security for critical code while enabling efficient updates for other portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs authentication setup in advance by identifying which code segments should be authenticated and generating the necessary authentication data structures before software updates occur. This preliminary configuration enables rapid verification during updates without requiring full recertification, as the authentication framework is already in place.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If comprehensive authentication of entire application code is performed, then code integrity is verified, but the process becomes complex and time-consuming during normal software maintenance and upgrades

Engineering Contradiction:
Improveintegrity verification accuracyVSAvoidauthentication process complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The authentication system divides the application code into authenticated segments and unauthenticated segments. Only the authenticated segments (which remain unchanged) need to be verified, while unauthenticated segments (which may change during updates) are excluded from authentication requirements. This segmentation allows the system to maintain security for critical code while enabling efficient updates for other portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of authenticating the entire application code base, the system applies authentication only to specific segments that require integrity verification. This partial authentication approach reduces complexity and update overhead while maintaining security for critical portions of the code.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If authentication mechanisms are implemented to detect tampering in adversarial devices, then security is improved, but the authentication process requires significant computational resources and time

Engineering Contradiction:
Improvetamper detection capabilityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The authentication system divides the application code into authenticated segments and unauthenticated segments. Only the authenticated segments (which remain unchanged) need to be verified, while unauthenticated segments (which may change during updates) are excluded from authentication requirements. This segmentation allows the system to maintain security for critical code while enabling efficient updates for other portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of authenticating the entire application code base, the system applies authentication only to specific segments that require integrity verification. This partial authentication approach reduces complexity and update overhead while maintaining security for critical portions of the code.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8407479B2Data authentication and tamper detection
Publication Date: 2013.03.26 HONEYWELL INTERNATIONAL INC
  • US8407479B2 patent drawing
  • US8407479B2 patent drawing
  • US8407479B2 patent drawing

AI summary

One embodiment includes a method that includes receiving an ephemeral value from a challenging device. The method also includes retrieving data whose content is presumed known to the challenging device. The method includes generating a digital signature of the data based on the ephemeral value. Additionally, the method includes transmitting the digital signature to the challenging device.