Air-Gapped Vault Log Transfer via Replication Streams
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Air-gapped vault systems are unable to communicate support logs and diagnostic reports to external systems due to the air gap, making it difficult to monitor and analyze them effectively, and introducing security vulnerabilities if direct communication is allowed.
Innovation Solution
Utilize the existing replication stream between the source and destination systems to piggyback logs and reports from the air-gapped vault to the source, using a Pickup-Send-Phase and Pickup-Receive-Phase to transfer data within the replication process without violating the air gap.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an air gap is maintained to prevent unauthorized access to the vault, then security is improved, but the ability to transfer logs and diagnostic data to external systems deteriorates
Solution Approach 1:
The patent merges the log transfer function with the existing replication stream by allowing the vault to send logs to the source system during the replication process. The replication stream serves dual purposes: both data replication and log transfer, eliminating the need for separate communication channels and maintaining air gap security.
Solution Approach 2:
The replication stream is given multi-functionality by enabling it to carry both replicated data and log information. The same communication channel used for data replication is also utilized for transferring logs and diagnostic reports from the vault to external systems, maximizing the utility of existing infrastructure.
2Loss of information
If a new process is allowed to pass through the air gap to send logs from the vault to external systems, then log transfer capability is improved, but security vulnerability increases
Solution Approach 1:
Instead of creating a new process for log transfer, the patent combines log transfer with the existing replication process. The vault sends logs to the source system during the replication window when the air gap is already temporarily closed for data transfer, avoiding the need for additional air gap openings and associated security risks.
Solution Approach 2:
The source system acts as an intermediary that receives both replicated data and logs during the replication process. The vault communicates logs to the source system through the established replication channel, and the source system then handles log processing and forwarding to external systems, eliminating the need for direct vault-to-external communication.
3Reliability
If the air gap is closed only for replication protocols, then security is maintained, but the ability to monitor and analyze vault systems deteriorates
Solution Approach 1:
The patent combines monitoring data transfer with the replication process by having the vault include logs and diagnostic reports in the data being transferred through the replication stream. This allows comprehensive monitoring capabilities to be achieved during the existing replication window without requiring separate monitoring channels.
Solution Approach 2:
The system implements feedback by transferring logs and diagnostic reports from the vault to the source system through the replication stream. This enables continuous monitoring and analysis of vault system health, performance, and security status, with the source system receiving regular updates on vault operations.
Data Source
AI summary
One example method includes, at a replication data source, initiating a replication process that includes transmitting a replication stream to a replication destination vault, and data in the replication stream is transmitted by way of a closed airgap between the replication data source and the replication destination vault, switching, by the replication data source, from a transmit mode to a receive mode, receiving, at the replication data source, a first checksum of a file, and the first checksum and file were created at the replication destination vault, receiving, at the replication data source, the file, calculating, at the replication data source, a second checksum of the file, and when the second checksum matches the first checksum, ending the replication process.


