8.2.8 Right To Forget

The Right to Forget (RTF) feature ensures that businesses protect sensitive Personally Identifiable Information (PII) related to party data. This functionality is available in Data Foundation Cloud Service (DFCS) and involves randomizing party data when it is no longer needed in the system.

RTF Process Overview

  • The RTF process is executed as a PMF job.
  • It is user-driven, requiring customers to input Party Identifiers that need to be forgotten.
  • Users must provide Party Identifiers through a PMF input, with multiple IDs entered as comma-separated values.
  • Before executing the RTF process, users must invoke the SCD process (DIM Incremental Process) to update the Party Dimension.
  • Only Party IDs present in the Party Dimension will be considered for randomization.

RTF Execution Details

  • For each RTF request, the service checks if the user has sensitive PII-related party data in any entity.
  • If such data exists, the system fetches the list of affected entities and mask/ hide the PII-related data.
  • The RTF Metadata Registration Table is preconfigured with Party Identifier (Business Term - BTO3899) for executing the RTF functionality.

RTF Data Visualization Reports

The following RTF-related information can be viewed in Data Visualization (DV) reports:

  1. Navigate to the Catalog menu, and open the Catalog application.
  2. Click on the Shared Folders tab.
  3. Navigate to Data Foundation Reports.
  4. Locate the Right To Forget folder in the list and click Sensitive Data Anonymization. For more information, see Pre-Built Reports.
  5. Dashboard Sections:

    Figure 8-117 Right to Forget Dashboard


    Right to Forget Dashboard

    • Customer Request and Status – Displays request details.
    • Audit Log – Tracks affected records for accountability.
  6. RTF Customer Request Table – Stores details of each RTF request, including:
    • Request Identifier – Unique request number.
    • Requested Date – Date of submission.
    • Requested By – Username of requester.
    • Party Identifier – Entity involved.
    • Execution Status – Indicates success or failure.
  7. Reviewing the Audit Log:
    • Party Identifier – Matches request ID.
    • Entity Name – Type of entity affected.
    • Records Affected – Number of modified records.
  8. Filtering and Searching Requests:
    • Use filters (e.g., Date, Requested By, Status) to narrow results.
    • Select a request to view details in the Audit Log.
  9. Verifying Execution Status & Impact:
    • If successful, check affected records.
    • If failed, troubleshoot using system logs.
  10. RTF Execution Status – Once the RTF Engine PMF process completes, the system logs the execution status:
    • If the Party ID is not found, the system updates the status as Not Available and exits.
  11. RTF Audit Log – Maintains execution records at the Entity Level, including:
    • Date of execution
    • Number of records affected

Post-Execution Considerations

  • Once an RTF request is successfully processed, the party data is randomized and secured.
  • To maintain data integrity, users must ensure that the forgotten Party IDs do not re-enter the system during data loads from multiple sources into DFCS.