Implementing Differential Privacy for the 2020 US Census

Implementing Differential Privacy for the 2020 US Census

USENIX Enigma Conference via YouTube Direct link

At the root of our acceptance problem: Non-negativity requirements create systematic bias and increase the size of outlier errors

14 of 15

14 of 15

At the root of our acceptance problem: Non-negativity requirements create systematic bias and increase the size of outlier errors

Class Central Classrooms beta

YouTube playlists curated by Class Central.

Classroom Contents

Implementing Differential Privacy for the 2020 US Census

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Differential Privacy was invented in 2006 (14 years ago) Modem Publik Key Cryptography was invented between 1976 and 1978
  3. 3 The Census Bureau deployed the first DP implementation in the world for OnTheMap (2008)
  4. 4 We solved many technical challenges deploying DP for the 2020 Census!
  5. 5 We still haven't met user expectations.
  6. 6 The Decennial Census!
  7. 7 By 2017, we thought we had a good understanding of how DP would fit.
  8. 8 Different groups at USCB had different assumptions about the data flow.
  9. 9 The DP system had to be developed with real (Title 13-protected) data. Most systems for the 2020 Census were developed using simulated data
  10. 10 Census Bureau leadership was 100% behind the move to Differential Privacy
  11. 11 Team and Reference Implementation
  12. 12 CPU load of 21 AWS Instances during an execution of the TopDown algorithm
  13. 13 We re-published the 2010 data using the 2020 TopDown algorithm.
  14. 14 At the root of our acceptance problem: Non-negativity requirements create systematic bias and increase the size of outlier errors
  15. 15 In summary: The 2020 Census DP Timeline

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.