14.42 Right to be Forgotten

This section provides information about the Right to be Forgotten feature used in the OFSAA Data Foundation applications.

Right to be Forgotten is the task of dropping PII (Personally Identifiable Information) of a Data Subject for the given Party. The financial institution can drop PII for those Data Subjects who have exercised the Right to be Forgotten functionality.

The Data Subjects may have made significant financial transactions, and (or) financial information may be required for regulatory or compliance reporting. Deleting the complete record that consists of PII may lead to issues in data reconciliation. In OFSAA, the PII data is replaced with randomized values, and therefore, the complete Data Subject record is retained. As a result, financial information is retained; however, the associated Party PII is removed permanently.

Implementation of Right to be Forgotten by OFSAA

To implement Right to be Forgotten, follow these steps:

1. Use the FSI_PARTY_RIGHT_TO_FORGET table to collect the input list of Party IDs for which PII must be removed from the system. The financial institution must source this Party ID list into the FSI_PARTY_RIGHT_TO_FORGET table, and then call the batch (<<INFODOM>>_RightToForget) or schedule it.

   Note:

   • For the sample query, see the Sample Query for the FSI_PARTY_RIGHT_TO_FORGET Table section.
   • If Redaction is already performed and if you want to implement Right to Forget, you must revert the redaction policy. For more information, see the Disabling Data Redaction section in Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.
2. Use the AAI table AAI_DRF_FUNCTION_COLUMN_MAP to store the PII attribute list. During the Right to Forget batch execution, the AAI_DRF_FUNCTION_COLUMN_MAP table is referred to as randomize the PII values. See the Data Redaction section in Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x
   1. Use the AAI table AAI_DRF_QUERY_METADATA to store the query metadata, which is used during the <<INFODOM>>_RightToForget batch execution. This is the query metadata table that can lead to the following two types of queries:
      1. When the table consists of Party Identifier as an attribute, a simple record is required in the metadata query table.
         For example:

         Select v_party_id from Dim_Party where v_party_id=’10’

      2. When the table does not consist of Party Identifier as an attribute, an interrelated set of records is required in the metadata query table AAI_DRF_QUERY_METADATA. Compose these set of records in a systematic way such that, for the selected Party Identifier, the table join procedure can be performed and traversed to reach the required PII attribute.
      3. To see more information about the table in the above image, see the Table Definition for AAI_DRF_QUERY_METADATA section.

         For example:

         DIM_CLAIM table does not consist of N_CLAIM_SKEY (N_CLAIM_SKEY is the required Primary Key for the PII Attribute N_DRIVER_SKEY). Therefore, perform the table join procedure similar to the following query:

         Dim_driver.n_driver_skey from dim_driver dim_driver, fct_driver_details fct_driver_details, Fct_Claim_Driver_Vehicle_Map Fct_Claim_Driver_Vehicle_Map, Dim_Claim Dim_Claim where dim_driver.n_driver_skey=fct_driver_details.n_driver_skey and fct_driver_details.n_driver_skey=Fct_Claim_Driver_Vehicle_Map.n_driver_skey and Fct_Claim_Driver_Vehicle_Map.n_claim_skey=Dim_Claim.n_claim_skey and v_claim_id='GDPR'

         In the preceding scenario, DIM_CLAIM.N_CLAIM_SKEY is a Number Data type.

         Note:

         • To arrive at the above-mentioned query, see the Steps to Perform the Table Join Procedure section.
         • For a pictorial representation of the above query, see the Pictorial Representation of Query Formed from the AAI_DRF_QUERY_METADATA Table section.
         • For more sample queries generated using the query metadata table, see Sample Queries Using the AAI_DRF_QUERY_METADATA Table section.
      4. You must arrive at the SKey or equivalent column in the table, which consists of the required PII attributes. Then the <<INFODOM>>_RightToForget batch uses this key to filter records (For example DIM_DRIVER) and randomize all the PIIs listed in the AAI_DRF_FUNCTION_COLUMN_MAP for that table.
3. Now, PII attributes can be queried and the values are randomized.