What is the best way to protect "customer information and transactions" in a database being backed up and sent to another party, such that the other party cannot access the protected information when they modify the database? Can the database be de-anonymized when we have it back and have the protected information restored?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Księgowość
- Zapasy
- PoS
- Project
- MRP
To pytanie dostało ostrzeżenie
1
Odpowiedz
3190
Widoki
Hi,
Smile has developed a very useful module for RGPD: https://apps.odoo.com/apps/modules/13.0/smile_anonymization/
Unfortunately, there isn't a V14 version of the module but you can try it and see what would happen.
hope this helps.
Thank you for your response. is there a way I can de-anonymize the data when I receive it back from the other party? there is little information available ie. is there a solution for anonymizing and de-anonymizing?
Hi,
When anonymization is done, new values are added to the DB which is exported and sent to other entities. NO real Data is stored in it in the first place.
So, that other entity cannot see real data because it ain't there.
I don't believe there's what you're looking for because data is not 'encrypted'.
an encryted DB means that if i have the key, i can decrypt it and then have access to 'critical' data.
You can check this article:
Hope it's clear.
Podoba Ci się ta dyskusja? Dołącz do niej!
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
0
lip 21
|
2836 | ||
|
0
cze 21
|
3567 | ||
|
0
lip 24
|
1047 | ||
|
1
mar 22
|
1408 | ||
|
2
sty 22
|
4764 |
