Attribute
Attribute
Presented by :
INTRODUCTION
1.1 Description
1.2 Problem Statement
1.3 Objectives
1.4 Existing System
1.4.1 Disadvantages Existing System
1.5 Proposed System
1.5.1 Advantages Proposed System
Abstract
Attribute-based encryption (ABE) has been widely used
in cloud computing where a data provider outsources
his/her encrypted data to a cloud service provider, and
can share the data with users possessing specific
credentials (or attributes).
It can be used to confidentially share data with users by
specifying access policies rather than sharing
decryption keys.
It achieves the standard notion of semantic security for
data confidentiality while existing systems only achieve
it by defining a weaker security notion.
1.1 Description
Cloud computing greatly facilitates data providers who want to outsource their
data to the cloud without disclosing their sensitive data to external parties and
would like users with certain credentials to be able to access the data[1], [2], [3], [4],
[5].
Cloud Storage :
Secure Deduplication with the goal of saving storage space for cloud
storage services, Douceur et al the first solution for balancing confidentiality and
efficiency in performing deduplication called convergent encryption, where a
message is encrypted under a message-derived key so that identical plaintexts are
encrypted to the same cipher texts.
Deduplication :
Data deduplication is a specialized data compression technique for
eliminating duplicate copies of repeating data. Related and somewhat synonymous
terms are intelligent (data) compression and single-instance (data) storage
Attribute Authority:
The AA issues every user a decryption key associated with user set of attributes At
the user side, each user can download an item and decrypt the ciphertext with the
attribute-based private key generated by the AA if this user’s attribute set satisfies the
access structure.
3.3 Non Functional Requirements
Usability :
Simple is the key here. The system must be simple that people like to use it, but
not so complex that people avoid using it. The user must be familiar with the user
interfaces and should not have problems in migrating to a new system with a new
environment.
Reliability :
The system should be trustworthy and reliable in providing the
functionalities. Once a user has made some changes, the changes must be made
visible by the system. The changes made by the Programmer should be visible
both to the Project leader as well as the Test engineer.
Security :
Apart from bug tracking the system must provide necessary security and
must secure the whole process from crashing. As technology began to grow in
fast rate the security became the major concern of an organization. Millions of
dollars are invested in providing security.
Performance :
The system is going to be used by many employees simultaneously. Since the
system will be hosted on a single web server with a single database server in the
background, performance becomes a major concern.
Scalability:
The system should be scalable enough to add new functionalities at a later
stage. There should be a common channel,
Maintainability:
The system monitoring and maintenance should be simple and objective in its
approach.
Portability :
The system should be easily portable to another system.
Reusability :
The system should be divided into modules that it could be used as a part of
another system without requiring much of work.
3.4 Hardware Requirements
Processor - Pentium – 4 & higher
Speed - 2.45 GHz
RAM - 4 GB
Hard Disk - 128 GB
Monitor - Super Video Graphic Array
SYSTEM DESIGN
4.1 Introduction
4.2 Module Description
4.3 System Architecture
4.4 Use Case Diagram
4.5 Sequence Diagram
4.6 Activity Diagram
4.7 Data Flow Diagram
4.1 Introduction :
In System Design has divided into three types like GUI Designing, UML
Designing with avails in development of project in facile way with different actor
and its utilize case by utilize case diagram, flow of the project utilizing sequence,
Class diagram gives information about different class in the project with methods
that have to be utilized in the project if comes to our project our UML Will utilizable
in this way. The third and post import for the project in system design is Data base
design where we endeavor to design data base predicated on the number of modules
in our project
4.2 MODULES
Data Provider:
A data provider wants to outsource his/her data to the cloud and share it with users
possessing certain credentials.
Cloud:
The cloud consists of a public cloud which is in charge of data storage and a private
cloud which performs certain computation such as tag checking.
User:
At the user side, each user can download an item, and decrypt the ciphertext with the
attribute-based private key generated by the AA if this user’s attribute set satisfies the
access structure. Each user checks the correctness of the decrypted message using the
label, and accepts the message if it is consistent with the label.
Architecture diagram
Fig: 4.2
CONCLUSION
Attribute-based encryption (ABE) has been widely used in cloud computing, where
data providers outsource their encrypted data to the cloud and can share the data with
users possessing specified credentials. On the other hand, deduplication is an important
technique to save the storage space and network bandwidth, which eliminates
duplicate copies of identical data. However, the standard ABE systems do not support
secure deduplication, which makes them costly to be applied in some commercial
storage services. In this paper, we presented a novel approach to realize an attribute-
based storage system supporting secure deduplication.
THANKING YOU