Do you have a Deletion/Masking Strategy? · Data Innovators Exchange

Do you have a Deletion/Masking Strategy?

I am wondering if you have a data deletion or data masking strategy in your projects if you have to delete/mask (personal) data. If yes, how do you find all the places where you have to delete/mask? The place where we usually tag data (as personal or not) is usually done in the metadata (example in Data Vault: when defining the Satellites). So, this could be used as the basis. when using column-level lineage you could figure out where the data is coming from (in case you have a PSA) and where the data goes to (Business Vault - Information Mart). Based on this, a procedure can do the delete/masking/NULLing ... What do you think about this and do you have a tool/mechanism which does that?

btw. what would you prefer? 1) NULL the values, 2) remove the whole row in the personal Satellite (but then you have to consider to re-create the PITs as some pointers to the Satellites do not exist anymore) or 3) mask it with a static value (not simple hashing of course), also to see that there was something before and to differentiate to "normal" NULLs?

Thanks for your thoughts!

2 comments