WORM Logical Containers for Unmodifiable Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data storage systems lack the functionality to persistently store data without modification or tampering, which is required by regulations such as those for banking statements, and scaling these systems to meet organizational needs is costly and inefficient.
Innovation Solution
An object-based data storage system that allows for the creation of WORM (Write Once Read Many) logical data containers, where data objects can be stored with an expiration date, preventing modification or deletion until the expiration date has passed, and automatically deleting data after that date, thereby ensuring data integrity and reducing the need for additional hardware.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional data storage systems are used, then data can be stored, but the data cannot be guaranteed to remain unmodified or untampered with over time
Solution Approach 1:
The system dynamically changes the accessibility and modifiability of data over time. Data objects transition from a locked state (unmodifiable) to an unlocked state (modifiable) based on temporal conditions. This is achieved through version control mechanisms where data is locked upon creation or upload, and can only be modified when a newer version supersedes it, ensuring regulatory compliance while maintaining data integrity throughout its lifecycle
Solution Approach 2:
The system performs preliminary actions by pre-establishing data locking and versioning rules at the time of data creation or upload. Data objects are immediately locked and assigned version identifiers, preventing any subsequent modification unless proper versioning protocols are followed. This preliminary configuration ensures that data integrity is maintained from the outset without requiring continuous intervention
2Reliability
If specifically configured WORM storage devices are used to prevent data modification, then data integrity is ensured, but the system becomes difficult to scale and requires additional hardware costs
Solution Approach 1:
The system makes conventional data storage systems universal by implementing software-based WORM capabilities that can be applied to any data object in the storage system. Instead of requiring specialized hardware, the version control and data locking mechanisms work across all data types and storage locations, allowing the same infrastructure to serve both regular and compliance-critical storage needs, thereby eliminating the need for separate dedicated WORM devices
Solution Approach 2:
The system creates logical copies of data through versioning rather than requiring physical duplication of hardware. When data needs to be preserved, the system maintains the original locked version and creates new version identifiers for any subsequent data, allowing multiple instances of data protection without duplicating the underlying storage infrastructure. This virtualization approach enables scaling without proportional increases in hardware complexity
3Extent of automation
If data is stored in a WORM logical data container with expiration date, then automatic deletion after expiration prevents manual intervention errors, but the system must track and manage expiration dates for all data objects
Solution Approach 1:
The system implements self-service through automated expiration date tracking and enforcement. Data objects automatically carry their expiration date metadata, and the system autonomously identifies and deletes expired data without requiring manual intervention or complex external management processes. The version control infrastructure itself manages the expiration logic, making the system self-regulating and reducing operational overhead
Data Source
AI summary
An object-based data storage system receives a request to create a logical data container subject to a condition that data objects are to be unmodifiable until after a specified amount of time has transpired. During the amount of time, the object-based data storage system may deny any requests to modify the data objects stored in the logical data container while allowing read-only access to the data objects. After the amount of time has transpired, the object-based data storage system may be configured to allow a customer to modify or delete any data objects stored within the logical data container. Alternatively, the object-based data storage system may be configured to delete the data objects automatically after the amount of time has transpired for the data objects.