The GDPR impact in database project
summary
GDPR extends worldwide and carries 4% or €20M fine and 72-hour breach notification, with consent that can be withdrawn and a hard-to-implement right to be forgotten across OLTP, warehouses and backups. Databases must map personal data (CPF as PK is a red flag), document processing (DPIA), and bake privacy by design into schemas. Practical controls discussed include SQL Server Dynamic Data Masking, row‑level security, TLS, Transparent Data Encryption and Always Encrypted, plus auditing and replication for availability.
AI-written summary · about
chapters (5)
- 0:00Introduction and speaker intro
- 1:20GDPR overview and key definitions
- 7:07Brazil’s GDPR impact and data governance
- 12:02Database project impacts and compliance
- 21:25Summary and key takeaways
related talks
48mThe impact of the GDPR
23mdev.privacy: GDPR in a nutshell
49mHow to implement GDPR with SQL Server &Azure SQL Database
49mPractical privacy: GDPR explained
56mPractical privacy - GDPR explained
26mData Protection Update and Tales from the Introduction of the GDPR
39mdev.privacy: GDPR in a nutshell
40mUnderstanding the GDPR and applying privacy principles in your designs
