Is it possible to comply with GDPR while using this to store data? Given that it operates like an append-only log, is it possible to actually remove data to comply with a GDPR request?
Your data modelling has to be GDPR compliant not your database.
Amazon Quantum Ledger Database
91–100 of 183 posts
Re: Amazon Quantum Ledger Database
#92Is it possible to comply with GDPR while using this to store data? Given that it operates like an append-only log, is it possible to actually remove data to comply with a GDPR request?
GDPR "Right to Forget" has an exception clause that defers to regional Accounting compliance laws, such as retaining a credit card transaction for 5 years.
Re: Amazon Quantum Ledger Database
#93Am I right in believing this looks like a competitor to Datomic?
I too am getting that vibe
Re: Amazon Quantum Ledger Database
#94This is what I use protected git repo with a pgp signature for.
Can you (have you?) say anything more publicly? Would be interested to know more.
Git and QLDB both use the Merkle tree concept to prove that history hasn't been edited. The GPG signing proves new events are coming from a trusted person or computer.
Re: Amazon Quantum Ledger Database
#95Earlier quoted context omitted.
You can use cryptoshredding: have an encryption key for each user (stored outside of this ledger) and encrypt all PII with that key. Throw away the key if the user wants you to delete their data.
What if the key leaked before you have thrown it away?
That's a good question!
If your keys leaked, you'd probably have to assume you lost all of the data up to that point. To secure the data going forward, you'd need to generate a second key per user for all of the future data. Well, and hopefully shore up the security problems!
I agree, though, that an immutable ledger like this complicates things in a way that you-shouldn't-mutate-but-can datastores do not.
Re: Amazon Quantum Ledger Database
#96Is it possible to comply with GDPR while using this to store data? Given that it operates like an append-only log, is it possible to actually remove data to comply with a GDPR request?
By not storing that type of data. It's you need to store that type of data you can also anonymize or turn into keys where you keep the answers in a separate (mutable) database. Also, for some purposes (legal) you are allowed to store the data regardless because you have to for other reasons.
But what about successors of GDPR? What if it becomes illegal to harbor certain information that already exists in the ledger?
Re: Amazon Quantum Ledger Database
#97Earlier quoted context omitted.
You can use cryptoshredding: have an encryption key for each user (stored outside of this ledger) and encrypt all PII with that key. Throw away the key if the user wants you to delete their data.
What if the key leaked before you have thrown it away?
[deleted]
Re: Amazon Quantum Ledger Database
#98Is it possible to comply with GDPR while using this to store data? Given that it operates like an append-only log, is it possible to actually remove data to comply with a GDPR request?
You can use cryptoshredding: have an encryption key for each user (stored outside of this ledger) and encrypt all PII with that key. Throw away the key if the user wants you to delete their data.
But then you must also plan for what happens when that encryption is broken. So I think you also need to control and protect your storage in order to make that a safe strategy.
The more I think about these things, the more I distrust cloud providers, and want my own hardware.
Do you really trust these companies enough to hand them the keys to all your data? Is there really any way to provide secrets to your app without trusting the hosting provider?
Re: Amazon Quantum Ledger Database
#99I'm pretty sure this is what most people actually want when they say they want a blockchain, they just don't know it yet. It's got all the useful database features with none of the "well uh let's distribute it over people's computers and let people mine coins to support it" complexity, which adds nothing to 99% of usecases besides silly ICO potential.
This. When I see something like this: https://techcrunch.com/2018/09/24/walmart-is-betting-on-the-... I just don't get it. I understand the motivation behind them wanting this sort of broad supply-chain tracking, but I don't see what "blockchain" actually solves for them that can't be more readily/efficiently solved in other ways. A trusted third party, with an immutable transaction ledger, and a simple to develop to…
> A trusted third party
What does an industry with thousands of different major players have to gain by coming together to give a single company a monopoly over their entire industry? And in fact, one of the biggest strengths of blockchain is that it provides a viable alternative to monopolies for various industries.
Re: Amazon Quantum Ledger Database
#100Is it possible to comply with GDPR while using this to store data? Given that it operates like an append-only log, is it possible to actually remove data to comply with a GDPR request?
Your data modelling has to be GDPR compliant not your database.
How do you delete user data from an immutable store? You get into cryptography at that point and then some edge cases make it not so simple.