Secure Data Transfer Using a Local Cache Locker
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data transfer technologies lack security measures to protect user profiles and devices from unauthorized access and data exfiltration, allowing bad actors to trace data items back to user profiles and access stored data items.
Innovation Solution
Implementing a local cache locker outside the user profile to store data items and decoupling servers from user profiles, along with a validation technique to authenticate data transfer and receipt requests, using proof-of-origin information to validate user legitimacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data items are shared with a website for transfer, then data transfer functionality is enabled, but user profile security deteriorates as bad actors can trace data items back to user profiles
Solution Approach 1:
The patent introduces a local cache locker as an intermediary storage mechanism between the user profile and the website. Data items are copied to this secure local storage before transfer, preventing direct exposure of the user profile to external websites while maintaining transfer functionality
Solution Approach 2:
The patent segments the data storage and transfer process into distinct components: the user profile (for permanent storage), the local cache locker (for temporary secure storage during transfer), and the website (for external access). This segmentation isolates the user profile from direct external access while enabling controlled data transfer
2Loss of information
If user profile identification is included with data items for transfer, then data transfer tracking is enabled, but security deteriorates as bad actors can trace and access user profiles
Solution Approach 1:
The local cache locker acts as an intermediary that decouples the user profile identification from the data item during transfer. The cache locker manages the association between data items and user profiles locally, preventing external websites from directly tracing data items back to user profiles while maintaining transfer tracking capability
3Ease of operation
If servers are directly connected to user profiles for data access, then data accessibility is improved, but security deteriorates as servers become vulnerable to attacks on user profiles
Solution Approach 1:
The patent positions the local cache locker as an intermediary layer between servers and user profiles. Servers can access data items through the cache locker without direct connection to user profiles, maintaining data accessibility while preventing servers from becoming vectors for attacking user profiles
Solution Approach 2:
The architecture segments server access rights from user profile access. Servers gain access to the local cache locker for data transfer operations, but this access is deliberately separated from direct user profile access, creating a security boundary that prevents server compromises from leading to user profile breaches
Data Source
AI summary
A system for performing secured operations includes a user device and a server. The user device generates a first operation data that includes the origin of the operation and a unique identifier of a user. The user device communicates the operation data to the server. The server generates, based on the first operation data, one or more first conditional rules that include a first rule that indicates the operation is to be executed when a second user requesting to receive a data item is identified. The server determines that one or more first conditional rules are met. In response, the server communicates a signal to the user device, where the signal indicates to transfer the data item to a second user device associated with the second user.