Enhanced data security for Pega SoR solutions

The promotion of the Pega SoR pattern, and the capabilities of the Common Data Application are making it more probable that our applications will contain larger quantities of more accessible sensitive data and PII. Can this Expert Circle be a host for insights into product capabilities (and limitations), and design best practices for maximising data security?

Traditionally we would only store small subsets of work-in-progress business data, typically embedded in Case BLOBs. This made it feasible to encrypt, and difficult to access at volume. Case architecture also contains capabilities to associate data by reference, and control, monitor, and alert on data missuse e.g. field-level audit. Storage of SoR data tends to make use of the Data architecture in Pega, which utilises ‘external classes’ with data stored in exposed columns. This implies more complexity in terms of data encryption and access control, and more risk from bulk access operations e.g. Search.

I appreciate that the topic spans all aspects of the solution design - storage, infrastucture, application design, operations design, and UX design. But where might we best host a University of Data Security?

@healj Thank you for starting this conversation.

You are right, it this is a complicated topic, but to your point, there are ways to protect data today.

What other control would you like to see added to the platform?

Itamar

Hi @budii. I’ve put up the post initially to find out if there is a domain of concern over this topic. Let us see whether the posting resonates before moving on to identifying specific features or controls that might be appropriate to add.

Does anyone else want to convene on this topic?