GDPR is the European Regulation that gives directives about data protection from an individual level. Every person in Europe is entitled to the some data rights which, at the organizational side, cause some major changes in how the information is managed and, consequently, affects the design and implementation of any applications that utilizes data. DBAs, by their turn, are held responsible for designing and securing those rights in a database level.
Besides their daily routines such as database administration, performance tuning and optimization and securing the data for backup and restore purposes, DBAs, should be even more concerned about data lineage, accesses to data, from what sources does it come from and to what destinations this information is delivered. In a certain way, DBAs should be aware also for what purposes is this data used for and how to address data leakages, if any data breaches occurs.
Not all activities, however, are exclusive responsibility to DBAs as this goes beyond database administration and falls into data governance category. So, what tools and tricks shall a DBA be aware of to help answer the challenges that GDPR imposes to our daily routines? This presentation aims at trying to give a brief panorama, gives some ideas on how to sort out some issues and present a simple framework that, even not thorough and complete, can help mitigate issues related to data lineages, data subject information reporting and the right to be forgotten.