Device Attestation Binding for Trusted Credential Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The diversity of wallet providers and device makers complicates the implementation of a unified and trusted security control for devices storing digital credentials, such as identity documents and bank credentials, necessitating a solution for verifying devices before issuing digital credentials.
Innovation Solution
A method involving device attestation through a verifier entity, where the device receives and signs binding data, transmits it to an issuer entity, and stores a signed device attestation, enabling verification of device information and integrity, using Verifiable Credentials (VC) and Verifiable Presentations (VP) for interoperability and trust.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a unified security control is implemented across diverse wallet providers and device makers, then trust and reliability are improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The verification system is segmented into distinct components: device information collection, binding data generation, attestation creation, and verification. Each component can be independently implemented and verified, reducing overall system complexity while maintaining reliability.
Solution Approach 2:
Device attestation is performed in advance before digital credentials are issued. The device information is collected, bound to cryptographic data, and verified beforehand, creating a trusted foundation that simplifies subsequent credential issuance processes.
2Object-affected harmful factors
If device verification with multiple security checks is performed, then fraud prevention and security are improved, but processing time and operational complexity increase
Solution Approach 1:
Security verification is performed in advance during the device attestation phase, before credential issuance. This preliminary security check prevents fraud early in the process, avoiding time-consuming verification steps later when credentials are already in use.
Solution Approach 2:
Traditional manual security verification processes are replaced with automated cryptographic verification. The verifier entity can automatically verify device information against the binding data using cryptographic algorithms, significantly reducing verification time while maintaining high security standards.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A method of verification of a device (101) by a verifier entity in a communications network, the method comprising: - receiving (221) by the device, from an issuer entity (130), information derived from device information descriptive of the device or of a component of the device; - determining (222) binding data, by the device, the binding data comprising the information derived from the device information and being signed by the device; - transmitting (223) the binding data to the issuer entity; - receiving (230), by the device and from the issuer entity, a device attestation (300) comprising the device information, the binding data and a signature of the issuer entity; - storing (231) the device attestation in the device; wherein, upon reception of a verification request from a verifier entity, the device presents the device attestation to the verifier entity.