There's a framework called ARX that could very useful for this. The only question you have is how compliant it would be with different sets of distinct legal requirements for privacy handling. In the absence of strong legal guidance, I'd say err on the side of complying with health care regulations because that's where you're likely to find the clearest guidance and established tools.
Ping me on any PR you send. On Wed, Jun 20, 2018 at 12:49 PM Sivaprasanna <sivaprasanna...@gmail.com> wrote: > With data becoming more critical and substantial to business development, > new stringent regulations & law are getting introduced (GDPR being a recent > example), I've been spending some time lately doing research on data > anonymization and after some hefty thinking, I finally decided to go ahead > with the creation of new processor bundle that has processors like > 'AnonymizeRecord', 'DeanonymizeRecord' (not quite sure about the name > though). Following are my questions: > > - What do you guys think about these proposed processors? > - If the processors are okay to be introduced, are they "standard" > enough to get them added to our 'nifi-standard-bundles' module or is it > better to keep it separated much like others like AWS, Azure bundles, > etc. > > Having said this, I'm very much in the beginning phase with my research and > development efforts so all your inputs & feedback on this one are greatly > appreciated. > > Thanks. > > - > Sivaprasanna >
