Remote Browser Data Persistence via Encrypted Local Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote browsing solutions fail to effectively persist and manage encrypted data securely on client devices, leaving them vulnerable to malicious attacks and data leaks.
Innovation Solution
A remote browsing system where encrypted remote browser data, including cookies, bookmarks, and passwords, is managed by a remote browser host that decrypts and configures the data for a local browser client, ensuring secure storage and transmission, with the client lacking access to decryption keys, thus protecting data from unintended or malicious exposure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If encrypted remote browser data is stored locally on the client device, then data persistence and session continuity are improved, but security vulnerabilities and risk of data exposure increase
Solution Approach 1:
The system segments the data storage and decryption functions by storing only encrypted data locally on the client device while keeping decryption keys exclusively on the remote server. This segmentation allows persistent local storage without exposing plaintext data or keys to the client, thereby maintaining security while achieving data persistence across sessions.
Solution Approach 2:
The system moves the decryption function to a different dimension (the remote server) rather than performing it locally. By encrypting data before storage and only decrypting on the remote server when needed, the system achieves local persistence without the security risks of storing or processing plaintext data on the client device.
2Ease of operation
If decryption keys are made accessible to the client device for data retrieval, then ease of operation is improved, but data security and protection from malicious attacks deteriorate
Solution Approach 1:
The system introduces an intermediary architecture where encrypted data is stored locally and decryption occurs remotely on the server. This intermediary approach allows seamless data retrieval operations without exposing plaintext data or keys to the client device, eliminating the trade-off between ease of operation and security.
Solution Approach 2:
The system segments the decryption operation from the client device, performing it exclusively on the remote server. This segmentation maintains ease of data retrieval through local storage while preventing data leaks by ensuring decryption keys never reside on or are accessible from the client device.
3Ease of operation
If remote browser data is stored in plaintext or weakly encrypted format, then ease of access and processing is improved, but vulnerability to malicious attacks and unauthorized access increases
Solution Approach 1:
The system performs preliminary encryption of browser data before storage on the client device. By encrypting data in advance and maintaining it in encrypted form during storage and transmission, the system ensures both easy access through local storage and strong protection against malicious attacks, eliminating the need to choose between accessibility and security.
Data Source
AI summary
A remote browsing session is initiated between a remote browser client executing on a client device and a remote browser host executing on a remote browser server. The remote browser host receives from the client device, encrypted remote browser data of remote browser data that affects the remote browser session. The remote browser client does not have access to a decryption key for the encrypted remote browser data. The encrypted remote browser data is decrypted to reveal the remote browser data. The remote browser host is configured with the remote browser data. The remote browser host manages updates to the remote browser data during the remote browsing session. Periodically, updates to the remote browser data are encrypted and transmitted to the remote browser client for storage.