Embedded Browser Data Encryption via Policy Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in managing data encryption and decryption for network applications accessed through embedded browsers, particularly in ensuring seamless functionality and protecting against data leakage, due to limitations in fully homomorphic encryption and computing resource constraints.

Innovation Solution

The implementation of a method where a client application with an embedded browser selectively uses tokenization and reversible encryption based on policies, identifying the type of data and user context, to encode and decode data in real-time, ensuring compatibility with network applications and reducing data leakage risks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If fully homomorphic encryption is used to allow operations on encrypted data, then data security is improved, but computing resource constraints make it impracticable

Engineering Contradiction:

Improvedata securityVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the encryption approach by using reversible encryption for data that needs to be processed and tokenized for data that requires higher security. This segmentation allows the system to avoid the high computational cost of fully homomorphic encryption while maintaining appropriate security levels for different data types.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the encryption parameter by using reversible encryption algorithms that are computationally efficient compared to fully homomorphic encryption. This parameter change reduces computing resource consumption while still providing security through tokenization for sensitive data.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If tokenization is used to substitute data with tokens, then data protection is improved, but network applications may be unable to recover original data

Engineering Contradiction:

Improvedata protectionVSAvoiddata recovery capability

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent applies local quality by using tokenization selectively for specific sensitive data fields while using reversible encryption for other data that needs to be processed and recovered by network applications. This localized application of different encryption strategies ensures data protection where needed while maintaining operational capability where required.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent introduces an intermediary component (the client application with embedded browser) that manages the tokenization and reversible encryption processes. This intermediary ensures that tokens are properly managed and that reversible encryption maintains data recoverability, thus bridging the gap between data protection and data recovery needs.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If reversible encryption is used to encode data, then data security is improved, but the encryption process may impact processing speed

Engineering Contradiction:

Improvedata securityVSAvoiddata processing speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The patent applies partial action by using reversible encryption only for data that requires it, rather than encrypting all data with the strongest possible encryption. This selective approach balances security requirements with processing speed considerations, applying encryption only where necessary.

Inventive Principle:

Principle #16Partial or excessive action

4Object-affected harmful factors

If encryption is applied to protect data from exfiltration, then data leakage prevention is improved, but the system complexity increases

Engineering Contradiction:

Improvedata leakage preventionVSAvoidsystem complexity

Core Design Contradiction:

Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent segments the data protection approach by implementing different encryption strategies (tokenization and reversible encryption) for different data types and sensitivity levels. This segmentation simplifies the overall system by avoiding the need for a single complex encryption system, instead using multiple simpler, targeted approaches.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11895096B2Systems and methods for transparent SaaS data encryption and tokenization

Publication Date: 2024.02.06 CITRIX SYSTEMS INC

AI summary

Embodiments described include systems and methods for encoding and decoding data for a network application. A client application may include an embedded browser. The embedded browser may establish a session with a network application. The client application may identify a policy specifying a type of data to encode upon input. The embedded browser may detect the type of data of an input field of the network application being displayed in the embedded browser. The embedded browser may, responsive to the detection and the policy, encode the data inputted into the input field or decode encoded data displayed in the input field.