Client-Side Encryption for Network Application Data Privacy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional online services face security and privacy issues due to the reliance on content sites for user data storage, where data can be inadvertently shared or accessed by malicious users, and users must manually manage account credentials across multiple services, increasing the risk of security breaches.

Innovation Solution

Implementing transparent client-side cryptography and server key management systems where user data is encrypted at the client device and stored encrypted at content sites, allowing only authorized users to decrypt and access their data, reducing reliance on content site security and minimizing data exposure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If user data is stored in plain text at content sites for easy access, then ease of operation is improved, but security and privacy are compromised

Engineering Contradiction:
Improvedata accessVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Data is encrypted at the client device before transmission to the content site, so the encryption action is performed in advance. This allows the content site to store and retrieve data without needing decryption capabilities, maintaining ease of operation while ensuring security through preliminary encryption

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An encryption key management system acts as an intermediary between the client and content site. The system manages encryption keys and enables authorized access without requiring the content site to store or process plain text data, thus maintaining both security and operational simplicity

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If traditional username and password systems are used for data access, then ease of operation is improved, but security risks increase due to credential management

Engineering Contradiction:
Improveaccount managementVSAvoidsecurity breaches
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The traditional mechanical username-password authentication system is replaced with a cryptographic key-based access control system. Encryption keys are managed securely and used to authorize access to encrypted data, eliminating the security vulnerabilities associated with password storage and transmission while maintaining user-friendly access through the key management system

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Device complexity

If content sites manage all user data storage and access, then device complexity is reduced, but loss of information control increases

Engineering Contradiction:
Improvedata management systemVSAvoiduser data control
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The data management system is segmented into two independent parts: encryption/decryption functions remain at the client device, while storage and retrieval functions are handled by the content site. This segmentation allows the content site to manage storage operations without accessing or controlling the actual user data, maintaining both system simplicity and user data control

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8583911B1Network application encryption with server-side key management
Publication Date: 2013.11.12 AMAZON TECH INC
  • US8583911B1 patent drawing
  • US8583911B1 patent drawing
  • US8583911B1 patent drawing

AI summary

In one embodiment, a system and associated processes for transparent client-side cryptography are provided. In this system, some or all of a user's private data can be encrypted at a client device operated by the user. The client can transmit the encrypted user data to a content site that hosts a network application, such as a social networking application, financial application, or the like. The content site can store the private data in its encrypted form instead of the actual private data. When the content site receives a request for the private data from the user or optionally from other users (such as social networking friends), the server can send the encrypted user data to a client associated with the requesting user. This client, if operated by an authorized user, can decrypt the private data and present it to the authorized user.