GDPR - An overview and its relevance for QA
summary
GDPR becomes law May 25, 2018 and applies to any service handling EU personal data so non‑EU vendors face 20 million euros or 4% turnover fines; examples: a hotel chain with 13,000 employees and 190 hotels calculates a €28M worst‑case. Rights enforced: access, rectification, erasure, portability and consent for profiling. Practical QA tasks: build an automated subject-access portal, log consent timestamp and IP, enforce encryption and two‑factor, run source‑code audits, vuln scans, dynamic tests and incident response plans.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:50Who am I
- 1:42Ashley Madison case
- 2:32Hackers threat
- 6:37Why Im here
- 7:30Take pictures
- 7:50You are the data subject
- 12:03rectification erasure and to be forgotten
- 13:58profiling
- 17:21data portability
- 18:53the importance of GDPR
- 21:04Privacy by design
- 24:07Transparency
- 26:33Privacy
- 28:59Internal requirements
- 30:58Personal information vs sensitive personal information
- 37:48Testing
- 38:39Support
- 39:52Maintenance
- 40:07Ashley Madison story
- 41:42The psychological hell
related talks
49mPractical privacy: GDPR explained
25mWhen GDPR and CCPA strike
01h 00mPrivacy and GDPR: What all developers should know
52mDeveloping privacy
39mdev.privacy: GDPR in a nutshell
46mDeveloping for Privacy
59mKeynote: Building in Privacy and Data Protection -- what is demanded by the GDPR?
39mSilent Spring: What if the GDPR Was Real?