Cloud Data Protection Service Centralizing Compliance Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software systems face challenges in managing data protection and privacy compliance across multiple countries, leading to redundant efforts, increased maintenance costs, and the risk of non-compliance due to hardcoded data protection rules that require code-refactoring and rebuilding.
Innovation Solution
A cloud platform system that registers target systems as consumer services, receives retention rule information, creates corresponding rules, and invokes them to extract and manage data according to specific retention requirements, reducing the need for redundant efforts and enabling compliance with country-specific regulations through a unified data protection and privacy framework.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data protection rules are hardcoded in each service application, then each service can independently enforce DPP compliance, but this leads to redundant efforts across the platform and increased maintenance costs requiring code-refactoring and rebuilding
Solution Approach 1:
The patent extracts data protection and privacy rules from individual service applications and consolidates them into a separate, dedicated DPP service. This allows the rules to be managed independently as configurable parameters rather than hardcoded code, eliminating the need for code-refactoring when rules need to be updated. The DPP service can be updated without rebuilding other applications, thus reducing maintenance complexity while maintaining compliance enforcement.
Solution Approach 2:
The patent creates a universal DPP service that can serve multiple consumer services across the entire cloud platform through a standardized API interface. Instead of each service having its own hardcoded rules, the universal DPP service provides compliance enforcement to all services, eliminating redundant efforts and reducing overall platform complexity while maintaining reliable DPP compliance across all services.
2Ease of operation
If each service on the cloud platform builds its own DPP module, then each service can enforce data protection rules independently, but this necessitates significant redundant and replicated effort across the platform
Solution Approach 1:
The patent merges the DPP enforcement capability from multiple individual service modules into a single centralized DPP service. This consolidated service maintains the ability to enforce rules independently for each consumer service through the API interface, but eliminates the redundant development effort of creating separate DPP modules in each service. The unified approach improves development efficiency while preserving independent rule enforcement capabilities.
Solution Approach 2:
The patent introduces a standardized API interface as an intermediary between consumer services and the DPP service. This intermediary allows services to maintain ease of operation by independently configuring and enforcing their own DPP rules through the API, while the backend DPP service consolidates the actual rule management logic. This eliminates redundant development effort while preserving service independence.
3Reliability
If hardcoded DPP rules are used in existing software systems, then DPP compliance can be enforced within those systems, but management of such rules requires code-refactoring and rebuilding of the application leading to additional maintenance cost
Solution Approach 1:
The patent transforms DPP rules from static hardcoded code into dynamic configurable parameters that can be modified without code changes. The DPP service allows rules to be updated, added, or removed through configuration interfaces and API calls, enabling flexible rule management. This dynamic approach maintains reliable DPP compliance while eliminating the need for code-refactoring and rebuilding, significantly reducing maintenance costs.
Data Source
AI summary
A retention service registers a target system as a consumer service. A cloud platform provides services to each of multiple consumer service. Retention rule information about the target system is received and reflects a data retention requirement. A rule is created that corresponds to the data retention requirement. A configuration is defined that specifies recurring future invocations of the rule. The rule is invoked per the configuration and a query is sent to the target system, the query configured to extract data. Extracted data is received and the rule is applied thereto. An action specified by the rule is taken with regard to the data.