Orphaned Data Object Detection in Privacy Integration Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistent data management across multiple systems leads to orphaned data objects, which can result in non-compliance with data privacy regulations and inefficient resource utilization, as these objects are not processed according to data privacy integration protocols due to lack of requester applications initiating the protocol.
Innovation Solution
A system and method to identify and handle orphaned objects by receiving end-of-purpose information from responder applications, determining which requester applications store the objects, and executing data privacy integration protocols to block or disassociate purposes from these objects, ensuring compliance and resource efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If responder applications do not initiate data privacy integration protocol executions, then system complexity is reduced and responder applications remain simpler, but orphaned objects are not identified and processed leading to data privacy compliance issues
Solution Approach 1:
Instead of having responder applications initiate the data privacy integration protocol (traditional role), the system inverts the approach by having responder applications send end-of-purpose information and by a coordinator entity (e.g., data privacy service) to identify and process orphaned objects. This inversion allows responder applications to remain simple while still enabling compliance through the coordinated effort of the coordinator entity that aggregates information from all responders and initiates appropriate actions.
Solution Approach 2:
A coordinator entity (data privacy service) acts as an intermediary between responder applications and the data privacy integration protocol execution. The coordinator receives end-of-purpose information from responders, identifies orphaned objects by coordinating with requester applications, and triggers protocol executions. This intermediary approach maintains low complexity in responder applications while ensuring reliable compliance through centralized coordination.
2Measurement precision
If requester applications are queried about every object to identify orphaned objects, then complete identification of orphaned objects is achieved, but communication overhead and processing time increase
Solution Approach 1:
The system performs preliminary actions by having requester applications maintain and register information about which objects they currently store. This preliminary registration creates a baseline state that the coordinator can use to quickly identify orphaned objects by comparing against end-of-purpose information from responders, avoiding the need to query requesters about every object in every situation.
Solution Approach 2:
The system implements feedback mechanisms where requester applications provide information about their current object storage status to the coordinator. This feedback allows the coordinator to accurately identify orphaned objects by comparing the feedback information with end-of-purpose information from responders, achieving precise identification without exhaustive querying in all cases.
3Reliability
If data privacy integration protocol is executed for all objects, then data privacy compliance is ensured, but computational resources are wasted on objects that are not orphaned
Solution Approach 1:
The system extracts and identifies only the specific subset of objects that are orphaned (those for which end-of-purpose information has been received and for which no requester currently stores the object). By extracting only these relevant objects for protocol execution, the system ensures data privacy compliance for orphaned objects while avoiding unnecessary computational resource consumption on non-orphaned objects.
Solution Approach 2:
The system changes the parameter of protocol execution from a blanket approach (executing for all objects) to a targeted approach (executing only for orphaned objects identified through comparison of end-of-purpose information with current storage status). This parameter change optimizes resource utilization by executing the protocol only when necessary while maintaining compliance.
Data Source
AI summary
The present disclosure involves systems, software, and computer implemented methods for data privacy. One example method includes receiving, from responder applications that participate in but do not initiate a data privacy integration protocol, end-of-purpose information for at least one object. The responders respond to protocol commands for executions of the protocol requested by a requester application. Identifying information for objects can be provided to each requester application in a message to the requester application that requests the requester application to determine whether the requester application currently stores the objects. At least one orphaned object can be identified from information in the responses received from the requester applications. An orphaned object is an object for which a responder application has provided end-of-purpose information but for which no requester application currently stores the object. Execution of the data privacy integration protocol can be triggered for each orphaned object.