Talking to a prospect today about PII - identifying it on data loaded into the system and then processing it - eg reporting its presence.
These rules could also be incorporated into a workflow that automatically pushes the data through a validate step before doing any processing (and pop a Fire Event step afterward to alert key people when PII is detected).
The passing rows could then be passed through to subsequent processing, with the results information being fed into a PII report (either within Aperture Data Studio, or outside into a visualisation tool like Tableau / PowerBI).
First step is to figure out specifically what data elements you want to identify under 'PII' (e.g. name, address, email, dob, telephone, credit card, cookie etc).
Then build rules that help you detect each type of PII data using the functions available within the product. Some useful functions include:
Using a combination of these functions will allow you to not only detect PII data (true/false), but categorise it (e.g. email, tel etc.) and locate it (e.g. which fields contain it).
See below for a screenshot of a quick example I just built:
FYI @Steve I've built this out into a slightly more detailed post (here) with some examples of how this can be taken a little further to allow you to automatically detect the presence of PII on an automated basis (e.g. with regular data feeds from external suppliers/partners).