Author
Listed:
- Yuan Tian
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China
These authors contributed equally to this work.)
- Xuan Zhou
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China
These authors contributed equally to this work.)
- Tanping Zhou
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China)
- Weidong Zhong
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China)
- Ruifeng Li
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China)
- Xiaoyuan Yang
(Chinese People’s Armed Police Force Engineering University, Xi’an 710086, China)
Abstract
With the surge in cloud storage popularity, more individuals are choosing to store large amounts of data on remote cloud service providers (CSPs) to save local storage resources. However, users’ primary worries revolve around maintaining data integrity and authenticity. Consequently, several cloud auditing methods have emerged to address these concerns. Many of these approaches rely on traditional public-key cryptography systems or are grounded in identity-based cryptography systems or certificateless cryptography systems. However, they are vulnerable to the increased costs linked with certificate management, key escrow, or the significant expenses of establishing a secure channel, respectively. To counter these limitations, Li et al. introduced a certificate-based cloud auditing protocol (LZ22), notable for its minimal tag generation overhead. Nonetheless, this protocol exhibits certain security vulnerabilities. In this paper, we devise a counterfeiting technique that allows the CSP to produce a counterfeit data block with an identical tag to the original one. Our counterfeiting method boasts a 100% success rate ∀ data block and operates with exceptional efficiency. The counterfeiting process for a single block of 10 kB, 50 kB, and 100 kB takes a maximum of 0.08 s, 0.51 s, and 1.04 s, respectively. By substituting the exponential component of homomorphic verifiable tags (HVTs) with non-public random elements, we formulate a secure certificate-based cloud auditing protocol. In comparison to the LZ22 protocol, the average tag generation overhead of our proposed protocol is reduced by 6.80%, 13.78%, and 8.66% for data sizes of 10 kB, 50 kB, and 100 kB, respectively. However, the auditing overhead of our proposed protocol shows an increase. The average overhead rises by 3.05%, 0.17%, and 0.45% over the LZ22 protocol’s overhead for data sizes of 10 kB, 50 kB, and 100 kB, correspondingly.
Suggested Citation
Yuan Tian & Xuan Zhou & Tanping Zhou & Weidong Zhong & Ruifeng Li & Xiaoyuan Yang, 2024.
"A Secure Certificate-Based Data Integrity Auditing Protocol with Cloud Service Providers,"
Mathematics, MDPI, vol. 12(13), pages 1-26, June.
Handle:
RePEc:gam:jmathe:v:12:y:2024:i:13:p:1964-:d:1421450
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:gam:jmathe:v:12:y:2024:i:13:p:1964-:d:1421450. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: MDPI Indexing Manager (email available below). General contact details of provider: https://www.mdpi.com .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.