Automated Data Syncing Between Security Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for syncing data between security domains face technical drawbacks such as failed continuous integration checks, inconsistencies due to path changes, rejected ontology changes, and the burden of manual data transfer.
Innovation Solution
A computer-implemented method for automated syncing of data between security domains, which involves identifying a dataset to be synced, performing pre-processing to satisfy data transfer restrictions, transferring the pre-processed dataset and associated metadata, and reconstructing the dataset in the target security domain using the metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual data transfer methods are used between security domains, then data can be transferred with security compliance, but the process is burdensome and error-prone
Solution Approach 1:
The system enables automated self-service data synchronization between security domains through configured data pipelines. The origin domain automatically publishes datasets with metadata including path information, and the target domain autonomously consumes and applies these datasets without manual intervention, eliminating manual transfer burdens while maintaining consistency through automated conflict resolution based on path matching rules.
2Adaptability or versatility
If data is transferred between security domains with different security levels, then data accessibility is improved, but data transfer restrictions and security compliance become more complex
Solution Approach 1:
The system segments the data transfer process into distinct automated components: origin domain publishes datasets with embedded path metadata, transfer mechanism segments data into manageable datasets with associated metadata files, and target domain segments the processing into consumption and application phases. This segmentation allows secure cross-domain transfer by handling each segment independently with appropriate security controls while maintaining overall system simplicity through automation.
3Productivity
If automated data synchronization is implemented, then productivity is improved, but handling restrictive data transfer mechanisms becomes more challenging
Solution Approach 1:
The origin domain performs preliminary actions by publishing datasets with embedded path metadata and configuration information before transfer. The metadata files contain pre-configured path information that enables the target domain to automatically resolve and apply datasets without manual path mapping. This preliminary action simplifies the transfer process automation by preparing all necessary information in advance, allowing high-speed automated synchronization that adapts to restrictive transfer mechanisms.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Described herein are systems, methods, and non-transitory computer readable media for automating the transfer/syncing of datasets or other artifacts from one security domain (e.g., a low security side environment) to another security domain (e.g., a high security side environment) in a seamless manner that complies with requirements of a data transfer mechanism used to transfer data between the two security domains while ensuring data integrity and consistency between the two security domains.