You are on page 1of 21

Data Integrity Proofs in Cloud Storage

Contents

Introduction. Problem Statement. Scope Literature survey System Analysis System Architecture Implementation System Design Conclusion. References.

4/5/2013

Introduction:

Cloud computing has been envisioned as the de-facto solution to the rising storage costs of IT Enterprises. With the high costs of data storage devices as well as the rapid rate at which data is being generated it proves costly for enterprises or individual users to frequently update their hardware. Apart from reduction in storage costs data outsourcing to the cloud also helps in reducing the maintenance. Cloud storage moves the users data to large data centers, which are remotely located, on which user does not have any control. However, this unique feature of the cloud poses many new security challenges which need to be clearly understood and resolved. We provide a scheme which gives a proof of data integrity in the cloud which the customer can employ to check the correctness of his data in the cloud. This proof can be agreed upon by both the cloud and the customer and can be incorporated in the Service level agreement (SLA).

Scope:

One of the important concerns that need to be addressed is to assure the customer of the integrity i.e. correctness of his data in the cloud. As the data is physically not accessible to the user the cloud should provide a way for the user to check if the integrity of his data is maintained or is compromised. In this paper we provide a scheme which gives a proof of data integrity in the cloud which the customer can employ to check the correctness of his data in the cloud. This proof can be agreed upon by both the cloud and the customer and can be incorporated in the Service level agreement (SLA). It is important to note that our proof of data integrity protocol just checks the integrity of data i.e. if the data has been illegally modified or deleted.

Literature survey:
Literature survey is the most important step in software development process. Before developing the tool it is necessary to determine the time factor, economy and company strength. Once these things are satisfied, then next steps is to determine which operating system and language can be used for developing the tool. Once the programmers start building the tool the programmers need lot of external support. This support can be obtained from senior programmers, from book or from websites. Before building the system the above consideration are taken into account for developing the proposed system.

Cloud Computing Outline Survey:


1.

CLOUD COMPUTING

Cloud computing provides unlimited infrastructure to store and execute customer data and program. As customers you do not need to own the infrastructure, they are merely accessing or renting; they can forego capital expenditure and consume resources as a service, paying instead for what they use.

More outline survey


Where does the data gets hosted???? OR In which country does it gets stored???? 2. DATA LOCATION
Data should be stored and processed only in specific jurisdictions as define by user. Provider should also make a contractual commitment to obey local privacy requirements on behalf of their customers, Data-centered policies that are generated when a user provides personal or sensitive information, that travels with that information throughout its lifetime to ensure that the information is used only in accordance with the policy.

Network Security:
1.

2. 3. 4. 5. 6.

Denial of Service: where servers and networks are brought down by a huge amount of network traffic and users are denied the access to a certain Internet based service. Like DNS Hacking: Routing Table Poisoning, XDoS attacks QoS Violation : through congestion, delaying or dropping packets, or through resource hacking. Man in the Middle Attack: To overcome it always use SSL IP Spoofing: Spoofing is the creation of TCP/IP packets using somebody else's IP address. Solution: Infrastructure will not permit an instance to send traffic with a source IP or MAC address other than its own.

Benefits of cloud storage

1. 2. 3. 4. 5.

Minimized Capital Expenditure Location and Device Independence Utilization and efficiency improvement Very high Scalability High Computing power

Existing System:
FACTS: o Maintaining the storages can be a difficult task. Transmitting the file across the network to the client can consume heavy bandwidths. o The problem is further complicated by the fact that the owner of the data may be a small device, like a PDA (personal digital assist) or a mobile phone, which have limited CPU power, battery power and communication bandwidth. DISADVANTAGES: The main drawback of this scheme is the high resource costs it requires for the implementation. Also computing hash value for even a moderately large data files can be computationally burdensome for some clients (PDAs, mobile phones, etc). Data encryption is large so the disadvantage is small users with limited computational power (PDAs, mobile phones etc.).

Proposed system:
FACTS: Correctness of data in the cloud. As the data is physically not accessible to the user the cloud should provide a way for the user to check if the integrity of his data is maintained or is compromised. In this paper we provide a scheme which gives a proof of data integrity in the cloud which the customer can employ to check the correctness of his data in the cloud. ADVANTAGES: Apart from reduction in storage costs data outsourcing to the cloud also helps in reducing the maintenance. Avoiding local storage of data. By reducing the costs of storage, maintenance and personnel. It reduces the chance of losing data by hardware failures. Not cheating the owner.

Existing system:

Proposed System :

Implementation:
ALGORITHM: Meta-Data Generation: Let the verifier V wishes to the store the file F with the archive. File F n file blocks. Initially preprocess the file and create metadata to be appended to the file. Let each n data blocks have m bits in them. Each of the Meta data from the data blocks mi is encrypted by using a suitable algorithm to give a new modified Meta data Mi. This process is showed by simple XOR operation. All the Meta data bit blocks procedure concatenated together. Concatenated Meta data appended to the file F at the cloud . The file F along with the appended Meta data e F is archived with the cloud.

Modules:
Simply Archives:
This module tries to obtain and verify a proof that the data that is stored by a user at remote data storage in the cloud (called cloud storage archives or simply archives) is not modified by the archive and thereby the integrity of the data is assured.

Cloud Storage:
Data outsourcing to cloud storage servers is raising trend among many firms and users owing to its economic advantages. This essentially means that the owner (client) of the data moves its data to a third party cloud storage server which is supposed to - presumably for a fee - faithfully store the data with it and provide it back to the owner whenever required.

More modules
Sentinels:
In this scheme, unlike in the key-hash approach scheme, only a single key can be used irrespective of the size of the file or the number of files whose retrievability it wants to verify. If the prover has modified or deleted a substantial portion of F, then with high probability it will also have suppressed a number of sentinels.

Verification Phase:
At the time of verification the verifier uses this Meta data to verify the integrity of the data. It is important to note that our proof of data integrity protocol just checks the integrity of data i.e. if the data has been illegally modified or deleted. It does not prevent the archive from modifying the data.

Login

System Design:

TPA

Admin

Owner

Data Flow Diagram:

File Verification

View & Download Owner Files

Exists Create Account

View Owner Details Direct Verification Download Verification

File Upload

Warning Mail To Owner

Cryptogrphic key Sent to Mail

key request to owner


Download Verification

Verifiction Status

Direct Verification

Block

Download Request Status

Check

Process Pending

File Not Modify

Allow
File Download

File Not Modify

File Modify File Download with key

Verify & Upload Downlod File

File Download with crypto key

download modify File with key

Warning from Admin

End

Create Account

Use case diagram:


Login

File Upload

TPA

File Verify Owner Cryptography key Request

Admin

File Download

File Details

Owner Details

Registration ID OwnerID Password Gender Mobile EMail Date

File Archive FileID FileName FileSize FilePath FileOwner MetaData KeyRequest DownloadStatus ModifyStatus VerifyStatus metadatagenration() fileupload()

Class Diagram:

Loginidgenration() CreateAccount()

File Archive Modify FileID FileName FileSize FilePath FileOwner MetaData KeyRequest VerifyStatus

comparemetadata() fileupload()

Conclusion:

In this paper we have worked to facilitate the client in getting a proof of integrity of the data which he wishes to store in the cloud storage servers with bare minimum costs and efforts. Our scheme was developed to reduce the computational and storage overhead of the client as well as to minimize the computational overhead of the cloud storage server. We also minimized the size of the proof of data integrity so as to reduce the network bandwidth consumption. Many of the schemes proposed earlier require the archive to perform tasks that need a lot of computational power to generate the proof of data integrity. But in our scheme the archive just need to fetch and send few bits of data to the client.

REFERENCE:
1.Sravan Kumar, Ashutosh Saxena, Data Integrity Proofs in Cloud Storage, IEEE Conference 2011. 2.Google App Engine, Online at http://code.google.com/appengine/. 3. Microsoft Azure, http://www.microsoft.com/azure/.

4.Amazon Web Services (AWS), Online at http://aws. amazon.com.