secure aggregation

**Secure Aggregation** is the **cryptographic protocol used in federated learning that allows a central server to compute the sum of client model updates without learning any individual client's gradient values** — providing mathematical privacy guarantees that the server cannot reconstruct any participant's local training data even if it observes the aggregated result, addressing the critical weakness that raw gradient updates can expose private training information. **What Is Secure Aggregation?** - **Definition**: A multi-party computation (MPC) protocol where N clients each hold a private vector v_i (gradient update) and jointly compute ΣV_i (sum of all updates) such that the server learns only the sum — not any individual v_i. - **Problem Solved**: In standard federated learning, each client sends raw gradients to the server — gradient inversion attacks (Zhu et al., 2019) can reconstruct training images pixel-perfectly from gradient updates alone, undermining FL's privacy promise. - **Key Property**: Even if the server is "honest but curious" (follows protocol but analyzes all received data), it cannot recover any individual client's gradient from the protocol outputs. - **Bonawitz et al. (2017)**: Google researchers published the seminal practical secure aggregation protocol for federated learning at scale, deployed in production for Gboard. **Why Secure Aggregation Matters** - **Gradient Inversion Attack**: Zhu et al. (2019) showed that given a client's gradient update, an adversary can reconstruct the original training image in fewer than 100 iterations of optimization — the gradient contains as much information as the raw data for small batches. - **Honest-But-Curious Server**: Many FL deployments involve clients who must trust the central server (telecom, tech giant) with gradient updates — even if the server is legally constrained, a data breach of gradient logs could expose user data. - **Regulatory Compliance**: GDPR Article 25 (Privacy by Design) and CCPA require minimizing data processed by third parties — secure aggregation ensures the server processes only aggregate statistics, not individual data. - **Multi-Institutional Settings**: Hospitals in FL consortia may not trust each other or the aggregator — secure aggregation enables collaboration without mutual trust. **How Secure Aggregation Works (Bonawitz et al.)** The protocol uses pairwise random masks that cancel on summation: **Setup**: N clients, each holds gradient update v_i. **Step 1 — Key Agreement**: - Each pair of clients (i, j) agrees on a shared random seed s_{ij} using Diffie-Hellman key exchange. - Each client also generates a self-mask seed b_i for dropout handling. **Step 2 — Mask Generation**: - Each client i generates masks from shared seeds: for each pair j, compute PRG(s_{ij}). - Client i's masked update: masked_i = v_i + Σ_{j>i} PRG(s_{ij}) - Σ_{ji} PRG(s_{ij}) - Σ_{j