Device Attestation via Off-Board Test Logic and Trusted Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing attestation processes expose proprietary details of devices under test to trust verifiers, making them vulnerable to malware and compromising device integrity.
Innovation Solution
A system where a trusted verifier performs attestation using a third-party software program that executes tests on a device under test without exposing its private data, utilizing a loader or attestation core and a test binary module to conduct tests while preserving confidentiality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If detailed information about the device's inner workings is provided for attestation, then the measurement precision of device integrity is improved, but the loss of information (proprietary data exposure) increases
Solution Approach 1:
The patent introduces a trusted verifier as an intermediary component that mediates between the device under test and the attestation authority. The trusted verifier executes test scripts and collects evidence about device integrity without requiring direct exposure of proprietary interfaces or confidential methodologies, thus enabling precise integrity measurement while protecting sensitive information through the intermediary layer
Solution Approach 2:
The attestation process is segmented into distinct components: test scripts, test managers, evidence collectors, and verifiers. This segmentation allows the system to separate the functions of testing, evidence collection, and verification, enabling detailed integrity assessment through multiple specialized modules without consolidating all proprietary information in a single exposed interface
2Reliability
If proprietary testing methodologies are shared with attestation equipment, then the reliability of malware detection is improved, but the device becomes more vulnerable to compromise
Solution Approach 1:
The trusted verifier acts as a secure intermediary that holds and executes proprietary testing methodologies without requiring them to be exposed to external attestation authorities. The intermediary maintains the confidentiality of detection algorithms while still enabling reliable malware detection through its controlled execution environment
Solution Approach 2:
Instead of sharing proprietary testing methodologies directly with external systems, the patent creates copies of test scripts and evidence collection mechanisms that run within the controlled environment of the trusted verifier. These copies enable external verification of detection results without exposing the original proprietary algorithms to potential compromise
3Measurement precision
If the device is tested with comprehensive test scripts, then the measurement precision of device state is improved, but the loss of time for attestation process increases
Solution Approach 1:
Test scripts are prepared and configured in advance before the actual attestation process begins. The test manager pre-loads test cases, evidence collection parameters, and verification criteria, so that during the actual attestation, the system can execute comprehensive tests without the overhead of real-time script generation or configuration, thus reducing attestation time while maintaining precision
Data Source
AI summary
Attestation of an electronic device provides assurances that the device is trustworthy and operating as intended or, at least, within acceptable parameters. Methods and systems are provided herein wherein a device under test (DUT) is subject to tests, the results of which are provided to a trust verifier (TV) to indicate whether the DUT passed or failed. To protect the integrity of the test from being discovered by malware, the test logic is developed “off board” and only machine code is provided to the DUT. Similarly, memory values and other data of the DUT are not revealed to the TV, which is only provided with test results.