News for hackers. Stuff that matters.
Re:GDPR for lazy people: Block all European users with Cloud... by Spivak on Friday May 25, 2018 @11:19PM (#17159993)
The general recommendation is that if it's too difficult to purge specific users from your backups then:

* Have a clear data retention policy and make sure that all backups have an expiration date.

* Secure your backups with strong encryption to protect user data in the event of a leak.

* Explain it to the user when the account is deleted when the deletion will filter through your backups.

* Guarantee that if a restore is needed, their data will be immediately deleted from the restored system.

Re:GDPR for lazy people: Block all European users with Cloud... by jeremyt on Saturday May 26, 2018 @05:17AM (#17161050)
How do you keep track of what info needs to be deleted on restore without violating GDPR?
Re:GDPR for lazy people: Block all European users with Cloud... by Tomte on Saturday May 26, 2018 @08:16AM (#17161634)
Save "on restore, delete all data sets pertaining to user id 47263".
Re:GDPR for lazy people: Block all European users with Cloud... by devocracy on Saturday May 26, 2018 @02:40PM (#17163603)
You should be able to record the deletion request for the life of the backup and purge those records once the backups are deleted (all tied to the same rolling dates)