Close popover
James Neal (JamesNeal6927a)

JamesNeal6927a Member since 2017 5 posts
Posted: August 1, 2017
Last activity: August 2, 2017

Data Masking of all Identified Fields

This question has been asked before but I have a different spin. Plus, I haven't seen any real robust answers to this type of question. They all seem individual code/setting based per field.

I want to identify a list of fields that will always be masked for everyone not associated with the appropriate rule set.

This includes, UI, Flows, Reports, etc..

I don't want to have to write special code and/or settings to implement. If the field, on the list, appears anywhere in Pega it is treated accordingly. This list enables every company using Pega to customize the names, types, etc. without worrying about location, usage, etc..

Since PII, ITAR, HIPPA, FISMA, PCI, and EAR are all internationally recognized as sensitive data I'd hope this has been addressed, or can be addressed in a future release, in the Pega platform holistically and not just an afterthought.

I've attached a simple workflow pic for clarity. This is a simple effective way to enable field masking. The performance impact can be analyzed and this could be enabled via an admin option so it doesn't have to be used if it isn't wanted.

Enterprise Application Development Dev/Designer Studio Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.