1. DATA DYNAMICS AND PUBLIC VERIFIABILITY CHECKING WITHOUT THIRD PARTY AUDITOR GUIDED BY PROJECT MEMBERS: Ms. V.JAYANTHI M.E Assistant Professor V.KARTHIKEYAN S.RAMAKRISHNAN S.SELVAKUMAR R.VENKATESAN

2. OBJECTIVE  To provide security between the client and server by using TPV(Third party verifier)in cloud  The client can store data without keeping any local copy in cloud server

3. INTRODUCTION  The Existing system can support Data dynamics and public verifiability with the help of a third party auditor.  The proposed system supports public verifiability without help of a third party auditor.  The proposed system does not leak any private information to third party verifiers.

4. EXISTING SYSTEM  The clients store the data in server  That server is trustworthy and after the third party auditor can audit the client files.  The possibility to the third party auditor can stolen the client files.

5. LITERATURE SURVEY C. Wang, Q. Wang, K. Ren, and W. Lou, “Privacy-preserving public auditing for data storage security in cloud computing,” in InfoCom2010, IEEE, March 2010.  External audit party to check the integrity of outsourced data when needed. To securely introduce an effective third party auditor(TPA).

6. C. Erway, A. K¨upc¸ ¨u, C. Papamanthou, and R. Tamassia, “Dynamic provable data possession,” in CCS’09, pp. 213–222, ACM, 2009.  In the provable data possession(PDP) model, the client preprocesses the data and then sends it to an untrusted server for storage.

7. PROPOSED SYSTEM  The client stores their data in the server without keeping a local copy  The proposed system inherits the support of data dynamics, and supports public verifiability and privacy against third-party verifiers.  Doesn’t need to use a third-party auditor.

8. Processor Type : Pentium IV Speed : 2.4 GHZ RAM : 256 MB Hard disk : 20 GB Keyboard : 101/102 Standard Keys Mouse: Scroll Mouse

9. Operating System : Windows XP Programming Package : Visual Studio 2008 Coding Language: ASP.Net with C# Database: MS-SQL Server 2005

10. EXPERIMENTAL SETUP

11. MODULES There are four modules that is Data Dynamics public verifiability Metadata Generation Privacy against Third Party Verifiers

12. Data dynamics means after clients store their data at the remote server, they can dynamically update their data at later times. Block Insertion The Server can insert anything on the client’s file. Block Deletion The Server can delete anything on the client’s file. Block Modification The Server can modify anything on the client’s file. DATA DYNAMICS

13. PUBLIC VERIFIABILITY  Each and every time the secret key sent to the client’s email and can perform the integrity checking operation.  Client doesn’t ask any secret key from third party.

14. METADATA KEY GENERATION  Initially preprocess the file and create metadata to be appended to the file.  Each of the Meta data from the data blocks m i is encrypted by using a RSA algorithm to give a new modified Meta data M i.

15. PRIVACY AGAINST THIRD PARTY VERIFIERS  If the server modifies any part of the client’s data, the client should be able to detect it.  In case a third party verifier verifies the integrity of the client’s data, the data should be kept private against the third party verifier.

16. CONCLUSION  Using the Third party verifier our stored data are secure the server can not able to view without the client permission.  If the server modifies the data the alert message can be given by the third party verifier to the client mail.

17. FUTURE ENHANCEMENT  Notifies what modification is done by server in the client file.  The user can view their file details such as upload files, download files.  Modification files can viewed through accessing with the help of mobile.

18. SCREEN SHOTS

21. THANK YOU