Leveraging Intel SGX to enable trusted and privacy preserving membership service in distributed ledgers Online publication date: Mon, 06-Sep-2021
by Xueping Liang; Sachin Shetty; Deepak K. Tosh; Peter Foytik; Lingchen Zhang
International Journal of Information and Computer Security (IJICS), Vol. 16, No. 1/2, 2021
Abstract: Distributed ledger technology (DLT) provides decentralised services by removing the need of trust among distributed nodes in the distributed system. Transactions across the network are visible to all participants. However, some transactions may contain sensitive information such as business contracts or even personal health records. To protect user privacy, the architecture of distributed multi-channel ledger with membership service as a critical component can be adopted. The proposed multi-channel membership service architecture combines two promising technologies, distributed ledger and Intel Software Guard Extensions (SGX). With SGX remote attestation and isolated execution, each node is enrolled as a trusted entity to the channels, which separate different applications and provide better flexibility. We propose security properties for membership service in distributed ledger and illustrate how SGX help to achieve these properties in each phase. Security analysis and evaluation show that the proposed architecture could enhance the privacy preservation and capabilities against attacks.
Online publication date: Mon, 06-Sep-2021
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Information and Computer Security (IJICS):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org