Replication Tags for Secure Cross-Partition Dataset Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud computing environments face challenges in efficiently replicating datasets across partitions while adhering to predefined replication policies, leading to potential unauthorized replication and data security risks.
Innovation Solution
The implementation of replication tags that associate datasets with specific destination partitions, verified through destination keys in replication credentials, ensures that datasets are replicated only to authorized partitions, preventing unauthorized replication and enhancing data security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If datasets are replicated across partitions without verification, then replication speed and productivity are improved, but data security and authorization control deteriorate
Solution Approach 1:
The system performs preliminary verification of replication tags and destination keys before executing the replication operation. The source dataset is checked against the replication policy to determine if replication to the requested destination is authorized, preventing unauthorized replication before it occurs
Solution Approach 2:
Replication tags and destination keys act as intermediary verification mechanisms between the source dataset and destination partition. These tags mediate the replication process by encoding authorization information that must be validated before data transfer occurs
2Reliability
If replication policies are strictly enforced with verification, then data security is improved, but replication complexity and processing time increase
Solution Approach 1:
The replication verification process is self-service in that the system automatically checks replication tags and destination keys against stored replication policies without requiring manual intervention. The source dataset itself contains the replication tag information needed for verification, enabling automated security checks
Solution Approach 2:
Replication tags serve multiple functions: they identify the source dataset, encode authorization information, specify destination partitions, and enable verification against replication policies. This multi-functionality reduces the need for separate verification mechanisms and simplifies the overall process
3Reliability
If replication tags are verified against destination keys, then unauthorized replication is prevented, but processing overhead increases
Solution Approach 1:
The system uses destination keys that are copies or representations of the actual destination partition identifiers. By verifying against these key copies rather than performing complex destination validations, the system achieves authorization control with minimal processing overhead
Data Source
AI summary
A system receives a request to generate a replication policy that allows replication of a dataset to a first partition of a cloud environment from a data repository located in a second partition of the cloud environment. The system generates the replication policy at least by associating the dataset with a replication tag that includes a destination key stored in a data structure for verifying replication requests. The destination key identifies one or more partitions of the cloud environment, including the first partition, where replication of the dataset is allowed. The system includes a set of executable instructions that implement the replication policy at least by allowing replication of the dataset to the first partition contingent upon verifying that a replication credential, associated with a replication request to replicate the dataset to the first partition, corresponds to the destination key of the replication tag.