Storage Device Secure Erase Prevention Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods fail to prevent accidental or unintentional erasure of data on storage devices during the data copy or ingest process before the data is verified, leading to potential loss of content.
Innovation Solution
A hardware and software system that includes a detection module to identify the history of a storage device using a unique identifier, preventing secure erase or sanitize operations until data is copied and verified through a checksum mechanism, with optional user override for secure erasure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If secure erase or sanitize functionality is provided on a storage device, then data security is improved, but the risk of accidental erasure increases
Solution Approach 1:
The system performs preliminary actions by checking whether data has been successfully copied and verified before enabling the secure erase function. The detection module verifies data integrity through checksum comparison, and only after successful verification does the enable module activate the secure erase capability. This prevents accidental erasure by ensuring data is safely backed up first.
Solution Approach 2:
The system implements feedback mechanisms where the detection module continuously monitors data copy status and provides feedback to the enable module. The checksum verification process creates a feedback loop that confirms data integrity before allowing secure erase operations, thereby preventing accidental data loss while maintaining security functionality.
2Reliability
If data copy and verification process is implemented, then data integrity is improved, but operation complexity increases
Solution Approach 1:
The patent introduces an intermediary detection module that mediates between the data copy process and the secure erase function. This intermediary component handles the checksum verification and status monitoring, simplifying the overall system architecture by separating the verification function from the erase function. The detection module acts as a gateway that enables or disables the secure erase based on verification status.
Solution Approach 2:
The system implements self-service verification where the detection module automatically monitors data copy status and performs checksum comparisons without requiring manual intervention. The system self-manages the verification process and automatically enables or disables secure erase functionality based on the verification outcome, reducing operational complexity while maintaining data integrity.
3Reliability
If automatic disable of erasure functionality is implemented, then unintentional data loss is prevented, but user flexibility is reduced
Solution Approach 1:
The system dynamically adjusts the secure erase functionality based on real-time data copy status. The enable module continuously monitors verification status and automatically enables or disables the secure erase function accordingly. This dynamic behavior prevents unintentional data loss when data is present while allowing user flexibility when data has been successfully verified and copied.
Data Source
AI summary
An integrated hardware and software system detects and prevents accidental secure erase on a storage device. It includes a detection engine using a unique identifier on the storage device to identify if the information stored on the storage unit has been previously copied before allowing performance of secure erase on such storage device. When it is detected that the data has not been copied and verified, the system automatically blocks the secure erase function if enabled in the software application component. The system keeps track of the storage device history to be aware that the last function on the storage device, based on its unique identifier, was a secure erase so that the next time it detects data on the storage device, it is aware that this data is new data; not copied and checksum verified while triggering the disabling of the secure erase software component functionality.