Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

github.com

Post reply on HN
Print view View original

21–30 of 35 posts

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#21

Post by throwaway823882 »

I think there would be more value to this project as a standard, and a set of implementations of the standard in different libraries and frameworks.

The companies I work for are just going to re-implement this (poorly) in their own language and framework. They generally can't just pick up a single turn-key solution, because they already have 50 custom internal systems with records they need to manage.

If there were open source libraries that followed a standard for GDPR record management, they could pick up those libraries and plug the pieces they need together, according to the standard. That would remove a lot bugs from trying to write all the code themselves, and make it easier to integrate different systems.

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#23

Post by Rule35 »

remus wrote: post #13
intricatedetail wrote: post #3

> and you still need to consult with an attorney specializing in privacy. Governments should be refunding solicitor costs to anyone needing GDPR advice. Otherwise this is just another way to add barriers. If you are on modest income you can forget about setting up a website in the EU.

> Otherwise this is just another way to add barriers. Personally I think pretty much everything in GDPR is just sensible guidelines for how to handle personal data, and if you're not willing to do those things then you probably shouldn't be handling personal data in the first place. Being ignorant of good data practice is not an excuse. > If you are on modest income you can forget about setting up a website in the EU…

> GDPR is just sensible guidelines for how to handle personal data

And yet it doesn't say "don't give it to me if you don't want me to have it."

> GDPR only applies to personal info for a start so if you don't store personal info then you have nothing to worry about.

So logging IPs is fine?

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#24

Post by jeffffff »

jimmygrapes wrote: post #18
NiceWayToDoIT wrote: post #5

Nice project, although I have question I would appreciate someone can answer. How does in real world "right to forget" works. What is confusing part for me that data that identify you are also required for the business, so how do you draw line what can be forgotten and what cannot. Let say I use some service, then I violate policies of that company, then I exercise my "right to forget", and after they delete my data…

I am no expert on GDPR or security, but wouldn't a simple "PII to Cryptologically Secure Hash" solution work for some of this? The PII would possibly need to be accessed piecemeal while the account is active, so hashing is not appropriate alone, but once the account is deleted you could store a user's hash (or partial hash, made from only truly unique info or info combos) since it cannot be reconstituted and contains…

this doesn't cut it. someone could take a list of email addresses, hash them, and then reidentify the dataset. hashing buys you nothing from a gdpr/ccpa compliance perspective, storing the hash is seen as no different from storing the pii itself. it really only makes things harder because it becomes more difficult to find where all the pii is when someone submits a request for you to return or delete their data.

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#25

Post by tmd83 »

It seems like a nice idea, the different consent/withdraw/forget workflow. But it seems the core idea is that all user PII is stored in a central table/tables and all other places uses reference. You can do this normally in a regular application, even the old version had only userId (a non PII info without the user table) and the PII was centralized. I think the biggest challenge is getting there where your PII is not spread all over the database and some denormalized PII for performance or whatever reason.

I guess the biggest advantage of this project is removing access to the PII by means of joins and such and automatically enforcing access to PII using a restricted API. I guess a premade API makes it much easier to ensure nobody ends up violating that access and integrate PII too closely with the application.

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#26

Post by michaelmior »

Rule35 wrote: post #23
remus wrote: post #13

Earlier quoted context omitted.

> Otherwise this is just another way to add barriers. Personally I think pretty much everything in GDPR is just sensible guidelines for how to handle personal data, and if you're not willing to do those things then you probably shouldn't be handling personal data in the first place. Being ignorant of good data practice is not an excuse. > If you are on modest income you can forget about setting up a website in the EU…

> GDPR is just sensible guidelines for how to handle personal data And yet it doesn't say "don't give it to me if you don't want me to have it." > GDPR only applies to personal info for a start so if you don't store personal info then you have nothing to worry about. So logging IPs is fine?

IP addresses are (probably) considered personal data under the GDPR.

https://www.fieldfisher.com/en/services/privacy-security-and...

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#27

Post by NiceWayToDoIT »

jimmygrapes wrote: post #18
NiceWayToDoIT wrote: post #5

Nice project, although I have question I would appreciate someone can answer. How does in real world "right to forget" works. What is confusing part for me that data that identify you are also required for the business, so how do you draw line what can be forgotten and what cannot. Let say I use some service, then I violate policies of that company, then I exercise my "right to forget", and after they delete my data…

I am no expert on GDPR or security, but wouldn't a simple "PII to Cryptologically Secure Hash" solution work for some of this? The PII would possibly need to be accessed piecemeal while the account is active, so hashing is not appropriate alone, but once the account is deleted you could store a user's hash (or partial hash, made from only truly unique info or info combos) since it cannot be reconstituted and contains…

There are two issue with hashing I can envisage:

1. Nothing user has is truly hash-able, (email can be replaced, there are people with the same name/dob/place of birth, address is not permanent attribute...)

2. Hash key can have duplicates - so those collisions would block different users (probably not for small companies but for FB with 2 billion users something worth considering.)

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#28

Post by runningmike »

Nice project. But mind that Some risks are designed by default. 1. Centralisation 2. Search 3. No automatic retention 4. Hard issues for managing online and offline backup/restore are not tackled. 4. Option to use cloud storage/ service 5. Too much details needed for a customerrecord.

Text on the site is often incorrect. ‘pseudonymization as a valid solution to store customer data as defined by GDPR.’ This is simple not true. Gdpr measurements are based on defined risks that differ per use case.

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#29

Post by stremovsky »

tmd83 wrote: post #25

It seems like a nice idea, the different consent/withdraw/forget workflow. But it seems the core idea is that all user PII is stored in a central table/tables and all other places uses reference. You can do this normally in a regular application, even the old version had only userId (a non PII info without the user table) and the PII was centralized. I think the biggest challenge is getting there where your PII is no…

Thanks for the feedback!

Re: Show HN: Databunker – a GDPR compliant, secure storage for personal data (PII)

#30

Post by stremovsky »

runningmike wrote: post #28

Nice project. But mind that Some risks are designed by default. 1. Centralisation 2. Search 3. No automatic retention 4. Hard issues for managing online and offline backup/restore are not tackled. 4. Option to use cloud storage/ service 5. Too much details needed for a customerrecord. Text on the site is often incorrect. ‘pseudonymization as a valid solution to store customer data as defined by GDPR.’ This is simple…

Thanks for the feedback. I would love to clarify all your questions. yuli@privacybunker.io
Post reply on HN