Database Backup Segmentation for Cybersecurity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In database management systems, the risk of cyber-attackers deleting essential backups is high due to the complexity of modern systems, which can lead to the deletion of all backups, including those of other customers, compromising service-level agreements for high availability databases.
Innovation Solution
Implementing a system where a database management system node can write and read from external storage but not delete information, while a separate backup housekeeping component, independent of the node, retrieves and deletes backup objects based on defined requirements, ensuring secure, automatic, and accurate management of backups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the database management system node manages backups independently (write, read, and delete), then the ease of operation is improved, but the reliability deteriorates due to cyber-attack risk
Solution Approach 1:
The backup management system is segmented into three distinct components with separate permissions: the database management system node (write and read only), the backup housekeeping component (delete only), and the external storage component. This segmentation ensures that no single component has full control, thereby improving reliability while maintaining operational ease through defined role separation.
Solution Approach 2:
The backup housekeeping component acts as an intermediary between the database management system node and the external storage component. It retrieves backup requirement information from the database node, determines which backups should be deleted based on retention policies, and performs deletion operations. This intermediary layer prevents direct deletion access from the database node, enhancing security while maintaining automated backup management.
2Productivity
If the database management system node can delete backups, then the productivity is improved, but the object-affected harmful factors worsen due to potential unauthorized deletion
Solution Approach 1:
Different components are assigned different local qualities or permissions regarding backup operations. The database management system node has write and read capabilities but lacks delete permission. The backup housekeeping component has delete permission but cannot write or read backup data directly. This localized permission assignment maintains productivity through automated management while eliminating the harmful factor of unauthorized deletion by the database node.
Solution Approach 2:
The system implements preliminary anti-action by pre-configuring the database management system node without delete permissions on backup objects. Before any deletion can occur, the backup housekeeping component must retrieve backup requirement information from the database node and execute the deletion through controlled access. This preliminary restriction prevents harmful unauthorized deletions while maintaining efficient automated backup management.
Data Source
AI summary
A system to manage database management system backup objects may include an external storage component storing a first database management system backup object. A database management system node (e.g., associated with a database as a service cluster of a hyper-scalar infrastructure) may be configured to write information to and read information from the external storage component without being able to delete information in the external storage component. A backup housekeeping component, independent of the database management system node, may trigger a request to retrieve backup requirement information (e.g., associated with a maximum backup age, a latest backup identifier, an indication of a newest backup to be deleted, etc.) from the database management system node. The backup housekeeping component may then delete all database management system backup objects in the external storage component that are no longer required, including the first database management object, based on the retrieved backup requirement information.