Apache Kafka and GDPR compliance

Post by closeparen » Mon, Dec 04, 2017, 8:43 PM UTC

erpellan wrote: post #8

mclarke wrote: post #4

Earlier quoted context omitted.

GDPR has an exemption related to the legal requirement to process data that might cover this (and related) scenarios. > ...(unless) processing is necessary for compliance with a legal obligation to which the controller is subject;

Does this mean that someone can game 1-time special offers by repeatedly signing up and then demanding to be forgotten? There's probably no legal obligation to enforce once-only cashback sign-up offers, so the right to be forgotten would presumably have to be followed.

Post by nerpderp83 » Mon, Dec 04, 2017, 9:28 PM UTC

Antwnis wrote: post #10

throwaway2016a wrote: post #9

I'm interested in the right to be forgotten section but I'm confused as too what this article is saying... How exactly do you "forget" the data on the logs? One interesting solution that kills two birds with one stone is if you encrypt the personally identifiable information then delete the private key if there is a request to be forgotten. Has the added benefit of also effectively destroying the data in backup copie…

> How exactly do you "forget" the data on the logs? If we think around the options, you can have either: i) eventual deletion (log retention policy) ii) compacted topics (and push null values) iii) expensive re-processing of the entire log iv) expensive segment re-write operation with each option bringing in a new set of challenges

Post by mcny » Mon, Dec 04, 2017, 9:38 PM UTC

Sir_Substance wrote: post #14

nemothekid wrote: post #12

Earlier quoted context omitted.

> What, none of these people /ever/ foresaw the need to delete some data? It's a performance trade off, and not a very surprising one. Hard Disk Drives have always been known to never actually delete data (if you want the data gone, you overwrite it with 0s). It's not unimaginable that this performance trade-off found its way up the stack. And just like a regular HDD, you can forcibly delete the data, it's just a ver…

>And just like a regular HDD, you can forcibly delete the data Except apparently not, because the linked article is literally saying it's not supported. I get wanting an audit trail, and I get wanting to not delete data if you don't have to for performance reasons, but neither of those things is the same as saying "it's literally not possible to delete stuff".

Post by theptip » Mon, Dec 04, 2017, 9:54 PM UTC

Post by theptip » Mon, Dec 04, 2017, 10:03 PM UTC

numbsafari wrote: post #18

theptip wrote: post #17

This "right to be forgotten" requirement is quite staggering in scope. Do I need to dig out all of my offsite tape backups and re-transcribe them to edit out my user's data every time a user requests to be forgotten? Sibling comments mention a cunning scheme with encryption, but that doesn't really help an enterprise with an existing non-GDPR-compliant backup archive.

My understanding is that the GDPR “right to be forgotten” does not cover backups. There may be some exceptions, but there are practical limits on its reach.