Cloud Computing
Cloud Computing
November 2015
Department of Computer Science and Engineering
Seminar 2015
Cloud
CERTIFICATE
Seminar Coordinator
1
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
ABSTRACT
2
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
ACKNOWLEDGEMENT
NOYAL P.A
3
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
CONTENTS
Page No.
1. INTRODUCTION
3. EXISTING SYSTEM
13
14
18
18
19
21
22
24
26
27
10. CONCLUSION
29
11. REFERENCES
30
4
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
LIST OF FIGURES:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Pg.No
Cloud Computing
Structure of cloud computing
Overview of CIA framework
Time to create log files of different sizes
Structure of logger
Auditing Mechanism in cloud
Working of CIA framework
Data Flow diagram in CIA
Flowchart in CIA
11
12
17
19
20
20
22
23
24
5
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
1. INTRODUCTION
Cloud computing is the use of computing resources(H/w & S/w) that are
delivered as a service over a network (typically the internet).Cloud computing refers
to the delivery of computing and storage capacity as a services to a heterogeneous
community of end-recipients the name comes from the use of clouds as an abstraction
for the complex infrastructure. It provides remote services with a users data, software
and computation over a network. Cloud computing is the newest term for the long
dreamed vision of computing as a utility. Cloud computing is scalable services. Cloud
computing is a computing platform that resides in a large data center and is able to
dynamically provide servers the ability to address a wide range of needs, ranging from
scientific research to e-commerce. Cloud computing is expanding rapidly as service
used by a great many individuals and organizations internationally, policy issues
related to cloud computing. Details of the services provided are abstracted from the
users who no longer need to be experts of technology infrastructure. Moreover, users
may not know the machines which actually process and host their data. While
enjoying the convenience brought by this new technology, users also start worrying
about losing control of their own data. The data processed on clouds are often
outsourced, leading to a number of issues related to accountability, including the
handling of personally identifiable information. It is necessary to provide an effective
mechanism for users to monitor the usage of their data in the cloud. For example,
users need to be able to ensure that their data are handled according to the service
level agreements made at the time. They sign on for services. Conventional access
control approaches developed for closed domains such as Databases and operating
systems, or approaches using a centralized server in distributed environments, are not
suitable, due to the following features characterizing cloud environments. First, data
handling can be outsourced by the direct cloud service provider (CSP) to other entities
in the Cloud and these entities can also delegate the tasks to others, and so on.
Outsourcing of data processing invariably raises governance and accountability
questions. Second, entities are allowed to join and leave the cloud in a flexible
manner. As a result, data handling in the cloud goes through a complex and dynamic
6
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
hierarchical service chain which does not exist in conventional environments. Cloud
computing is expanding rapidly as service used by a great many individuals and
organizations internationally, policy issues related to cloud computing.
We propose a, namely Cloud Information Accountability (CIA) framework,
based on the notion of information accountability. Privacy protection technologies
built on the hide-it-or-lose-it perspective, information accountability focuses on
keeping the data usage transparent and track able.
Our proposed CIA framework provides end-to end accountability in a highly
distributed fashion. One of the main innovative features of the CIA framework lies in
its ability of maintaining lightweight and powerful accountability that combines
aspects of access control, usage control and authentication. Data owners can track not
only whether or not the servicelevel agreements are being honored, but also enforce
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 logs being periodically sent to the data owner or stakeholder while the
pull mode refers to an alternative approach whereby the user (or another authorized
party) can retrieve the logs as needed.
The design of the CIA framework presents substantial challenges, including
uniquely identifying CSPs, ensuring the reliability of the log, security issues,
accountability (The Obligation of an individual(or) Organization to account for its
activities, accept responsibility for them.),
infrastructure, etc. Our basic approach toward addressing these issues is to leverage
and extend the programmable capability of JAR (Java Archives) files to automatically
log the usage of the users data by any entity in the cloud. JAR file includes a set of
simple access control rules specifying whether and how the cloud servers and possibly
other data stakeholders are authorized to access the content itself. JAR will provide
usage control associated with logging (or) will provide only logging associated with
logging functionality. Users will send their data along with any policies such as access
control policies and logging policies that they want to enforce, enclosed in JAR files,
to cloud service providers. Any access to the data will trigger an automated and
authenticated logging mechanism local to the JARs. We refer to this type of
enforcement as strong binding since the policies and the logging mechanism travel
7
Dept. of CSE
College of Engineering
Munnar
Seminar 2015
Cloud
with the data. This strong binding exists even when copies of the JARs are created;
thus, the user will have control over his data at any location. Such decentralized
logging mechanism meets the dynamic nature of the cloud but also imposes challenges
on ensuring the integrity of the logging. To cope with this issue, we provide the JARs
with a central point of contact which forms a link between them and the user. It
records the error correction information sent by the JARs, which allows it to monitor
the loss of any logs from any of the JARs. Moreover, if a JAR is not able to contact its
central point, any access to its enclosed data will be denied.
The results demonstrate the efficiency, scalability, and granularity of our
approach. We also provide a detailed security analysis and discuss the reliability and
strength of our architecture. The following new contributions. First, we integrated
integrity checks and oblivious hashing (OH) technique to our system in order to
strengthen the dependability of our system in case of compromised JRE. We also
updated the log records structure to provide additional guarantees of integrity and
authenticity. Second, we extended the security analysis to cover more possible attack
scenarios. Third, we report the results of new experiments and provide a thorough
evaluation of the system performance. Fourth, we have added a detailed discussion on
related works to prepare readers with a better understanding of background
knowledge. Finally, we have improved the presentation by adding more examples and
illustration graphs
8
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
9
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
space you will use, a business can purchase more space or reduce their subscription as
their business grows or as they find they need less storage space.
10
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
Seminar 2015
Cloud
providers. Cloud computing may also allow for better audit trails. In addition,
information in the cloud is not as easily lost
Fig:Cloud Computing:
12
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
13
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
3. EXISTING SYSTEM
Cloud computing is the delivery of computing as a service rather than a
product, by which shared resources, software, and information are given to computers
and other devices as a utility like the electricity grid over a network (typically the
Internet). In these days a single server deals with the multiple requests from the user.
Here the server has to operate the both the request from the user simultaneously, so
the processing time will be high. This may leads to deficit of data and packets may be
delayed and corrupted and also the Data Management and the Services are not Trust
Worthy. While enjoying the convenience brought by this new technology, users also
start bothering about losing control of their own data. The data operated on clouds are
often outsourced, which lead to a number of issues related to accountability, including
the management of personally identifiable information. To allay users concerns, it is
necessary to provide an effective mechanism for users to monitor the usage of their
data in the cloud. For example, users required to be able to ensure that their data are
handled according to the service level agreements made at the time they sign on for
services in the cloud. Conventional access control approaches made for closed
domains such as databases and operating systems, or approaches with a centralized
server in distributed environments, are not suitable, because of the following features
characterizing cloud environments.
14
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
College of Engineering
Seminar 2015
Cloud
the logs. Alternatively, the decryption can be carried out on the client end if the path
between the log harmonizer and the client is not trusted. In this case, the harmonizer
sends the key to the client in a secure key exchange. It supports two auditing
strategies: push and pull. Under the push strategy, the log file is pushed back to the
data owner periodically in an automated fashion. The pull mode is an on-demand
approach, whereby the log file is obtained by the data owner as often as requested.
These two modes allow us to satisfy the aforementioned fourth design requirement. In
case there exist multiple loggers for the same set of data items, the log harmonizer will
merge log records from them before sending back to the data owner. The log
harmonizer is also responsible for handling log file corruption. In addition, the log
harmonizer can itself carry out logging in addition to auditing. Separating the logging
and auditing functions improves the performance. The logger and the log harmonizer
are both implemented as lightweight and portable JAR files. The JAR file
implementation provides automatic logging functions, which meets the second design
requirement.
The overall CIA framework, combining data, users, logger and harmonizer is
explained. At the beginning, each user creates a pair of public and private keys based
on IdentityBased Encryption [4]. This IBE scheme is a Weil-pairingbased IBE
scheme, which protects us against one of the most prevalent attacks to our
architecture. Using the generated key, the user will create a logger component which
is a JAR file, to store its data items. The JAR file includes a set of simple access
control rules specifying whether and how the cloud servers and possibly other data
stakeholders (users, companies) are authorized to access the content itself. Then, he
sends the JAR file to the cloud service provider that he subscribes to. To authenticate
the CSP to the JAR, we use Open SSL based certificates, wherein a trusted certificate
authority certifies the CSP. In the event that the access is requested by a user, we
employ SAML-based authentication [8], wherein a trusted identity provider issues
certificates verifying the users identity based on his username. Once the
authentication succeeds, the service provider (or the user) will be allowed to access
the data enclosed in the JAR. Depending on the configuration settings defined at the
time of creation, the JAR will provide usage control associated with logging, or will
provide only logging functionality.
16
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
As for the logging, each time there is an access to the data, the JAR will
automatically generate a log record, encrypt it using the public key distributed by the
data owner, and store it along with the data (step 6 in Fig. 1). The encryption of the
log file prevents unauthorized changes to the file by attackers. The data owner could
opt to reuse the same key pair for all JARs or create different key pairs for separate
JARs. Using separate keys can enhance the security (detailed discussion is in Section
7) without introducing any overhead except in the initialization phase. In addition,
some error correction information will be sent to the log harmonizer to handle
possible log file corruption. To ensure trustworthiness of the logs, each record is
signed by the entity accessing the content.
Further, individual records are hashed together to create a chain structure, able
to quickly detect possible errors or missing records. The encrypted log files can later
be decrypted and their integrity verified. They can be accessed by the data owner or
other authorized stakeholders at any time for auditing purposes with the aid of the log
harmonizer. As discussed, our proposed framework prevents various attacks such as
detecting illegal copies of users data. Note that our work is different from traditional
logging methods which use encryption to protect log files. With only encryption, their
logging mechanisms are neither automatic nor distributed. They require the data to
stay within the boundaries of the centralized system for the logging to be possible,
which is however not suitable in the cloud. Example 2, Considering Example 1, Alice
can enclose her photographs and access control policies in a JAR file and Send the
JAR file to the cloud service provider.
With the aid of control associated logging, Alice will be able to enforce the
first four requirements and record the actual data access. On a regular basis, the pushmode auditing mechanism will inform Alice about the activity on each of her
photographs as this allows her to keep track of her clients demographics and the
usage of her data by the cloud service provider. In the event of some dispute with her
Clients, Alice can rely on the pull-mode auditing mechanism to obtain log records.
17
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
18
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
19
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
the
20
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
21
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
22
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
There are two major components of the CIA, the first being the logger, and
the second being the log harmonizer.
The logger is strongly coupled with users data (either single or multiple
data items). Its main tasks include automatically logging access to data items that it
contains, encrypting the log record using the public key of the content owner, and
periodically sending them to the log harmonizer. It may also be configured to ensure
that access and usage control policies associated with the data are honored. For
example, a data owner can specify that user X is only allowed to view but not to
modify the data. The logger will control the data access even after it is downloaded by
user X. The log harmonizer forms the central component which allows the user access
to the log files. The log harmonizer is responsible for auditing.
23
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
24
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
25
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
Flowchart i,
26
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
Flowchart ii,
27
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
28
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
framework will apply multi-clouds and the secret sharing algorithm to reduce
the risk of data intrusion and the loss of service availability in the cloud and ensure
data integrity. In relation to data intrusion and data integrity, assume we want to
distribute the data into three different cloud providers and we apply the secret sharing
algorithm on the stored data in the cloud provider. An intruder needs to retrieve at least
three values to be able to find out the real value that we want to hide from the
intruder. This depends on Shamirs secret sharing algorithm with a polynomial
function technique which claims that even with full knowledge of (k 1) clouds, the
service provider will not have any knowledge of vs (vs is the secret value). We have
used this technique in previous databases-as-aserves research [5]. In other words,
hackers need to retrieve all the information from the cloud providers to know the real
value of the data in the cloud. Therefore, if the attacker hacked one cloud providers
password or even two cloud providers passwords, they still need to hack the third
cloud provider (in the case where k = 3) to know the secret which is the worst case
scenario. Hence, replicating data into multi-clouds by using a multi-share technique
may reduce the risk of data intrusion and increase data integrity. In other words, it will
decrease the risk of the Hyper-Visor being hacked and Byzantine fault-tolerant data
29
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
being stolen from the cloud provider. Regarding service availability risk or loss of
data, if we replicate the data into different cloud providers, we could argue that the
data loss risk will be reduced. If one cloud provider fails, we can still access our data
live in other cloud providers. This fact has been discovered from this survey and we
will explore dealing with different cloud provider interfaces and the network traffic
between cloud providers.
30
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
10. CONCLUSION
31
Dept. of CSE
Munnar
College of Engineering
Seminar 2015
Cloud
11. REFERENCES
32
Dept. of CSE
Munnar
College of Engineering