FADE: Secure Overlay Cloud Storage with

File
Assured Deletion

ABSTRACT

We address the problem of resource management for a large-scale cloud environment that
hosts sites. Our contribution centers around outlining a distributed middleware
architecture and presenting one of its key elements, a gossip protocol that meets our
design goals: fairness of resource allocation with respect to hosted sites, efficient
adaptation to load changes and scalability in terms of both the number of machines and
sites. We formalize the resource allocation problem as that of dynamically maximizing
the cloud utility under CPU and memory constraints. While we can show that an optimal
solution without considering memory constraints is straightforward (but not useful), we
provide an efficient heuristic solution for the complete problem instead. We evaluate the
protocol through simulation and find its performance to be well aligned with our design
goals.

EXISTING SYSTEM:

In Existing system the outsource data backup to third-party cloud storage services will
cost more for data management and security concerns arise in terms of ensuring the
privacy and integrity of outsourced data.

 Vanish:
Divide the data key into many key shares.

 Weakness:
Time based no fine-grained control.

PROPOSED SYSTEM:
In proposed system we present FADE, a secure overlay cloud storage system that
ensures file assured deletion and works seamlessly atop today’s cloud storage services.
FADE decouples the management of encrypted data and encryption keys, such that
encrypted data remains on third-party (untrusted) cloud storage providers, while
encryption keys are independently maintained by a key manager service, whose
trustworthiness can be enforced using a quorum scheme. FADE generalizes time-based
file assured deletion (i.e., files are assuredly deleted upon time expiration) into a more
fine-grained approach called policy based file assured deletion, in which files are
associated with more flexible file access policies (e.g., time expiration, read/write
permissions of authorized users) and are assuredly deleted when the associated file access
policies are revoked and become obsolete.
Design Of Fade:
1.Work atop todays cloud as an overlay.
2.Achieve protection from cloud clients perpective,no changes on the cloud provider
side.
Security Of Fade:
1.Fine-grained file assured deletion:Files are permanently inaccessible based on
policies.

MODULE DESCRIPTION:

Number of Modules
After careful analysis the system has been identified to have the following modules:

1. DataOwner Module.
2. Key Manager Module.
3. Storage Cloud(Third Party Provider) Module.
4. Policy Revocation For File Assured Deletion Module.
1. DataOwner Module:

The data owner is the entity that originates file data to be stored on the cloud. It may be a
file system of a PC, a user-level program, a mobile device, or even in the form of a plug-
in of a client application. The data owner requests the key manager to decrypt a blinded
version of the encrypted data key. If the associated policy is satisfied, then the key
manager will decrypt and return the blinded version of the original data key. The data
owner can then recover the data key. In this way, the actual content of the data key
remains confidential to the key manager as well as to any attacker that sniffs the
communication between the data owner and the key manager.
2.Key Manager Module:

The key manager maintains the policy-based control keys that are used to encrypt data
keys. It responds to the data owner’s requests by performing encryption, decryption,
renewal, and revocation to the control keys. The key manager can be deployed as a
minimally trusted third-party service. By minimally trusted, we mean that the key
manager reliably removes the control keys of revoked policies. However, it is possible
that the key manager can be compromised. In this case, an attacker can recover the files
that are associated with existing active policies. On the other hand, files that are
associated with revoked policies still remain inaccessible, as the control keys are
removed. Hence, file assured deletion is achieved.

3.Storage Cloud(Third party provider) Module:

The storage cloud is maintained by a third-party cloud provider (e.g., Amazon S3) and
keeps the data on behalf of the data owner. We emphasize that we do not require any
protocol and implementation changes on the storage cloud to support our system. Even a
naive storage service that merely provides file upload/download operations will be
suitable.

4.Policy Revocation for File Assured Deletion Module:

If a policy Pi is revoked, then the key manager completely removes the private key di and
the secret prime numbers pi and qi. Thus, we cannot recover Si from Sei i , and hence
cannot recover K and the file F. We say that the file F, which is tied to policy Pi, is
assuredly deleted. Note that the policy revocation operations do not involve interactions
with the storage cloud.

SOFTWARE REQUIREMENTS:

Operating System : Windows

Technology : Java and J2EE
Web Technologies : Html, JavaScript, CSS
IDE : My Eclipse
Web Server : Tomcat
Tool kit : Android Phone
Database : My SQL
Java Version : J2SDK1.5

HARDWARE REQUIREMENTS:

Hardware : Pentium
Speed : 1.1 GHz
RAM : 1GB

Hard Disk : 20 GB

Floppy Drive : 1.44 MB

Key Board : Standard Windows Keyboard

Mouse : Two or Three Button Mouse

Monitor : SVGA