Balancing Performance, Accuracy, and Precision for
Secure Cloud Transactions
ABSTRACT:
In distributed
transactional database systems deployed over cloud servers, entities cooperate
to form proofs of authorizations that are justified by collections of certified
credentials. These proofs and credentials may be evaluated and collected over
extended time periods under the risk of having the underlying authorization
policies or the user credentials being in inconsistent states. It therefore
becomes possible for policy-based authorization systems to make unsafe
decisions that might threaten sensitive resources. In this paper, we highlight
the criticality of the problem. We then define the notion of trusted
transactions when dealing with proofs of authorization. Accordingly, we propose
several increasingly stringent levels of policy consistency constraints, and
present different enforcement approaches to guarantee the trustworthiness of
transactions executing on cloud servers. We propose a Two-Phase Validation
Commit protocol as a solution, which is a modified version of the basic
Two-Phase Validation Commit protocols. We finally analyze the different
approaches presented using both analytical evaluation of the overheads and
simulations to guide the decision makers to which approach to use.
EXISTING SYSTEM:
To provide
scalability and elasticity, cloud services oftenmake heavy use of replication
to ensure consistent performance and
availability. As a result, many cloud services rely on the notion of eventual
consistency when propagating data throughout the system. This consistency model
is a variant of weak consistency that allows data to be inconsistent among some
replicas during the update process, but ensures that updates will eventually be
propagated to all replicas.
DISADVANTAGES
OF EXISTING SYSTEM:
Ø Consistency problems can arise as transactional
database systems are deployed in cloud environments and use policy-based
authorization systems to protect sensitive resources.
Ø The system may suffer from policy inconsistencies
during policy updates.
Ø It is possible for external factors to cause user
credential inconsistencies over the lifetime of a transaction.
PROPOSED SYSTEM:
Ø We formalize the concept of trusted transactions.
Ø We define several different levels of policy
consistency constraints and corresponding enforcement approaches that guarantee
the trustworthiness of transactions executing on cloud servers.
Ø We propose a Two-Phase Validation Commit (2PVC)
protocol that ensures that a transaction is safe by checking policy,
credential, and data consistency during transaction execution.
Ø We carry out an experimental evaluation of our
proposed approaches.
ADVANTAGES
OF PROPOSED SYSTEM:
Ø Identifies transactions that are both trusted and
conform to the ACID properties of distributed database systems.
Ø Guarantee the trustworthiness of transactions
executing on cloud servers.
Ø A transaction is safe by checking policy, credential,
and data consistency during transaction execution.
Ø Most suitable in various situations.
SYSTEM
REQUIREMENTS:
HARDWARE REQUIREMENTS:
Ø
System : Pentium IV 2.4 GHz.
Ø
Hard Disk :
40 GB.
Ø
Floppy Drive : 1.44
Mb.
Ø
Monitor : 15
VGA Colour.
Ø
Mouse :
Logitech.
Ø Ram : 512 Mb.
SOFTWARE
REQUIREMENTS:
Ø Operating system : Windows
XP/7.
Ø Coding Language : ASP.net,
C#.net
Ø Tool : Visual Studio 2010
Ø Database : SQL
SERVER 2008
REFERENCE:
Marian K.
Iskander, Tucker Trainor, Dave W. Wilkinson, Adam J. Lee, and Panos K.
Chrysanthis, “Balancing Performance, Accuracy, and Precision for Secure
Cloud Transactions”, VOL. 25, NO. 2, FEBRUARY 2014.
No comments:
Post a Comment