Remote Message Attestation via Pre-established Certificates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote attestation methods in computer system security are limited in scenarios where immediate end-to-end connectivity is not available, such as store-and-forward messaging and Delay- and Disruption Tolerant Networking, making it difficult to verify the software configuration of a message sender across multiple intermediaries.

Innovation Solution

A method involving the creation of asymmetric key pairs and certificates within a trusted platform module and an application, allowing for secure message signing and verification of software platform state information, even in the absence of direct end-to-end connectivity, by using attestation identity keys and cryptographic transformations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional interactive remote attestation methods are used, then the software configuration of a device can be verified, but immediate end-to-end connectivity between the remote and target devices is required

Engineering Contradiction:
Improvesoftware configuration verificationVSAvoidconnectivity scenario flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the remote attestation process into two independent phases: (1) a setup phase where the remote device interacts with a target device to establish cryptographic bindings between platform configuration register (PCR) values and asymmetric key pairs, and (2) a message signing phase where the remote device can independently sign messages using the established key pairs without requiring real-time connectivity to the target device. This segmentation allows the attestation relationship to be established once and reused across multiple communication scenarios including store-and-forward messaging and delay-tolerant networking.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-establishing the cryptographic binding between PCR values and asymmetric key pairs during an initial setup phase before actual message communication occurs. The target device signs the remote device's public key along with relevant PCR values to create a certificate that binds the software configuration state to the cryptographic identity. This preliminary attestation relationship enables subsequent message signing operations to proceed independently without requiring the target device to be immediately available, thus enabling operation in scenarios without immediate end-to-end connectivity.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple intermediaries are involved in message transmission, then store-and-forward messaging is enabled, but verifying the sender's software configuration becomes more difficult

Engineering Contradiction:
Improvemessage routing flexibilityVSAvoidsender verification complexity
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces digital certificates as intermediary objects that mediate the verification process between the remote device and message recipients. The target device acts as a trusted intermediary by signing the remote device's public key together with PCR values to create a certificate. This certificate serves as verifiable evidence that binds the sender's software configuration state to their cryptographic identity. Intermediate nodes in the message routing path can forward messages with these certificates attached, and final recipients can verify the sender's software configuration by checking the certificate signature without needing to interact with the original target device, thus simplifying verification across multiple intermediaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a verifiable copy of the sender's software configuration state by having the target device sign the PCR values and bind them to the sender's public key in a certificate. This signed certificate is a portable, immutable copy of the attestation evidence that can be attached to messages and forwarded through multiple intermediaries. The certificate serves as a self-contained verification artifact that contains all necessary information (public key, PCR values, signature) for recipients to verify the sender's software configuration without requiring real-time access to the sender's device or the original target device, thus enabling verification in store-and-forward messaging scenarios.

Inventive Principle:
Principle #26Copying

3Reliability

If asymmetric key pairs and certificates are created and verified, then message authenticity and software configuration trust are ensured, but computational overhead and processing time increase

Engineering Contradiction:
Improvemessage authenticityVSAvoidmessage processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs the computationally intensive certificate creation operation in advance during an initial setup phase. The target device signs the remote device's public key along with PCR values to create a certificate, which is then stored on the remote device. During subsequent message communication, the remote device simply uses its private key to sign messages, and recipients verify signatures using the pre-established public key and certificate. This eliminates the need to perform complex attestation computations during every message exchange, significantly improving processing efficiency while maintaining strong authenticity and configuration verification guarantees.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the cryptographic operations into a heavy setup phase and a lightweight message signing phase. The setup phase involves creating asymmetric key pairs, measuring platform configuration, and generating signed certificates - operations that are computationally intensive but performed only once per communication partner. The message signing phase involves only signing messages with the private key and verifying signatures with the public key - operations that are computationally lightweight and can be performed efficiently for every message. This segmentation allows the system to achieve strong security guarantees while maintaining high message processing throughput.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2171633B1Method for remote message attestation in a communication system
Publication Date: 2016.01.06 NOKIA TECHNOLOGIES OY
  • EP2171633B1 patent drawingFigure 1
  • EP2171633B1 patent drawingFigure 2A
  • EP2171633B1 patent drawingFigure 2B

AI summary

The invention relates to a method for remote attestation. In the method is created a first asymmetric key pair (302) in a trusted platform module in an electronic device. A first public key and software platform state information are certified (306) with an attestation identity key associated with the trusted platform module to produce a first certificate. A second asymmetric key pair is produced (308) in an application within the electronic device. The second public key is certified (310) with said first secret key to produce a second certificate. A message is signed (316) with the second secret key to provide a message signature in the first electronic device. The message and the message signature, software platform state information, the first certificate and the second certificate are sent (318) to a second electronic device.