A Platform for Secure Analytics and Machine Learning

Born out of research in the UC Berkeley RISE Lab, MC² is a platform for running secure analytics and machine learning on encrypted data. With MC², users can outsource their confidential data workloads to the cloud, while ensuring that the data is never exposed unencrypted to the cloud provider. MC² also enables secure collaboration -- multiple data owners can use the platform to jointly analyze their collective data, without revealing their individual data to each other.

MC² provides the following secure computation services:

Opaque SQL: Encrypted data analytics on Spark SQL using hardware enclaves
Secure XGBoost: Collaborative XGBoost training and inference on encrypted data using hardware enclaves

The MC² project also includes exploratory research prototypes that develop new cryptographic techniques for secure computation. Please visit the individual project pages for more information:

Cerebro: A general purpose Python DSL for learning with secure multiparty computation.
Delphi: Secure inference for deep neural networks.
Muse: Secure inference resilient to malicious clients.
Federated XGBoost: Collaborative XGBoost in the federated setting

For more information on MC², visit our website.

This repository contains the source code for the MC² client, which enables users to easily interface with MC² services deployed remotely in the cloud. Currently, the client supports remote deployments of Opaque SQL only. Support for Secure XGBoost is coming soon. To run an end-to-end MC² workflow:

Launch Opaque SQL in the cloud (instructions to do so can be found in the respective repositories)
Use the MC² client to encrypt data locally, transfer it to the cloud VMs, run scripts specifying the desired computation, and retrieve and view encrypted results.

Installation
Quickstart
Documentation
Contact

Installation

To quickly play with MC² Client and Opaque SQL, you can use the provided Dockerfile to build a container (takes ~7 min) with all MC² Client and Opaque SQL dependencies. Alternatively, you can pull a pre-built Docker image instead of building one. To do either, you must have Docker installed.

The container will have the contents of this mc2 directory at /mc2/client, and Opaque SQL will be at /mc2/opaque-sql

For ease of use, we recommend that you create a directory within your host mc2 directory that will serve as your playground, and then mount your playground directory to the Docker container. Mounting will ensure that changes you make in your playground directory outside the container will be reflected inside the container, and vice versa. If you're bringing your own data, you can either copy your data over to your playground directory, or separately mount your data directory to the container.

Installation via building an image

# Clone the `mc2-project/mc2 repo`
git clone https://github.com/mc2-project/mc2.git

# Build a Docker image called `mc2_img`
docker build -t mc2_img .

# Run the container, mounting your playground to the container, and open a shell into the container
docker run -it -v </absolute/path/to/mc2/playground>:/mc2/client/playground mc2_img /bin/bash

Installation via pulling an image

If you prefer to pull the image instead, you can pull a pre-built image (~3 GB) from Docker Hub.

# Clone the `mc2-project/mc2 repo`
git clone https://github.com/mc2-project/mc2.git

# Pull the mc2_img from Docker Hub
docker pull mc2project/mc2_img:v0.1.3

# Run the container, mounting your playground to the container, and open a shell into the container
docker run -it -v </absolute/path/to/mc2/playground>:/mc2/client/playground mc2_img /bin/bash

Installation via build from source

Alternatively, if you'd like to install MC² Client directly on your host, follow these instructions.

Quickstart

This quickstart will give you a flavor of using MC² with Opaque SQL, and can be entirely done locally with Docker if desired. You will use MC² Client to encrypt some data, transfer the encrypted data to a remote machine, run an Opaque SQL job on the encrypted data on the remote machine, and retrieve and decrypt the job's encrypted results. To run everything securely, you can choose to spin up Opaque SQL on Azure VMs with SGX-support. Alternatively, to get a flavor of MC² without having to use Azure, you can use the deployment of Opaque SQL in the Docker container.

MC² Client provides a command line interface that enables you to remotely interact with MC² compute services. The CLI relies on a configuration file that you should modify before each step in this quickstart to tell MC² Client what exactly you want to do. An example of the configuration file is here.

The dataset we'll be using in this quickstart is a medical dataset containing patient records. Here's a couple of sample records for reference.

Age,BMI,Glucose,Insulin,HOMA,Leptin,Adiponectin,Resistin,MCP.1,Classification
48,23.5,70,2.707,0.467408667,8.8071,9.7024,7.99585,417.114,1
83,20.69049454,92,3.115,0.706897333,8.8438,5.429285,4.06405,468.786,1
82,23.12467037,91,4.498,1.009651067,17.9393,22.43204,9.27715,554.697,1

If you get stuck at any point while running the quickstart, feel free to ping us on Slack.

Docker Quickstart

If you'd like to try everything out locally, you can do so within the Docker container you built in the installation section.

In the container, copy the contents of the quickstart directory to your mounted playground directory to ensure that your changes inside the container get reflected on your host. Then, configure MC² Client with your configuration file.
```
# From the /mc2/client directory
cp -r quickstart/* playground
mc2 configure $(pwd)/playground/config.yaml
```
Generate a keypair and a symmetric key that MC² Client will use to encrypt your data. Specify your username and output paths in the user section of the configuration file. Then, generate the keys.
```
mc2 init
```
Start Opaque SQL, a MC² service for secure SQL analytics.
```
mc2 start
```
Prepare your data for computation by encrypting and uploading it. This step uses the keys you generated in step 2 to encrypt your data. Note that "uploading" here means copying because we have a local deployment.
```
mc2 upload
```
Run the provided Opaque SQL quickstart script, to be executed by MC². The script can be found here, and performs a filter operation over our data -- the results will contain records of all patients who are younger than 30 years old. Results are encrypted by MC² before being saved, and can only be decrypted with the key you used to encrypt your data in the previous step.
```
mc2 run
```
Once computation has finished, you can retrieve your encrypted results and decrypt them. Results are saved in the results/ directory. You can view the results by looking at results/opaque_sql_result.dec
```
mc2 download
```

Azure Quickstart

You can also choose to run this quickstart with enclave-enabled VMs on the cloud with Azure Confidential Computing. Unlike the Docker quickstart, in this quickstart you'll first launch enclave-enabled VMs on Azure using MC² before uploading data and runing computation.

Start off in the container you built in the installation section. In the container, copy the contents of the quickstart directory to your mounted "playground" directory to ensure that your changes inside the container get reflected on your host. Otherwise, no need to do anything. Then, configure MC² Client with your configuration file.
```
# From the /mc2/client directory
cp -r quickstart/* playground
mc2 configure $(pwd)/playground/config.yaml
```
Generate a keypair and a symmetric key that MC² Client will use to encrypt your data. Specify your username and output paths in the user section of the configuration file. Then, generate the keys.
```
mc2 init
```
Next, launch the machines and resources you'll be using for computation. This step does not exist in the Docker quickstart. MC² Client provides an interface to launch resources on Azure (and sets up the machines with necessary dependencies). Take a look at the launch section of the configuration file -- you'll need to specify the path to your Azure configuration file, which is a YAML file that details the names and types of various resources you will launch.

Next, log in to Azure through the command line and set your subscription ID. Here are instructions on how to find your subscription ID.
```
az login
az account set -s <YOUR_SUBSCRIPTION_ID>
```
Once you've done that, launch the resources.
```
mc2 launch
```
Start Opaque SQL, a MC² service for secure SQL analytics.
```
mc2 start
```
Prepare your data for computation by encrypting and uploading it. This step uses the keys you generated in step 2 to encrypt your data. Note that "uploading" here means copying because we have a local deployment.
```
mc2 upload
```
Run the provided Opaque SQL quickstart script, to be executed by MC². The script can be found here, and performs a filter operation over our data -- the results will contain records of all patients who are younger than 30 years old. Results are encrypted by MC² before being saved, and can only be decrypted with the key you used to encrypt your data in the previous step.
```
mc2 run
```
Once computation has finished, you can retrieve your encrypted results and decrypt them. Results are saved in the results/ directory. You can view the results by looking at results/opaque_sql_result.dec
```
mc2 download
```
Once you've finished using your Azure resources, you can use MC² Client to terminate them. You can specify which resources to terminate in the teardown section of the configuration.
```
mc2 teardown
```

Documentation

For more thorough documentation MC² Client and Opaque SQL, please visit:

Contact

Join our Slack, open a GitHub issue, or send a message to mc2-dev@googlegroups.com.

sophgen/mc2