helloasfen.blogg.se - Dasboot danbunker github

This customer token is basically a user pseudonymised identity.Īfterward, you can query the Databunker service using the user token to receive user personal data, saving the audit trail. Now, when Databunker returns a user token, you can store it in your existing database instead of storing personal records in clear text (PII).

Return user token (UUID generated before) to the API caller.

Encrypt the whole user JSON and save it in the backend database (MySQL, PostgreSQL, SQLite).

Random generation of a user UUID token to be used as the main user index.

Generate an error in case of duplicates found.

Check for duplicate email, phone, and login records.

Securely encode email address, phone number, login name.

Generate an error if some fields are missing or error.

Strict user schema validation if the schema is defined in the configuration.

Normalize email address, phone number, login name.

Request sanity check and access validation check.

Upon an API request to create a new user record, Databunker performs the following operations: However, data breaches are a common occurrence, specifically with such a thriving cybercriminal landscape.Īmidst this, any organization falling victim to a data breach might be able to avoid GDPR fines if it implements data protection through encryption. Since the GDPR has not made data encryption a mandatory method for imposing data security, not implementing data encryption is not a violation of GDPR compliance. This method is compatible with Schrems II.ĭatabunker is a special encrypted database for sensitive personal records and Personally Identifiable Information ( PII).

This way you make the user not identifiable directly. So, now when performing a cross-border transfer or saving application logs, change user identity (email, name, etc…) with a Databunker user token. This user token is a user pseudonymised identity. When saving a user object in Databunker you are getting a user token.

User personal data is encrypted and stored separately from the application database. ‘pseudonymization’ means the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organizational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.ĭatabunker complies with the definition of pseudonymization. The controller and the processor shall implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk including the pseudonymization and encryption of personal data.