Límite 72 horas

on YouTube ↗44m

" summary

Explains GDPR’s 72-hour breach-notification requirement from May 25, 2018: what qualifies as a security breach under the regulation, which notification duties exist toward supervisory authorities and affected data subjects, and the practical steps to take when a breach occurs. Also covers other legal obligations to report security incidents under applicable laws.

AI-written summary · about

" related talks

• 49mPractical privacy: GDPR explainedMarcus Bointon · Craft Conference 2019
• 47mYou lost data, unfortunately… Who will knock on your door and whyGopi Ramamoorthy · BSidesSF 2023
• 01h 10mThe state of the art requirement for GDPR security measures.Prokopios Drogkaris, Irene Kamara, Janita Hofman, Giuseppe Vaciago, Stefano Leucci · CPDP 2020
• 22mThe Data Breach vs The Ethics Breach: How to Prepare for BothLinda Thielová · Bitkom Privacy Conference 2020
• 59mKeynote: Building in Privacy and Data Protection -- what is demanded by the GDPR?Marit Hansen · PyData Berlin 2018
• 39mOne year after the GDPR came into force, did anything happen?Karen Falkenberg · TYPO3 Developer Days 2019
• 46mGDPR - An overview and its relevance for QAPer Thorsheim · QA Fest 2017
• 01h 00mPrivacy and GDPR: What all developers should knowJohannes Brodwall · NDC Oslo 2019