Proxy-Based PII Obfuscation for JSON Response Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in ensuring privacy, security, and compliance with data protection laws when handling Personal Identifiable Information (PII) during the execution of web-based applications.
Innovation Solution
A method and apparatus that utilize a proxy to apply predefined rules to identify and anonymize PII by matching URLs and JSON data mappings, replacing sensitive data with safe values or placeholders, and creating a PII-free dataset copy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If PII data is collected and stored for web-based applications, then data functionality and user service capability are improved, but privacy security and compliance risk increase
Solution Approach 1:
The system performs preliminary identification of PII data elements before data is stored or processed. By defining rules that map URL patterns to JSON data mappings and using regex patterns to identify PII, the system proactively marks sensitive data for obfuscation before it can be exposed or misused, thus maintaining data functionality while preventing security risks
Solution Approach 2:
The proxy server acts as an intermediary between the web application and the data storage/processing systems. It intercepts data flows, applies obfuscation rules dynamically, and returns modified data to applications. This intermediary layer enables data functionality to continue while systematically protecting privacy security through automated PII identification and obfuscation
2Measurement precision
If PII data is processed and stored in detail, then data accuracy and application performance are improved, but compliance with data protection regulations becomes more difficult
Solution Approach 1:
The system applies different quality treatments to different parts of the data based on sensitivity. PII data elements are identified using regex patterns and mapped to specific obfuscation rules, receiving localized obfuscation treatment (such as masking or replacement) while non-PII data retains its full accuracy and detail, thus maintaining overall data accuracy while ensuring compliance
3Object-affected harmful factors
If real-time PII identification and obfuscation is implemented, then privacy protection is improved, but system complexity and processing overhead increase
Solution Approach 1:
The system performs preliminary configuration of obfuscation rules that map URL patterns to JSON data mappings and define regex patterns for PII identification. This upfront rule definition enables the proxy to make quick pattern-matching decisions in real-time without complex analysis, thus providing strong privacy protection while keeping real-time processing overhead manageable
Solution Approach 2:
The system implements a rule-based feedback mechanism where the proxy continuously monitors data flows, applies obfuscation rules, and logs obfuscation events. This feedback loop enables automated adaptation and optimization of privacy protection without requiring complex real-time decision-making, balancing privacy protection with system simplicity
4Reliability
If comprehensive PII obfuscation rules are applied, then data security is improved, but data processing time and computational resources increase
Solution Approach 1:
The system applies obfuscation rules selectively based on pattern matching rather than processing all data uniformly. By defining specific URL patterns and JSON data mappings that correspond to PII elements, the proxy applies obfuscation only where needed (partial action) rather than to entire data sets, thus maintaining strong data security while minimizing processing time and computational overhead
Data Source
AI summary
A method, including defining rules for protecting sensitive data, each of the rules including a reference URL and a reference JSON data mapping to an item of the sensitive data in a JSON payload. A proxy receives, from an application executing on a host computer, a query including a URL for data hosted by a server, and forwards the URL to the server. The proxy receives, from the server, a response to the forwarded URL, the response including a set of values stored in respective mappings. The URL and the mappings in the response are compared to the rules; and upon detecting a match between a given rule and a combination including the URL and a given mapping in the response, the proxy anonymizes by the proxy, the value stored at the given mapping in the response, and forwards the response, including the anonymized value, to the software application.