cryptDB talk tomorrow 11:00am

[cs294 s11]

---------- Forwarded message ----------
From: Prashanth Mohan <prm...@eecs.berkeley.edu>
Date: Sat, Apr 16, 2011 at 1:02 PM
Subject: Fwd: [AMP Cloud] Talk on CryptDB by Raluca Popa (MIT) Monday
(4/18) 11am in 405 Soda Hall
To: cs29...@gmail.com


FYI

---------- Forwarded message ----------
From: Ali Ghodsi <al...@eecs.berkeley.edu>
Date: Sat, Apr 16, 2011 at 12:55 PM
Subject: [AMP Cloud] Talk on CryptDB by Raluca Popa (MIT) Monday
(4/18) 11am in 405 Soda Hall
To: amp-...@lists.eecs.berkeley.edu



Raluca Popa is visiting from MIT, and will be presenting CryptDB on
Monday's cloud seminar 11am. For those who attended Sam Madden's talk,
this work is part of the RelationalCloud project.

Please note the new location (405 Soda Hall).

http://cloudseminar.berkeley.edu

Title: CryptDB: Confidentiality for Database Applications with
Encrypted Query Processing
Speaker: Raluca Ada Popa (MIT)
Date&Time: Monday, 18th of April, 11:00am-12:00pm
Location: 405 Soda Hall

Abstract:
Online applications are vulnerable to the theft of sensitive
information because adversaries can exploit software bugs to gain
access to private data, and because curious or malicious
administrators may capture and leak data. CryptDB is a system that
provides practical and provable confidentiality in the face of these
attacks for applications backed by SQL databases. It works by fully
executing SQL queries over encrypted data using a collection of
efficient SQL-aware encryption schemes. CryptDB also chains encryption
keys to user passwords, so that a data item can be decrypted only
using the password of one of the users with access to that data. As a
result, a database administrator can tune a database without learning
confidential information, and, even if all servers are compromised, an
adversary cannot decrypt the data of any user that is not logged in.
Our evaluation shows that CryptDB has low overhead: on a real
application, phpBB, CryptDB reduces throughput by 13%, and on the
TPC-C benchmark by 27% compared to regular Postgres. Chaining
encryption keys to user passwords requires 11–13 unique schema
annotations for database schemas of three multi-user web applications
to capture their policies.




--
Prashanth Mohan
http://www.cs.berkeley.edu/~prmohan