05-09-2016, 11:37 AM
1452750387-finalprinted.pdf (Size: 1.69 MB / Downloads: 14)
Abstract
Now a days storage system are exposed to wide numbers of threat while handling the
information in cloud service. Therefore we design a secured storage system for ensuring
security and dynamic operation in the environment. The data is stored in the server using
dynamic data operation with partitioning method. AES Encryption Technique also used
which enables the user to access process in a secure manner and efficient way. The system
does a verification to prevent the loss of data and ensures security with storage integrity
method i.e. SHA-1 algorithm. Cloud storage system enables storing of data in the cloud
server efficiently and makes the user to work with the data without any trouble of the
resources.
An efficient distributed storage auditing mechanism is planned which overcomes the
limitations in handling the data loss. In our project the partitioning method is proposed for
the data storage which avoids the local copy at the user side by using partitioning method.
This method ensures high cloud storage integrity, enhanced error localization and easy
identification of misbehaving server. To achieve this, remote data integrity checking concept
is used to enhance the performance of cloud storage. In nature the data are dynamic in cloud;
hence this project aims to store the data in reduced space with less time and computational
cost with maintaining high security.
Problem Definition:-
Cloud storage system enables storing of data in the cloud server efficiently and
makes the user to work with the data without any trouble of the resources. In the existing
system, the data are stored in the cloud using dynamic data operation with computation
which makes the user need to make a copy for further updating and verification of the
data loss. An efficient distributed storage auditing mechanism is planned which overcome
the limitations in handling the data loss.
In this the partitioning method is proposed for the data storage which avoids the
local copy at the user side by using partitioning method. This method ensures high cloud
storage integrity, enhanced error localization and easy identification of misbehaving
server. If any of the server compromised, we can recover damaged files.
Literature survey:-
Cloud storage is a service which provides direct access to networking
resources and the storage .Users data is stored in the cloud by services of hosted
network and it also provide the control to user. Therefore secured storage system
is designed to give privilege to security and runtime operation in the environment.
In the previous provided system RSA algorithm is used for encryption which uses
public key of 1024 bits. It takes more storage size and computational time for
RSA. But the actual issue in the previous proposed system is there is no way to
recover the data loss at server side. In this proposed system we use SeedBlock
algorithm to create a recovery file which is stored on a recovery server. In this
proposed system we use AES Encryption Technique which creates a 128 bit
longer key. So in a way AES is more preferable than RSA. The system does a
verification to prevent the loss of data and ensures security with storage integrity
method i.e. SHA-1 algorithm
The limitations in handling the data loss can be overcome with the planned
distributed storage auditing process. Avoids the local copy at the user side can be
avoided by using data partitioning method. This method ensures high cloud
storage integrity, improved error localization and easy identification of
misbehaving server. To enhance the cloud storage performance this remote data
integrity concept is used. In nature the data is dynamic in cloud; hence this project
aims to store the data in reduced space with less time and computational cost with
maintaining high security.
Software Requirements Specification:-
This software requirements specification provides you with some
functional details of the project.
3.1Introduction
3.1.1 Project Scope
World Wide Web is usually visualized as numerous cloud servers and
hosting third party users; therefore the term cloud computing is used for
computation can be done through the internet at remote server. Authorized
Cloud users can access cloud resources over the internet from anywhere,
without concentrating on any resource management or maintenance. Besides,
instances in cloud are certainly dynamic and scalable. The cloud has evolved
by the different technologies including parallel computing, distributed
computing, virtualization, grid computing and utility computing.
Virtualization optimizes the performance in a cost efficient manner.
Cloud data user who wish to store the data in cloud first generate the
hash code and send data along with hash to the remote cloud server. The
partitioning method is proposed for the data storage which avoids the local
copy at the user side by using partitioning method.
3.1.2 User classes and characteristics
There are four primary users of User Classes and Characteristics:
Administrators
These users control enabling or disabling the reporting capability. The
reporting capability can be enabled/ disabled at the host level, domain level,
or at the project level. The project level activation will most likely be done by
the Project Owner. Host Admin will also be allowed to configure the ETL
frequency with certain restrictions
Domain Owners
These users have a global view on size/health of the site, project
participation, and user productivity. They can configure and maintain the
Subversion activity reports at the domain level in the Subversion activity
metrics landing page. They can also view the Pre-defined Itemized reports on
most active projects, most active users, and Most active downloads. They will
also be allowed to enable/disable reporting at the domain level.
There will be only few users of this type in a domain.
Project Owners
These users are responsible for configuring (no authoring of reports
from scratch) the reports and maintaining the CEE and CBP landing page
default reports. They will also be allowed to enable/disable reporting at the
project level. If reporting is enabled in the project, they also have the option of
configuring the Subversion reporting data harvesting paths and Excluded
subversion folder paths.There will be only few users of this type in a project.
Project Users
These users will view the configured reports. They may also be
allowed to pass parameters to the report configuration and run it, but will not
be allowed to save to the dashboard, CEE or CBP landing pages. All members
of the project are potentially this type of user.
3.1.3 Operating Environment:-
JDBC- ODBC and MS ACCESS
3.1.4 Design and Implementation Constraints
Design Constraints
Availability of Network is up to the mark.
Software design requires hardware drivers in order to work accordingly.
Implementation Constraints
User must provide the correct data.
3.1.5 Assumptions and Dependencies
Assumptions
Data collected by server is correct.
TPA provides right information to user.
Dependencies
Size of database.
3.2System Features:-
There are following features to this system:-
3.2.1Security
The system will provide more security to the data of the customer by using
data partitioning method. It will provide higher security to data on public data
storage sources.
3.2.2Integrity
It ensures high cloud storage integrity, enhanced error localization and
easy identification of misbehaving server.
3.2.3Recovery
Though the data stored on server get damaged because of server
failure or anonymous attack, data can be recovered through recovery system.
3.3External Interface Requirements :-
3.3.1. User Interface
User interface decides how users interact with the system and how they
feel about the system in terms of outlook and easiness of use. A friendly and
artistic user interface would attract and retain users, while an unfriendly or dry
one could drive users away.
User interacts with TPA via Web Access. . They expect to use the least
effort to find the most accurate and complete results. This expectation is natural,
and the system design will try to meet it.
3.3.2. Hardware Interfaces
7 laptops, mouse, keyboard.
Windows 7 system requirements
1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
16 GB available hard disk space (32-bit) or 20 GB (64-bit)
DirectX 9 graphics device with WDDM 1.0 or higher driver
Linux system requirements
700 MHz processor (about Intel Celeron or better)
512 MB RAM (system memory)
5 GB of hard-drive space (or USB stick, memory card or external
drive but see Live CD for an alternative approach)
VGA capable of 1024x768 screen resolution
Either a CD/DVD drive or a USB port for the installer media