Panda public auditing for shared data with efficient user revocation in the cloud
Download as PPTX, PDF1 like1,039 views
This document presents a novel public auditing mechanism for verifying the integrity of shared data in the cloud, with a focus on efficient user revocation. It allows the cloud to re-sign data blocks on behalf of existing users, mitigating the inefficiencies associated with user revocation while ensuring public verifiers can audit data integrity without full retrieval. The proposed system addresses security concerns by preventing unauthorized access and detailing architectural modules for user registration, file upload, verification, and administration.
Panda public auditing for shared data with efficient user revocation in the cloud
- 1. Panda: Public Auditing for Shared Data with Efficient User Revocation in the Cloud Boyang Wang, Baochun Li, Member, IEEE, and Hui Li, Member, IEEE
- 2. Abstract With data storage and sharing services in the cloud, users can easily modify and share data as a group. To ensure shared data integrity can be verified publicly, users in the group need to compute signatures on all the blocks in shared data. Different blocks in shared data are generally signed by different users due to data modifications performed by different users. For security reasons, once a user is revoked from the group, the blocks which were previously signed by this revoked user must be re-signed by an existing user. The straightforward method, which allows an existing user to download the corresponding part of shared data and re-sign it during user revocation, is inefficient due to the large size of shared data in the cloud. In this paper, we propose a novel public auditing mechanism for the integrity of shared data with efficient user revocation in mind. By utilizing the idea of proxy re-signatures, we allow the cloud to re-sign blocks on behalf of existing users during user revocation, so that existing users do not need to download and re-sign blocks by themselves. In addition, a public verifier is always able to audit the integrity of shared data without retrieving the entire data from the cloud, even if some part of shared data has been re-signed by the cloud. Moreover, our mechanism is able to support batch auditing by verifying multiple auditing tasks simultaneously. Experimental results show that our mechanism can significantly improve the efficiency of user revocation.
- 3. Existing System An existing system the file uploaded in cloud which not signed by user in each time of upload. So that integrity of shared data is not possible in existing system. However, since the cloud is not in the same trusted domain with each user in the group, outsourcing every user’s private key to the cloud would introduce significant security issue.
- 4. Disadvantages of Existing System For security reasons, when a user leaves the group or misbehaves, this user must be revoked from the group. As a result, this revoked user should no longer be able to access and modify shared data, and the signatures generated by this revoked user are no longer valid to the group. Since shared data is outsourced to the cloud and users no longer store it on local devices, a straightforward method to re-compute these signatures during user revocation.
- 5. Proposed System In our Proposed system may lie to verifiers about the incorrectness of shared data in order to save the reputation of its data services and avoid losing money on its data services. In addition, we also assume there is no collusion between the cloud and any user during the design of our mechanism. Generally, the incorrectness of share data under the above semi trusted model can be introduced by hardware/software failures or human errors happened in the cloud. Considering these factors, users do not fully trust the cloud with the integrity of shared data.
- 6. Advantages of Proposed System Blocking User account . Security question. Login with secret key in each time.
- 7. Architecture
- 8. Modules User Module: User module can divided into the following sub modules: Registration File Upload Download Re-upload Unblock Auditor Module: Auditor module can divided into the following sub modules: File Verification View File Admin Module: Admin module can divided into the following sub modules: View Files Block user
- 9. Module Description User Module Registration: In this module each user register his user details for using files. Only registered user can able to login in cloud server . File Upload: In this module user upload a block of files in the cloud with encryption by using his secret key. This ensure the files to be protected from unauthorized user.
- 10. Download: This module allows the user to download the file using his secret key to decrypt the downloaded data of blocked user and verify the data and re-upload the block of file into cloud server with encryption .This ensure the files to be protected from unauthorized user. Re-upload: This module allow the user to re-upload the downloaded files of blocked user into cloud server with resign the files (i.e) the files is uploaded with new signature like new secret with encryption to protected the data from unauthorized user. Unblock: This module allow the user to unblock his user account by answering his security question regarding to answer that provided by his at the time of registration. Once the answer is matched to the answer of registration time answer then only account will be unlocked.
- 11. Auditor Module File Verification: The public verifier is able to correctly check the integrity of shared data. The public verifier can audit the integrity of shared data without retrieving the entire data from the cloud, even if some blocks in shared data have been re-signed by the cloud. Files View: In this module public auditor view the all details of upload, download, blocked user, re-upload.
- 12. Admin Module View Files: In this module public auditor view the all details of upload, download, blocked user, re-upload. Block User: In this module admin block the misbehave user account to protect the integrity of shared data.
- 13. Minimum Hardware Configuration of the Proposed System Processor : Intel/AMD Hard Disk : 40 GB Monitor : 14’ Colour Monitor Mouse : Optical Mouse RAM : 512 MB
- 14. Software Configuration of the Proposed System Operating system : Windows 7 and above Coding Language : ASP.Net with C# Data Base : SQL Server 2008
- 15. References B. Wang, B. Li, and H. Li, “Public Auditing for Shared Data with Efficient User Revoation in the Cloud,” in the Proceedings of IEEE INFOCOM 2013, 2013, pp. 2904–2912. M. Armbrust, A. Fox, R. Griffith, A. D. Joseph, R. H. Katz, A. Konwinski, G. Lee, D. A. Patterson, A. Rabkin, I. Stoica, and M. Zaharia, “A View of Cloud Computing,” Communications of the ACM, vol. 53, no. 4, pp. 50–58, Apirl 2010. G. Ateniese, R. Burns, R. Curtmola, J. Herring, L. Kissner, Z. Peterson, and D. Song, “Provable Data Possession at Untrusted Stores,” in the Proceedings of ACM CCS 2007, 2007, pp. 598–610. H. Shacham and B. Waters, “Compact Proofs of Retrievability,” in the Proceedings of ASIACRYPT 2008. Springer-Verlag,2008,pp. 90–107. C. Wang, Q. Wang, K. Ren, and W. Lou, “Ensuring Data Storage Security in Cloud Computing,” in the Proceedings of ACM/IEEE IWQoS 2009, 2009, pp. 1–9.