In Production instance this PII data is secured using VPD policies applied at database level.
Where as the same is not available in Test instances. Hence, securing PII data while conversion and secure data while P2T is always a safe approach.
Note: Not applicable to Fusion Coexistence projects, the data can be masked at Source system. Since source system is the source of truth for core-HR data.
Note: Oracle announced that, there will be an option for data masking in Fusion Apps cloud, soon.
In this article, I am going to discuss about how/when to apply data masking techniques in P2T (Production 2 Test) migration:
It is recommended to apply data masking formats on test instance data to facilitate SIT or UAT test cycles. The following are the generic masking principles to be followed:
1. break the key reference identity between parent and child data objects
For example, to mask the ethnicity details of a person, just mask the person id in person table and jumble the ethnicity details. So that, even with the key id i.e, Person id, ethnicity details can not be searched/fetched.
2. Identify the type of masking format to be applied on a field
4 types of masking formats are possible:
1. Jumble
2. Substitution
2.1 Fixed string
2.2 Random
Write SQL scripts to mask the PII data and raise an SR with Oracle to run the same in HCM test instance.
In the next post, I will provide sample masking template for Fusion HCM PII data masking, using sql scripts.