Embedding GDPR into the SDLC
summary
Maps GDPR articles to concrete SDLC actions and shows which artifacts change: Privacy Impact Assessment becomes a formal step in risk analysis, DPO sits on governance boards, and privacy by design maps to architecture requirements and threat models. Practical items include adding privacy to secure coding guidelines, training and security champions in teams, using static and dynamic analysis plus automation for checks, baking a 12 domains compliance matrix into user stories and sprint work, and wiring central logging/monitoring and breach-notification into vulnerability and incident processes.
AI-written summary · about
chapters (14)
- 0:00GDPR in SDLC intro
- 3:32GDPR origins and evolution
- 8:10GDPR principles and definitions
- 11:02Integrating GDPR in SDLC
- 16:23GDPR governance roles
- 20:20Data inventory and impact assessments
- 24:11Privacy by design and default
- 27:48Automating GDPR checks
- 31:45Practical steps and examples
- 36:22Budget for compliance
- 38:51Documentation and legal risks
- 40:19Team collaboration for GDPR
- 41:24Security events and improvements
- 42:06Next steps and resources
related talks
01h 15mDATA PROTECTION ENGINEERING: WHAT IS THE ROAD AHEAD?
30mPrivacy by Design?
59mKeynote: Building in Privacy and Data Protection -- what is demanded by the GDPR?
01h 16mSecurity meets data protection: risk assessment, standards and certification
40mData Privacy and Security by Design
23mTransitioning GDPR from a Compliance Checklist to “Business as Usual”
46mDeveloping for Privacy
01h 00mPrivacy and GDPR: What all developers should know