One year after the GDPR came into force, did anything happen?
summary
One year after the GDPR goes live the talk lists concrete failures and fixes for websites: authorities target contact forms, ERP/CRM exports and CMS plugins; audits repeatedly flag missing breach documentation, weak passwords and unpatched sites. Actionable items include running securityheaders.com scans, enforcing two‑factor authentication, scheduling plugin updates and offline encrypted backups, removing no third‑party embeds like automatic Google Maps/YouTube imports, documenting data flows and having a tested breach‑report and recovery plan that actually works.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 2:51GDPR guidelines and best practices
- 5:07Territorial scope and data protection officers
- 10:21Compliance and enforcement in Germany
- 13:23German approaches to data protection
- 17:48Access security and password policies
- 20:17Technical measures and server security
- 23:40Privacy-friendly integrations
- 25:51Cookies and third-party content
- 28:22Two-factor authentication and responsibility
- 30:13Security headers and website maintenance
- 32:58Data breach procedures and reporting
- 36:07Final remarks and Q&A
