This section provides information about the Pseudonymization feature used in the OFSAA Data Foundation applications.
Topics:
· Overview of Pseudonymization
· Implementation of Pseudonymization by OFSAA
Pseudonymization is a process by which PII fields of a record are replaced by one or more artificial identifiers or pseudonyms. There can be a single pseudonym for a collection of replaced fields or one pseudonym for each replaced field. Therefore, Pseudonymization is a method to substitute PII data with a reversible and consistent value. This decreases the linking ability of a data set with the original identity of a data subject and acts as a Data Security mechanism.
The mapping of pseudonyms to those PIIs that are required for lookups, to retrieve the data subject information, must be stored away from the data warehouse in a secure location. This involves highly restricted access controls and security mechanisms that are defined in the customer environment to suit customer data security needs.
OIDF data model enables its customers to implement the Pseudonymization process such that the PII data is separated from transaction data, and this PII data is referenced only by a pseudonym. For a wide range of analytical processes, access to PII data is not necessary.
1. Customers can employ Pseudonymization and load the Pseudonymized data into OIDF.
2. When analytical or modeling condition requires the availability of PII data, then care must be taken by the customer to load PII data into those columns that consist of additional data security controls such as Redaction. When the required attributes are not part of the seeded PII list, then the customer must:
§ Extend the PII list
§ Verify the completeness of the extensions
§ Verify that Redaction is enabled on the extended PII fields prior to loading sensitive data attributes
To know more about Data Redaction, see Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.
NOTE:
It is recommended that the PII values must not be added in the account dimension, party dimension, and customer dimension columns where redaction is not applied. For example, PII values must not be added in the V_ACCOUNT_NUMBER, V_PARTY_ID, and V_CUST_ID columns. Instead, they must be loaded in the V_ORIGINAL_ACCOUNT_NUMBER, V_ORIG_PARTY_ID and V_ORIG_CUST_REF_CODE columns respectively, where redaction is applied.