GDPArrrrr: Using Privacy Laws to Steal Identities
summary
An experiment treats GDPR's Right of Access as an attack surface, sending 150 right-of-access requests via a Python script while the attacker knows only name, guessed email and phone. Results show 83 organizations actually hold the target's data; one-quarter of organizations handed over personal records on email/phone proof, 16% accepted weak forgeries, ~40% demanded strong proof, and a few returned SSN, DOB, travel history, partial card digits and breached passwords used to log into accounts. Recommendations include stronger verification, third‑party identity checks, and clearer legal guidance.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:16Agenda
- 2:46Why GDP
- 3:06Fear
- 3:19Bad Decisions
- 3:38Time Pressure
- 3:59Flexible Language
- 4:56Right of Access
- 5:11Right of Access Process
- 5:57Letter to Organizations
- 7:00Reasonable Measures
- 8:10Three Bad Options
- 9:10The GDPR Process
- 11:10Forms of Identity
- 12:54Example
- 18:13Proposed Bill
- 18:48Online Businesses
- 19:33Legislators
- 20:22Data Hygiene
- 21:05Conclusion
related talks
22mPersonal Information Leakage by Abusing the GDPR 'Right of Access'
52mDeveloping privacy
41mIllegitimate Data Protection Requests - To Delete or to Address?
23mdev.privacy: GDPR in a nutshell
49mPractical privacy: GDPR explained
56mPractical privacy - GDPR explained
48mThe impact of the GDPR
40mHow the Identity Portions of CCPA Regs Put Consumers and Businesses at Risk
