Top Banner
Ragib Hasan Johns Hopkins University en.600.412 Spring 2010 Lecture 7 03/28/20 11 Security and Privacy in Cloud Computing
18

Security and Privacy in Cloud Computing

Feb 07, 2016

Download

Documents

Rafael Chupan

Security and Privacy in Cloud Computing. Ragib Hasan Johns Hopkins University en.600.412 Spring 2010. Lecture 7 03/ 28/2011. Provenance. http://moma.org/collection/provenance/items/644.67.html. L'artiste et son modèle (1928), at Museum of Modern Art. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Security  and  Privacy  in  Cloud Computing

Ragib HasanJohns Hopkins Universityen.600.412 Spring 2010

Lecture 703/28/2011

Security and Privacy in Cloud Computing

Page 2: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 2

Provenance• Provenance: from Latin provenire ‘come

from’, defined as – “(i) the fact of coming from some particular

source or quarter; origin, derivation.

– (ii) the history or pedigree of a work of art, manuscript, rare book, etc.; a record of the ultimate derivation and passage of an item through its various owners” (Oxford English Dictionary)

• In other words, Who owned it, what was done to it, how was it transferred …

• Widely used in arts, archives, and archeology, called the Fundamental Principle of Archival

3/28/2011

http://moma.org/collection/provenance/items/644.67.html

L'artiste et son modèle (1928), at Museum of Modern Art

Page 3: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 3

Data Provenance

3/28/2011

• Definition*– Description of the origins of data and the process by which it

arrived at the database. [Buneman et al.]

– Information describing materials and transformations applied to derive the data. [Lanter]

– Metadata recording the process of experiment workflows, annotations, and notes about experiments. [Greenwood]

– Information that helps determine the derivation history of a data product, starting from its original sources. [Simmhan et al.]

*Simmhan et al. A Survey of Provenance in E-Science. SIGMOD Record, 2005.

Page 4: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 4

Forensics and Provenance in Clouds

• Cloud provenance can be– Data provenance: Who created, modified, deleted

data stored in a cloud (external entities change data)– Process provenance: What happened to data once it

was inside the cloud (internal entities change data)• Cloud provenance should give a record of who

accessed the data at different times• Auditors should be able to trace an entry (and

associated modification) back to the creator

3/28/2011

Page 5: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 5

Privacy questions

• Should the cloud provider know the identity of cloud users?

• Should cloud users know the identity of other users in the same group?

3/28/2011

Page 6: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 6

The “Bread and Butter” paper

Problem– To preserve user privacy and allow anonymous

authentication/access in a cloud– To determine authorship of data, i.e., to bind data

versions to user identities in a cloud

3/28/2011

Lu et al., Secure Provenance: The Essential Bread and Butter of Data Forensics in Cloud Computing, AsiaCCS 2010

Page 7: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 7

Threat Model

• Who are the key players?– Users– SM– SP

• Who trusts who?– Users: trust the SM, but not the SP– SP: Trust SM– SM: ?

• What attacks can happen?3/28/2011

Page 8: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 8

System Model

• SM: Manages the whole system(?), registers cloud users and providers, issues keys

• SP: Cloud service provider, manages access to cloud resources

• Users: A user is part of a group of authorized principals who can access group resources

3/28/2011

Page 9: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 9

Secure provenance (according to the paper)

By secure provenance, the authors imply– Users can anonymously authenticate themselves as

part of authorized users/groups to the cloud provider

– Users can anonymously access and modify resources– Encrypted data stored by a user can be decrypted by

other users from the same group– If necessary, the SM can trace a data item to the user

who created it

3/28/2011

Page 10: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 10

Setup

• Inputs: Security parameter k• Output: Master key, public parameters

3/28/2011

SM

K

Master Key

Param(Public Parameters)

Page 11: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 11

User/provider registration

• Inputs: Master key, public parameters, user identity• Outputs: Private key, entry in tracking list3/28/2011

Master Key

Param(Public Parameters)

User identity Ui

Private key ski

Tracking list

Page 12: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 12

User-cloud interaction (1)

User anonymously authenticate herself to the cloud

Cloud provider can check that the signature was made with a key issued by the SM3/28/2011

χ

σA = signski(Yi||χ)

σP / aski

Page 13: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 13

User-cloud interaction (2)

Provider stores Signatures and authentication information during each access

3/28/2011

EncryptedData: C = encrypt(M)

Sig = signaski(C)

Store C and σA

Page 14: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 14

Identifying authorship

3/28/2011

σA

User identity

Page 15: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 15

Confidentiality preservation

• Each user gets a different authorized group user access key

• Any group user access key can be used to decrypt a ciphertext created by other users in the same group

3/28/2011

Page 16: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 16

Discussion

Suppose Amazon S3 implements such a model. What will be the advantages, and what will be the disadvantages?

3/28/2011

Page 17: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 17

What about other provenance in computation clouds?

If the data is being manipulated by processes running in the cloud, how will the problem change?

3/28/2011

Page 18: Security  and  Privacy  in  Cloud Computing

en.600.412 Spring 2011 Lecture 7 | JHU | Ragib Hasan 183/28/2011

Further Reading

Ragib Hasan, Radu Sion, and Marianne Winslett, Protecting History Forgery with Secure Provenance, ACM Transactions on Storage, December 2009