Secure Data Sharing in Cloud With Distributed Accountability
Secure Data Sharing in Cloud With Distributed Accountability
Secure Data Sharing in Cloud With Distributed Accountability
20 www.erpublication.org
Secure Data Sharing In Cloud with Distributed Accountability
environments, are not suitable, due to the following features We conduct experiments on a real cloud testbed. The results
characterizing cloud environments. demonstrate the efficiency, scalability, and granularity of our
approach. We also provide a detailed security analysis and
A. Problems on existing system discuss the reliability and strength of our architecture.
First, data handling can be outsourced by the direct cloud III. MODULES
service provider (CSP) to other entities in the cloud and theses Following are the important module used in our project,
entities can also delegate the tasks to others, and so on. Module 1: DATA OWNER
Second, entities are allowed to join and leave the cloud in a Module 2: JAR CREATION
flexible manner. As a result, data handling in the cloud goes Module 3: CLOUD SERVICE PROVIDER
through a complex and dynamic hierarchical service chain
which does not exist in conventional environments.
A. DATA OWNER
B. Proposed System
In this module, the data owner can upload their data in the
We propose a novel approach, namely Cloud Information cloud server. The new user has to register with the service
Accountability (CIA) framework, based on the notion of provider by creating new account because of that security is
information accountability. Unlike privacy protection maintained and he can upload or store his files. Data owner
technologies which are built on the hide-it-or-lose-it encrypt data for security purpose.
perspective, information accountability focuses on keeping The Data owner can have capable of manipulating the
the data usage transparent and tractable. Our proposed CIA encrypted data file. And the data owner can set the access
framework provides end-to end accountability in a highly privilege to the encrypted data file. To allay users concerns,
distributed fashion. One of the main innovative features of the it is essential to provide an effective way for users to monitor
CIA framework lies in its ability of maintaining lightweight the usage of their data in the cloud. For example, users need to
and powerful accountability that combines aspects of access be able to ensure that their data are handled according to the
control, usage control and authentication. By means of the service level agreements made at the time they sign on for
CIA, data owners can track not only whether or not the services in the cloud.
service-level agreements are being honored, but also enforce
B. JAR CREATION
access and usage control rules as needed. Associated with the
accountability feature, we also develop two distinct modes for
auditing: push mode and pull mode. The push mode refers to In this module Jar file is created for file uploading.The user
logs being periodically sent to the data owner or stakeholder should have the same jar file to download the file. This way
while the pull mode refers to an alternative approach whereby the data is going to be secured. The logging should be
the user (or another authorized party) can retrieve the logs as decentralized in order to adapt to the dynamic nature of the
needed. cloud. More specifically, log files should be tightly bounded
with the corresponding data being controlled, and require
minimal infrastructural support from any server. Every access
Our main contributions are as follows: to the users data should be correctly and automatically
logged. This requires integrated techniques to authenticate the
We propose a novel automatic and enforceable logging entity who accesses the data, verify, and record the actual
mechanism in the cloud. Our proposed architecture is operations on the data as well as the time that the data have
platform independent and highly decentralized, in that it does been accessed. Log files should be reliable and tamper proof
not require any dedicated authentication or storage system in to avoid illegal insertion, deletion, and modification by
place. malicious parties. Recovery mechanisms are also desirable to
restore damaged log files caused by technical problems. The
proposed technique should not intrusively monitor data
recipients systems, nor it should introduce heavy
communication and computation overhead, which otherwise
will hinder its feasibility and adoption in practice.
C. CLOUD SERVICE PROVIDER
21 www.erpublication.org
International Journal of Engineering and Technical Research (IJETR)
ISSN: 2321-0869, Volume-2, Issue-11, November 2014
knowledge of our CIA architecture. We first assume that the
JVM is not corrupted, followed by a discussion on how to
ensure that this assumption holds true.
A. Attacks on JAR files
V. CONCLUSION
In this paper we see innovative approaches for
automatically logging any access to the data in the cloud
together with an auditing mechanism is proposed. The
approach allows the data owner to not only audit his content
but also enforce strong back-end protection if needed.
Moreover, one of the main features of our work is that it
enables the data owner to audit even those copies of its data
that were made without his knowledge.
In the future, planned to refine our approach to
verify the integrity and the authentication of JARs
ACKNOWLEDGMENT
Good Teachers are worth more than thousand books,
we have them in Our Department.
REFERENCES
[1] SmithaSundareswaran, Anna C. Squicciarini and Dan Lin,
"EnsuringDistributed Accountability for Data Sharing in the Cloud,",
IEEETransaction on dependable a secure computing, VOL. 9, NO. 4, pg
556-568, 2012.
[2]Hsio Ying Lin,Tzeng.W.G, A Secure Erasure Code-Based Cloud
Storage System with Secure Data Forwarding,IEEE transactions on
parallel and distributed systems,2012.
[3] Yan Zhu, Hongxin Hu, Gail JoonAhn, Mengyang Yu, Cooperative
Provable Data Possession for IntegrityVerification in MultiCloud
Storage , IEEE transactions on parallel and distributed systems,2012.
[4]http://www.a4cloud.eu/cloud-accountability
[5]http://www.hpl.hp.com/techreports/2011/HPL-2011-38.pdf.
22 www.erpublication.org