Data Anonymization Limitations

[Rachna S]

Hi,

I recently started exploring Data privacy/Data Anonymization techniques for a requirement of ours. The requirement is to mask email addresses entered in the summary or description field of an incident form. This masking must only happen 7 days after an incident is closed and some privileged roles should still be able to still the actual email addresses. From what I've read so far, I don't think the data anonymization product caters to any of our requirements. 

Firstly, it does not let us specify characters to selectively mask email addresses in a string field that may also contain other data before or after email address, then it does not let us run scheduled job periodically or even trigger it from a flow or something as entering a start time and end time is mandatory when scheduling. Lastly, I don't see the option to allow certain roled users to be able to see actual data even after it is masked.

Can someone please help me confirm if my understanding of the limitations is correct here ? OR if there is a way around to resolve ?

Thanks

Rachna

[Mathias Vandend]

Hi Rachna
I came to the same conclusion. Only applicable for fields with a specific input of data like email, phone, etc...
And indeed no scheduling based on certain criteria.