10-08-2012, 04:31 PM
Storing data
Storing data .doc (Size: 135.5 KB / Downloads: 63)
INTRODUCTION
Storing data in the cloud has become a trend. An increasing number of clients store their important data in remote servers in the cloud, without leaving a copy in their local computers. Sometimes the data stored in the cloud is so important that the clients must ensure it is not lost or corrupted. While it is easy to check data integrity after completely downloading the data to be checked, downloading large amounts of data just for checking data integrity is a waste of communication bandwidth. Hence, a lot of works have been done on designing remote data integrity checking protocols, which allow data integrity to be checked without completely downloading the data.
Remote data integrity checking is first introduced in which it is independently proposed RSA-based methods for solving this problem. After that Shah et al. propose a remote storage auditing method based on precompiled challenge-response pairs. Recently, many works focus on providing three advanced features for remote data integrity checking protocols: data dynamics, public verifiability and privacy against verifiers. The protocols it support data dynamics at the block level, includes block insertion, block modification, and block deletion. The protocol of supports data appends operation. In addition, it can be easily adapted to support data dynamics.
We propose a remote data integrity checking protocol for cloud storage, which can be viewed as an adaptation of Sebe´ et al.’s protocol. The proposed protocol inherits the support of data dynamics from, and supports public verifiability and privacy against third-party verifiers, while at the same time it doesn’t need to use a third-party auditor. We give a security analysis of the proposed protocol, which shows that it is secure against the untreated server and private against third-party verifiers.
We consider a cloud storage system in which there are a client and an untrusted server. The client stores her data in the server without keeping a local copy. Hence, it is of critical importance that the client should be able to verify the integrity of the data stored in the remote untrusted server. If the server modifies any part of the client’s data, the client should be able to detect it; furthermore, any third-party verifier should also be able to detect it. In case a thirdparty verifier verifies the integrity of the client’s data, the data should be kept private against the third-party verifier.
The proposed protocol has functions SetUp, TagGen, Challenge, GenProof, and CheckProof, as well as functions for data dynamics. , we first show that the proposed protocol is correct in the sense that the server can pass the verification of data integrity as long as both the client and the server are honest. Then we show that the protocol is secure against the untrusted server. These two theorems together guarantee that, assuming the client is honest, if and only if the server has access to the complete and uncorrupted data, it can pass the verification process successfully.
Finally, we show that the proposed protocol is private against third-party verifiers. The proposed protocol supports data dynamics at the block level in the same way it is suitable for providing integrity protection of customers’ important data. The proposed protocol supports data insertion, modification, and deletion at the block level, and also supports public verifiability.
.PROBLEM SPECIFICATION
PROBLEM STATEMENT
In this, it mainly deals with data integrity problem in accessing the information from the remote system. Here when we use previous protocols the data integrity is not provided, and the confidentiality is not provided. Due to the reason the speed of accessing is decreased. The privacy against the servers is not determined. Here the third party verifiers are used to check the integrity. While it is easy to check data integrity after completely downloading the data to be checked, downloading large amounts of data just for checking data integrity is a waste of communication bandwidth. The proposed protocol inherits the support of data dynamics from, and supports public verifiability and privacy against third-party verifiers, while at the same time it doesn’t need to use a third-party auditor. We give a security analysis of the proposed protocol, which shows that it is secure against the untreated server and private against third-party verifiers.
PROBLEM DESCRIPTION
In this, we mainly deals with remote data integrity checking in the remote systems. Storing data in the cloud has become a trend. An increasing number of clients store their important data in remote servers in the cloud, without leaving a copy in their local computers. Sometimes the data stored in the cloud is so important that the clients must ensure it is not lost or corrupted. While it is easy to check data integrity after completely downloading the data to be checked, downloading large amounts of data just for checking data integrity is a waste of communication bandwidth. Hence, a lot of works have been done on designing remote data integrity checking protocols, which allow data integrity to be checked without completely downloading the data. Remote data integrity checking is first introduced in which independently propose RSA-based methods for solving this problem. Recently, many works focus on providing three advanced features for remote data integrity checking protocols: data dynamics public verifiability and privacy against verifiers. The protocols in support data dynamics at the block level, including block insertion, block modification, and block deletion.
EXISTING SYSTEM
Existing system utilizes Third Party Auditors(TPA). The third party auditor (TPA) is the one, who has expertise and capabilities that cloud users do not have and is trusted to assess the cloud storage service security on behalf of the user upon request. TPA scheme is the first to support scalable and efficient public auditing in the Cloud Computing. They may also dynamically interact with the CS(Cloud Server) to access and update their stored data for various application purposes to achieve data dynamics.
DELIMITATIONS OF EXISTING SYSTEM
1) Existing protocols can support either Data dynamics or Public verifiability. These protocols utilize third party auditors to support the activities which are expensive.
2) These protocols have the possibility of leaking the private information, which is not recommended, to third party auditors.
3) Modifications cannot be done while transmission.
4) We can’t able to predict the data.
5) Threats will increase in internet.
6) Confidentiality is not provided.
PROPOSED SYSTEM
Existing system fails to predict the data consistency. So we introduce a new concept, to monitor the packets by verifier. Verifier checks the blocks of a data randomly by sending a challenge request and verifying challenge response from that packet after verifier is authorize using its public key. If the challenge and challenge response is matched then the block is normal. If challenge response is differed from the expected challenge response then the block is affected. Verifier will give alert to the entire user who is all using the cloud server. By using in this method we can access remote system without any losses or malicious. The Data stored in a Cloud Server is split into blocks. The Integrity of the blocks are verified randomly by the Third Party Verifier. Verifier will give its public key then the Challenge to a particular Block. The block will respond with Challenge Response. The Verifier verifies the CR, if it is Genuine then the data is safe condition; if not data Access is blocked