Public integrity verification for data sharing in cloud with asynchronous revocation

Cloud data sharing service, which allows a group of people to access and modify the shared data, is one of the most popular and efficient working styles in enterprises. Recently, there is an uprising trend that enterprises tend to move their IT service from local to cloud to ease the management and...

Full description

Bibliographic Details
Main Authors: Wei Song, Yu Wu, Yihui Cui, Qilie Liu, Yuan Shen, Zicheng Qiu, Jianjun Yao, Zhiyong Peng
Format: Article
Language:English
Published: KeAi Communications Co., Ltd. 2022-02-01
Series:Digital Communications and Networks
Subjects:
Online Access:http://www.sciencedirect.com/science/article/pii/S2352864821000109
_version_ 1818329820945186816
author Wei Song
Yu Wu
Yihui Cui
Qilie Liu
Yuan Shen
Zicheng Qiu
Jianjun Yao
Zhiyong Peng
author_facet Wei Song
Yu Wu
Yihui Cui
Qilie Liu
Yuan Shen
Zicheng Qiu
Jianjun Yao
Zhiyong Peng
author_sort Wei Song
collection DOAJ
description Cloud data sharing service, which allows a group of people to access and modify the shared data, is one of the most popular and efficient working styles in enterprises. Recently, there is an uprising trend that enterprises tend to move their IT service from local to cloud to ease the management and reduce the cost. Under the new cloud environment, the cloud users require the data integrity verification to inspect the data service at the cloud side. Several recent studies have focused on this application scenario. In these studies, each user within a group is required to sign a data block created or modified by him. While a user is revoked, all the data previously signed by him should be resigned. In the existing research, the resigning process is dependent on the revoked user. However, cloud users are autonomous. They may exit the system at any time without notifying the system admin and even are revoked due to misbehaviors. As the developers in the cloud-based software development platform, they are voluntary and not strictly controlled by the system. Due to this feature, cloud users may not always follow the cloud service protocol. They may not participate in generating the resigning key and may even expose their secret keys after being revoked. If the signature is not resigned in time, the subsequent verification will be affected. And if the secret key is exposed, the shared data will be maliciously modified by the attacker who grasps the key. Therefore, forcing a revoked user to participate in the revocation process will lead to efficiency and security problems. As a result, designing a practical and efficient integrity verification scheme that supports this scenario is highly desirable. In this paper, we identify this challenging problem as the asynchronous revocation, in which the revocation operations (i.e., re-signing key generation and resigning process) and the user's revocation are asynchronous. All the revocation operations must be able to be performed without the participation of the revoked user. Even more ambitiously, the revocation process should not rely on any special entity, such as the data owner or a trusted agency. To address this problem, we propose a novel public data integrity verification mechanism in which the data blocks signed by the revoked user will be resigned by another valid user. From the perspectives of security and practicality, the revoked user does not participate in the resigning process and the re-signing key generation. Our scheme allows anyone in the cloud computing system to act as the verifier to publicly and efficiently verify the integrity of the shared data using Homomorphic Verifiable Tags (HVTs). Moreover, the proposed scheme resists the collusion attack between the cloud server and the malicious revoked users. The numerical analysis and experimental results further validate the high efficiency and scalability of the proposed scheme. The experimental results manifest that re-signing 10,000 data blocks only takes 3.815 ​s and a user can finish the verification in 300 ​ms with a 99% error detection probability.
first_indexed 2024-12-13T12:54:08Z
format Article
id doaj.art-5e0b98d0ef104336bc67156297433fff
institution Directory Open Access Journal
issn 2352-8648
language English
last_indexed 2024-12-13T12:54:08Z
publishDate 2022-02-01
publisher KeAi Communications Co., Ltd.
record_format Article
series Digital Communications and Networks
spelling doaj.art-5e0b98d0ef104336bc67156297433fff2022-12-21T23:45:15ZengKeAi Communications Co., Ltd.Digital Communications and Networks2352-86482022-02-01813343Public integrity verification for data sharing in cloud with asynchronous revocationWei Song0Yu Wu1Yihui Cui2Qilie Liu3Yuan Shen4Zicheng Qiu5Jianjun Yao6Zhiyong Peng7School of Computer Science, Wuhan University, Wuhan, 430074, ChinaSchool of Computer Science, Wuhan University, Wuhan, 430074, ChinaSchool of Software Engineering, Chongqing University of Posts and Telecommunications, Chongqing, 400054, ChinaSchool of Communication and Information Engineering, Chongqing University of Posts and Telecommunications, Chongqing, 400054, China; Corresponding author.School of Computer Science, Wuhan University, Wuhan, 430074, ChinaCollege of Information Engineering, Tarim University, Alar City, Xinjiang, 843300, ChinaCollege of Information Engineering, Tarim University, Alar City, Xinjiang, 843300, ChinaSchool of Computer Science, Wuhan University, Wuhan, 430074, ChinaCloud data sharing service, which allows a group of people to access and modify the shared data, is one of the most popular and efficient working styles in enterprises. Recently, there is an uprising trend that enterprises tend to move their IT service from local to cloud to ease the management and reduce the cost. Under the new cloud environment, the cloud users require the data integrity verification to inspect the data service at the cloud side. Several recent studies have focused on this application scenario. In these studies, each user within a group is required to sign a data block created or modified by him. While a user is revoked, all the data previously signed by him should be resigned. In the existing research, the resigning process is dependent on the revoked user. However, cloud users are autonomous. They may exit the system at any time without notifying the system admin and even are revoked due to misbehaviors. As the developers in the cloud-based software development platform, they are voluntary and not strictly controlled by the system. Due to this feature, cloud users may not always follow the cloud service protocol. They may not participate in generating the resigning key and may even expose their secret keys after being revoked. If the signature is not resigned in time, the subsequent verification will be affected. And if the secret key is exposed, the shared data will be maliciously modified by the attacker who grasps the key. Therefore, forcing a revoked user to participate in the revocation process will lead to efficiency and security problems. As a result, designing a practical and efficient integrity verification scheme that supports this scenario is highly desirable. In this paper, we identify this challenging problem as the asynchronous revocation, in which the revocation operations (i.e., re-signing key generation and resigning process) and the user's revocation are asynchronous. All the revocation operations must be able to be performed without the participation of the revoked user. Even more ambitiously, the revocation process should not rely on any special entity, such as the data owner or a trusted agency. To address this problem, we propose a novel public data integrity verification mechanism in which the data blocks signed by the revoked user will be resigned by another valid user. From the perspectives of security and practicality, the revoked user does not participate in the resigning process and the re-signing key generation. Our scheme allows anyone in the cloud computing system to act as the verifier to publicly and efficiently verify the integrity of the shared data using Homomorphic Verifiable Tags (HVTs). Moreover, the proposed scheme resists the collusion attack between the cloud server and the malicious revoked users. The numerical analysis and experimental results further validate the high efficiency and scalability of the proposed scheme. The experimental results manifest that re-signing 10,000 data blocks only takes 3.815 ​s and a user can finish the verification in 300 ​ms with a 99% error detection probability.http://www.sciencedirect.com/science/article/pii/S2352864821000109Cloud storageIntegrity verificationAsynchronous revocation
spellingShingle Wei Song
Yu Wu
Yihui Cui
Qilie Liu
Yuan Shen
Zicheng Qiu
Jianjun Yao
Zhiyong Peng
Public integrity verification for data sharing in cloud with asynchronous revocation
Digital Communications and Networks
Cloud storage
Integrity verification
Asynchronous revocation
title Public integrity verification for data sharing in cloud with asynchronous revocation
title_full Public integrity verification for data sharing in cloud with asynchronous revocation
title_fullStr Public integrity verification for data sharing in cloud with asynchronous revocation
title_full_unstemmed Public integrity verification for data sharing in cloud with asynchronous revocation
title_short Public integrity verification for data sharing in cloud with asynchronous revocation
title_sort public integrity verification for data sharing in cloud with asynchronous revocation
topic Cloud storage
Integrity verification
Asynchronous revocation
url http://www.sciencedirect.com/science/article/pii/S2352864821000109
work_keys_str_mv AT weisong publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT yuwu publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT yihuicui publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT qilieliu publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT yuanshen publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT zichengqiu publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT jianjunyao publicintegrityverificationfordatasharingincloudwithasynchronousrevocation
AT zhiyongpeng publicintegrityverificationfordatasharingincloudwithasynchronousrevocation