Asynchronous Snapshot Replication Under Intrusion Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distributed storage systems lack effective mechanisms to manage data replication in the presence of potential intrusions, leading to potential data corruption or loss, especially when intrusion alerts result in unnecessary system shutdowns or delays.
Innovation Solution
Implementing an asynchronous replication manager that pauses data transmission to a secondary storage system upon intrusion detection, allowing continued data bucket collection, generates an alert, and resumes transmission based on confirmation of the intrusion, or stops data collection entirely if the intrusion is confirmed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data transmission is stopped immediately upon intrusion detection, then data corruption risk is reduced, but system availability and replication efficiency deteriorate due to false positives
Solution Approach 1:
The system performs preliminary actions by continuing to collect data buckets even after stopping transmission upon intrusion detection. This allows the system to prepare recovery data in advance, so that when the intrusion is confirmed to be a false positive, replication can resume quickly without data loss. This resolves the contradiction by preparing for both scenarios (true intrusion and false positive) simultaneously.
Solution Approach 2:
The system dynamically adjusts its operation based on intrusion confirmation status. When intrusion is detected, transmission stops but collection continues. When false positive is confirmed, collection resumes immediately. When true intrusion is confirmed, the system transitions to recovery mode. This dynamic behavior allows the system to optimize between data integrity and replication efficiency based on real-time conditions.
2Reliability
If system shutdown is implemented upon intrusion alert, then security is improved, but system availability deteriorates due to unnecessary shutdowns from false positives
Solution Approach 1:
Instead of implementing full system shutdown upon intrusion alert, the system applies partial action by stopping only the data transmission component while maintaining data bucket collection. This selective approach provides security by preventing potential data corruption during transmission, while maintaining availability by keeping the collection function running and ready for quick resumption if the alert is a false positive.
3Reliability
If data collection continues after stopping transmission, then recovery capability is improved for false positives, but complexity of intrusion response management increases
Solution Approach 1:
The system segments the data replication process into two independent functions: data bucket collection and data transmission. This segmentation allows each function to be controlled independently based on intrusion status. The collection function continues running to maintain recovery capability, while the transmission function stops to prevent data corruption. This segmentation simplifies intrusion response management by providing clear, separate control paths for each function.
Data Source
AI summary
A method for use in a storage system including a primary storage system and a secondary storage system, the method comprising: starting an asynchronous replication manager; detecting that an intrusion detector has detected an intrusion in the primary storage system; in response to the intrusion being detected, causing the asynchronous replication manager to stop transmission, to a secondary storage system, of replication data associated with any data buckets that are collected by the asynchronous replication manager while allowing the asynchronous replication manager to continue collecting new data buckets; generating an alert that indicates that the intrusion detector has detected the intrusion; receiving a response that is indicative of whether the intrusion is confirmed; when the response indicates that the intrusion is not confirmed, resuming the asynchronous replication manager, and when the intrusion is confirmed, causing the asynchronous replication manager to stop collecting data buckets.