<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Theoretical Computer Science on DASYA</title>
    <link>https://dasya.itu.dk/tags/theoretical-computer-science/</link>
    <description>Recent content in Theoretical Computer Science on DASYA</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© DASYA, IT University of Copenhagen</copyright>
    <lastBuildDate>Mon, 15 Mar 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://dasya.itu.dk/tags/theoretical-computer-science/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Secure Multi-party Computation in Databases</title>
      <link>https://dasya.itu.dk/for-students/proposals/archive/mpc-databases/</link>
      <pubDate>Mon, 15 Mar 2021 00:00:00 +0000</pubDate>
      
      <guid>https://dasya.itu.dk/for-students/proposals/archive/mpc-databases/</guid>
      <description>(This topic is going to be co-supervised by Bernardo Machado David [http://www.bmdavid.com/])
Database systems managing private data may leak sensitive information when queries are done in the clear, even if the data itself is encrypted. A recent line of research has looked into combining database engines supporting standard SQL queries with techniques for secure Multiparty Computation (MPC), which allow for both queries and data to be handled privately. In these hybrid systems, not only the data is protected but the queries made by legitimate users are kept private even from the database engine itself (and consequently from the systems executing this engine).</description>
    </item>
    
    <item>
      <title>Privacy Preserving Transformations</title>
      <link>https://dasya.itu.dk/for-students/proposals/archive/privacypreserving/</link>
      <pubDate>Tue, 08 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://dasya.itu.dk/for-students/proposals/archive/privacypreserving/</guid>
      <description>Given a private database that I can access only through specific queries, there is still a lot I can learn on its entries [1]. Differential Privacy (DP) tackles this: letting me learn the (approximate) result of complex queries on a database, but preventing me from learning much about its specific entries. The basic approach of DP often boils down to: “apply a privacy-preserving transformation T on the result of the query F or on the data itself before computing F”.</description>
    </item>
    
  </channel>
</rss>