Data Sanitization Proxy for Public Cloud PII Anonymization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Public cloud services pose a risk to organizations due to third-party access to sensitive information, such as personally identifiable information (PII), which can be exploited for identity theft or other malicious activities, and existing solutions either encrypt all data, limiting processing capabilities or rely on trusting the cloud provider to protect sensitive data.
Innovation Solution
A data sanitization system that acts as a proxy between the organization's private network and public cloud services, selectively anonymizing (encrypting) only sensitive information within messages while maintaining the original data structure, allowing secure processing by third-party services without exposing PII, and using a key identifier for decryption upon return.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all data is encrypted before transmission to public cloud services, then security of sensitive information is improved, but processing capability of the service provider is reduced
Solution Approach 1:
The patent segments data into sensitive and non-sensitive fields, applying different processing treatments to each. Sensitive fields are encrypted while non-sensitive fields remain in plaintext, allowing the service provider to process non-sensitive data without decryption keys while maintaining security for sensitive information.
Solution Approach 2:
The patent implements local quality by applying encryption selectively to specific sensitive fields within the data structure rather than encrypting the entire data set. This allows different parts of the data to have different security states, enabling processing of non-sensitive portions while protecting sensitive portions.
2Productivity
If sensitive data is transmitted in plaintext to public cloud services, then processing capability of the service provider is improved, but security risk of sensitive information is increased
Solution Approach 1:
The patent segments data into sensitive and non-sensitive fields, transmitting sensitive fields in encrypted form and non-sensitive fields in plaintext. This segmentation allows the service provider to process non-sensitive data efficiently while sensitive data remains protected during transmission and storage.
Solution Approach 2:
The patent introduces encryption as an intermediary mechanism between the client and service provider. The encryption layer allows sensitive data to be transmitted without exposing the actual sensitive information to the service provider, while still enabling the provider to perform processing operations on the encrypted or non-sensitive portions of the data.
3Reliability
If data structure is modified to protect sensitive information, then security of sensitive information is improved, but compatibility with service processing is reduced
Solution Approach 1:
The patent applies local quality by modifying only the sensitive fields within the data structure while leaving non-sensitive fields and the overall data structure intact. This selective modification maintains compatibility with service processing requirements while providing security for sensitive information.
Solution Approach 2:
The patent changes the parameter state of sensitive fields from plaintext to encrypted form, while maintaining the same data structure and field organization. This parameter change enables security protection without affecting the structural compatibility required for service processing.
Data Source
AI summary
The example embodiments are directed to a system and method for managing blockchain transaction processing. In an example, the method includes one or more of receiving a message transmitted from a client device, the message including a predefined structural format for processing by a service providing computing system, determining a type of the message and detecting one or more sensitive fields within the message based on the determined type of the message, anonymizing values of the one or more sensitive fields within the message while leaving the predefined structural format intact, and transmitting the anonymized message including the one or more anonymized values with the predefined structural format remaining intact to the service providing computing system. The system can anonymize data from a private network before it is transmitted to a public service.