GDPR for lazy people: Block all European users with Cloudflare Workers

Re:GDPR for lazy people: Block all European users with Cloud... by fiddlerwoaroof on Friday May 25, 2018 @09:43PM (#17159638)

I’m not sure that delete=1 is a good idea, because you’re still mutating database records. But, it’s often lot cleaner conceptually to model state as an append-only log of assertions and retractions or via a log-structured system, where you never delete old records but just push a new index record that leaves the appropriate record out.

[ Parent | on HN ]

Re:GDPR for lazy people: Block all European users with Cloud... by _delirium on Friday May 25, 2018 @10:02PM (#17159722)

Sure, but it also leaves a much bigger attack surface, because you still have all the deleted data ready to be leaked, as has repeatedly happened in practice. It's only a cleaner solution if your risk accounting allocates close to zero cost to that, which is what most startups do.

It's hardly only EU bureaucrats who have pointed this out. See Bruce Schneier from a few years ago: https://www.schneier.com/blog/archives/2016/03/data_is_a_tox...

[ Parent | on HN ]

Re:GDPR for lazy people: Block all European users with Cloud... by fiddlerwoaroof on Friday May 25, 2018 @10:06PM (#17159742)

Yeah, my point is just that the way databases have been developing recently has been towards eliminating mutation and deletion. The GDPR’s conception of deletion is fundamentally opposed to these models.

However, you can sort of match the two by storing personal data in a separate key-value map, using the (random) key from that map to link your data to the personal data and then just deleting the map entry when someone asks to be forgotten.

The annoying part is retrofitting data scrubbing into things like data warehouses and other systems of record, without accidentally deleting data you have a legal obligation to retain to satisfy, e.g. anti-money laundering laws or audit requirements.

[ Parent | on HN ]

Re:GDPR for lazy people: Block all European users with Cloud... by sunir on Saturday May 26, 2018 @01:41AM (#17160427)

It is insufficient to only mask PII because behavioural data can in some cases uniquely identify an individual, such as purchasing history. You have to destroy all data from the user.

By the way it is this stuff that is so maddening about GDPR. The EU steadfastly refused to be helpful by even answering frequently asked questions clearly.

[ Parent | on HN ]