Security enhanced database design method based on storage object separation mechanism

Abstract

The invention discloses a security enhanced database design method based on a storage object separation mechanism, which comprises the following steps of: firstly, installing and configuring a proper database management system according to the data type of a storage object, and then creating an independent database and a corresponding data table structure for each storage object; according to the method, sensitive data and non-sensitive data are physically isolated, the risk of data leakage is effectively reduced, strict role access control authority is set, it is ensured that only authorized users can access the sensitive data, and meanwhile, a reasonable data backup strategy is formulated according to different types of data tables; and finally, connecting the separately stored databases with a back-end service to form efficient sharing and safe utilization of data between the systems. According to the method, the resource utilization rate and the management efficiency are remarkably optimized while the data security is improved.

Description

Technical Field

[0001] The present invention belongs to the field of database design and information security, and relates to a database design method for improving data security through a storage object separation mechanism. Background Art

[0002] With the widespread application of information systems in finance, healthcare, intelligent manufacturing and other fields, the demand for data security and access control is increasing, especially in the context of rapid expansion of data scale and widespread application of deep learning. Traditional database designs usually store all data objects in the same database, lacking isolation and refined management of different types of data. This design allows sensitive data to coexist with non-sensitive data, significantly increasing the risk of data leakage and unauthorized access. Although existing security measures such as access control and data encryption can ensure data security to a certain extent, they still cannot effectively protect against internal threats and advanced persistent attacks. Especially in an environment where both basic system data and deep learning processing data are stored, once the traditional single database storage method is hacked, all data will face the same security risk, making it difficult to meet high security requirements.

[0003] In addition, current database management and maintenance methods have not been optimized for the specific needs of different data types, resulting in problems such as insufficient resource utilization and inefficient management. Summary of the Invention

[0004] In response to the deficiencies in the prior art, the purpose of the present invention is to provide a security-enhanced database design method based on a storage object separation mechanism. This method selects an appropriate database management system according to the data type of the storage object, separates and stores storage objects of different data types, creates corresponding databases and data tables, and sets access permissions and data backups for each data table, thereby achieving independent management of different types of data. This design can effectively reduce the risk of data leakage, improve the overall security of the database and the flexibility of access control, while optimizing resource management efficiency.

[0005] In order to solve the above technical problems, the present invention adopts the following technical solutions:

[0006] A security-enhanced database design method based on a storage object separation mechanism includes the following steps:

[0007] S1: Select the same or different database management systems for different storage objects based on the data structure, access frequency, data volume, and business needs. Once the database management system is determined, install and configure a cloud server or local server to provide the foundation for separate storage.

[0008] S2: In the selected database management system, create an independent database and corresponding data table for each storage object based on the separation mechanism, and import different storage objects into the data table separately. By setting up independent databases for different data types and storing them separately, the physical separation of sensitive data and non-sensitive data is achieved, reducing the risk of data leakage;

[0009] S3 connects the databases of different storage objects that are stored separately with back-end services, enabling efficient sharing and secure use of data between systems.

[0010] The present invention also includes the following technical features:

[0011] Specifically, the storage objects include:

[0012] Storage object I: system basic data;

[0013] Storing Objects II: Deep Learning to Analyze Data.

[0014] Specifically, the types of database management systems include:

[0015] Relational databases: MySQL, PostgreSQL, Oracle databases;

[0016] Non-relational databases: NoSQL, MongoDB, Cassandra, and Elasticsearch databases;

[0017] Time series database: InfluxDB database;

[0018] Data warehouse: Snowflake, BigQuery database.

[0019] Specifically, the S1 includes:

[0020] Step S101: Identify and classify the data types of storage objects, determine the degree of structure of different storage objects, analyze the appropriate database management system, and further confirm the sensitivity and usage requirements of the storage object data;

[0021] Step S102, selecting the database management system type required for each storage object based on the classification result;

[0022] Step S103: Install and configure the selected database management system on the cloud server or local server to ensure the security and efficient operation of the database.

[0023] Specifically, in step S102:

[0024] For storage, choose a relational database that supports structured data, high reliability, and fast query.

[0025] For storage object II, choose a non-relational database with optimized performance and strong scalability;

[0026] Through this detailed classification and reasonable selection of database systems, separate storage of data can be achieved, suitable storage solutions can be provided for different types of data, and the security of the overall system, the flexibility of data management and the efficiency of resource utilization can be improved.

[0027] Specifically, the S2 includes:

[0028] Step S201: creating independent databases for different storage objects in a database management system;

[0029] Step S202: After the independent database is created, corresponding data tables are created in the databases of different storage objects;

[0030] Step S203: Configure multi-level access control permissions for the data tables in the independent database. Design a reasonable permission classification mechanism based on the sensitivity and usage requirements of the stored objects. Based on the role-based access control model, set strict permissions on the database to ensure that only authorized users can access sensitive data.

[0031] Step S204: import the storage objects into corresponding data tables in the database of the corresponding storage objects according to their data types and storage requirements;

[0032] Step S205 : To ensure that the data tables in the database can continue to operate stably, an effective data backup strategy is configured based on the structured degree, access frequency, data volume, and business requirements of the storage object data.

[0033] Specifically, in step S201:

[0034] Creating a database suitable for storing object I in a relational database management system;

[0035] In a non-relational database management system, a dedicated database is created for storing object II;

[0036] In step S202:

[0037] In the database storing object I, data tables are designed according to the specifications of relational databases, and primary keys, foreign keys, and index structures of the tables are set to ensure efficient storage and access of data;

[0038] In the non-relational database of storage object II, create data tables that conform to its specific data structure and configure appropriate indexes and query mechanisms to meet the needs of fast processing and retrieval of large-scale data;

[0039] In step S204:

[0040] The basic data of the system is stored in the data table corresponding to the database of the storage object 1 to ensure its efficient access and management in the relational database management system;

[0041] Import deep learning analysis data into the data table corresponding to the database of storage object II to utilize the flexibility and scalability of non-relational databases to achieve accurate data management and rapid response.

[0042] Specifically, step S203 includes:

[0043] Step S2031: Identify the data tables, row-level, and column-level data in different storage objects for which user permissions to view, delete, modify, and insert need to be restricted.

[0044] Step S2032: Based on the role-based access control model, different user roles are defined according to specific business needs and user responsibilities, and appropriate permissions are assigned to each role.

[0045] Step S2033: After the roles and permissions are determined, the roles are created in the databases of different storage objects and the permissions of the roles are configured;

[0046] Step S2034: Create user accounts in the databases of different storage objects and set the user's username and password. The administrator assigns the user to an appropriate role based on the user's position and job title.

[0047] Step S2035: When a user initiates an access request, the system automatically determines the user's role and performs permission verification according to the preset access control model;

[0048] Step S2036: Enable the access log record and security audit function of the database to monitor the user's access behavior and permission change records.

[0049] Specifically, step S205 includes:

[0050] Step S2051, clarify the data type and frequency of the separately stored database that needs to be backed up;

[0051] Step S2052: Based on the selected database management system backup method, choose to write an automated script to perform the backup task, or perform manual operation according to system requirements;

[0052] Step S2053: Select appropriate backup strategies for different storage objects. Backup strategies include full backup, incremental backup, and differential backup.

[0053] Step S2054, setting the time and frequency of automatic backup for different storage objects;

[0054] Step S2055, setting storage locations of backup files for different storage objects;

[0055] Step S2056, executing the backup task.

[0056] Specifically, in step S2051:

[0057] For the basic system data in storage object I, the backup frequency is high;

[0058] Deep learning data in storage object II does not need to be frequently backed up;

[0059] In step S2053:

[0060] For storage object I, a full backup strategy is adopted to ensure that each backup contains all data in the database, facilitating rapid recovery in the event of a catastrophic failure;

[0061] For storage object II, an incremental backup strategy is used to back up only the changes since the last backup, which can save storage space and improve backup efficiency;

[0062] In step S2054:

[0063] For storage object I, set up daily backup to ensure that data loss at any time is minimized;

[0064] For Storage Object II, set up daily or weekly backups;

[0065] The specific backup time should be selected during a period when the system is less frequently used to avoid affecting normal business operations.

[0066] Compared with the prior art, the present invention has the following technical effects:

[0067] In response to various potential security threats, the present invention proposes a more secure and reliable database design solution, namely a security-enhanced database design method based on a storage object separation mechanism. This method significantly reduces the risk of sensitive data exposure by physically separating storage objects, effectively preventing data leakage and illegal access. At the same time, the corresponding database management system is selected according to the characteristics of the data type, which improves resource utilization and management efficiency and enhances the flexibility of the back-end service system. In addition, setting access control permissions for each data table based on roles makes data access more secure, ensuring that only authorized users can access sensitive information, and designing independent backup strategies for separated storage objects to ensure data security at the physical and logical levels. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1It is an overall structural diagram of the security-enhanced database design method based on the storage object separation mechanism according to an embodiment of the present invention.

[0069] Figure 2 It is a flow chart of step S1 of an embodiment of the present invention.

[0070] Figure 3 It is a detailed schematic diagram of the storage object separation mechanism according to an embodiment of the present invention.

[0071] Figure 4 This is a flow chart of setting multi-level access control in an embodiment of the present invention.

[0072] Figure 5 Detailed diagram of data backup configuration according to an embodiment of the present invention. DETAILED DESCRIPTION

[0073] Specific embodiments of the present invention are given below. It should be noted that the present invention is not limited to the following specific embodiments, and all equivalent modifications made on the basis of the technical solution of this application fall within the protection scope of the present invention.

[0074] Example:

[0075] This embodiment provides a security-enhanced database design method based on a storage object separation mechanism. Figure 1 , shows the overall structure of the security-enhanced database design method based on the storage object separation mechanism provided by this embodiment. This method is applicable to database design for various programs, applications, or systems, and specifically includes the following steps:

[0076] S1: Based on the degree of structuring, access frequency, data volume, and business needs of the storage object data, select the same or different database management systems for different storage object data. After determining the database management system, install and configure a cloud server or local server to provide a basis for separate storage. When selecting a cloud server, users can use the cloud service provider's management tools to quickly deploy the required database instance. When selecting a local server, users need to consider hardware configuration and operating system compatibility, and manually install and configure the database software.

[0077] In this embodiment, the storage objects include storage object I and storage object II, where storage object I is the basic system data and storage object II is the deep learning analysis data. The two storage objects can be stored in the same database management system or in different database management systems.

[0078] Storage objects can be structured, unstructured, or semi-structured, depending on the degree of data structure. For structured data, such as user information and transaction records, relational databases (such as MySQL, PostgreSQL, or Oracle) are more suitable, as they provide strong query and transaction support. For unstructured or semi-structured data, such as log files, documents, or social media content, non-relational databases (such as MongoDB, Cassandra, or Elasticsearch) offer greater flexibility and adaptability.

[0079] Business needs for storing object data, including those for real-time data analysis or streaming data, require the selection of specialized time-series databases (such as InfluxDB) or data warehouses (such as Snowflake or BigQuery) to optimize data processing efficiency and performance.

[0080] like Figure 2 , S1 specifically includes:

[0081] In step S101, to achieve separate storage, the data types of the storage objects are first identified and classified, the degree of structuring of different storage objects, i.e., storage object I and storage object II, is determined, and the appropriate database management system is analyzed. At the same time, the sensitivity and usage requirements of the storage object data are further confirmed.

[0082] In step S102, the database management system (DBMS) type required for each storage object is selected based on the classification results. For storage object I, a relational database (such as MySQL) that supports structured data, high reliability, and fast queries can be selected. For storage object II, a non-relational database (such as a NoSQL database) with optimized performance and strong scalability is suitable to accommodate large-scale data processing needs and flexible structure requirements. This detailed classification and appropriate selection of database systems allows for separate data storage, providing more suitable storage solutions for different data types, thereby improving overall system security, data management flexibility, and resource utilization efficiency.

[0083] Step S103: Install and configure the selected database management system on a cloud server or local server to ensure database security and efficient operation. Appropriate server resources and hardware configurations, such as CPU, memory, storage space, and network bandwidth, are selected based on application requirements and data processing volume. Next, download the installation package for the selected database management system according to its instructions and begin deployment, ensuring its version is compatible with the server operating system.

[0084] S2: Within the selected database management system, separate databases and corresponding data tables are created for each type of storage object data based on a separation mechanism. Different storage object data is then imported into the tables separately. This process not only ensures effective organization and management of storage object data but also improves data security. By setting up independent databases for different data types and storing them separately, sensitive data can be physically separated from non-sensitive data, effectively reducing the risk of data leakage.

[0085] like Figure 3 , is a detailed diagram of a storage object separation mechanism according to an embodiment of the present invention. This mechanism physically separates storage objects, storing different data types in independent databases or storage units to effectively improve data security and management efficiency. Specifically, it includes the following steps:

[0086] Step S201, in the database management system, create independent databases for different types of storage objects to achieve efficient separate management of data; in this embodiment, first, create a database suitable for storage object I in the relational database management system, and secondly, create a dedicated database for storage object II in the non-relational database management system.

[0087] In step S202, after the two independent databases are created, corresponding data tables are created in the databases of different storage objects, namely, storage object I and storage object II. In this embodiment, in the database of storage object I, data tables are designed according to relational database specifications, and primary keys, foreign keys, and index structures are set to ensure efficient data storage and access. In the non-relational database of storage object II, data sets or tables that conform to its specific data structure are created, and appropriate indexing and query mechanisms are configured to meet the requirements for rapid processing and retrieval of large amounts of data.

[0088] In step S203, multi-level access control permissions are configured for the data tables in the two independent databases to enhance data security and refined access management. A reasonable permission grading mechanism is designed based on the sensitivity and usage requirements of the stored objects. Based on the role-based access control (RBAC) model, strict permissions are set for the databases to ensure that only authorized users can access sensitive data. By setting access permissions for different roles (e.g., administrator, ordinary user, guest), data security and controllability are ensured.

[0089] Specifically, after the database and data tables are created, it is necessary to set corresponding multi-level access control permissions for each data table based on the sensitivity and access requirements of the data. First, when designing access control permissions, the data stored in the data table should be classified to identify which data is sensitive information. Then, different user roles should be defined and the corresponding access permissions should be assigned to them based on actual needs. When setting up access control, a role-based access control (RBAC) model is adopted. Through this model, users are assigned to different roles, and their access to data is controlled according to the permissions defined by the role. This process is crucial because it ensures that only authorized user roles can access sensitive data, thereby effectively protecting the confidentiality and integrity of the data.

[0090] More specifically, according to steps S101, S102, and S103, the storage objects are stored separately. Through the coordination of the above three steps, the separate storage of different types of data is achieved, and the storage object I and storage object II are respectively stored in the database that is most suitable for them, thereby improving the management efficiency of data storage, the security of the system, and the performance of subsequent data processing. According to steps S201 and S202, the databases and corresponding data tables for storage object I and storage object II are created respectively. Figure 4 , is a flowchart of how to set up multi-level access control in an embodiment of the present invention. This flowchart illustrates the specific steps and methods for implementing multi-level access control in a database management system, ensuring that users of different levels can only access authorized data while protecting the security and integrity of sensitive data. The specific steps are as follows:

[0091] In step S2031, before setting access control permissions for the database, it is necessary to first identify the data tables, rows, and columns within different storage objects (i.e., Storage Object I and Storage Object II) for which user permissions such as viewing, deletion, modification, and insertion must be restricted. This process involves analyzing data sensitivity, identifying which data is critical to business operations, which data contains sensitive information or personal privacy, and which data modification may pose system risks. Therefore, it is necessary to first categorize the various types of stored data so that appropriate permission control models can be configured for different data tiers.

[0092] Step S2032: The role-based access control (RBAC) model defines different user roles based on specific business needs and user responsibilities, and assigns appropriate permissions to each role. In this step, the system divides roles based on the user's position and responsibilities within the organization, as well as the type of data they need to access. For example, an administrator role may have full access to all data, including modification and deletion; a regular user role may be limited to viewing data; and a guest role may only have read-only permissions. This role division ensures that data access control closely matches the organizational structure, avoiding unnecessary excessive granting of permissions.

[0093] In step S2033, after determining the roles and permissions, roles are created and their permissions are configured in the databases of different storage objects, namely, Storage Object I and Storage Object II. The core of this step is to simplify permission management by integrating user permissions with specific business needs through role mapping. When creating roles, the database administrator will configure the corresponding data access permissions based on each role's permission requirements, including which data tables can be accessed, which columns and rows can be queried, and whether new data can be inserted or existing data can be modified. In this way, the system can efficiently manage role permissions and ensure the accuracy and consistency of permission allocation.

[0094] In step S2034, user accounts are created in the databases for the different storage objects, Storage Object I and Storage Object II, and user names and passwords are set. Based on the user's position and job title, the administrator assigns the user to the appropriate role. During this process, each user's permissions are indirectly granted through their role. By setting user access permissions, the administrator ensures that users can only access data relevant to their work and avoid accessing sensitive or unauthorized data.

[0095] In step S2035, when a user initiates an access request, the system automatically determines the user's role and performs permission verification based on the pre-defined access control model (RBAC). The system checks the user's identity information and compares it with their role permissions to ensure that the user can access the resources permitted by their role. If the user's requested operation exceeds their permissions, the system will deny the operation and return an error message, ensuring system security and data protection.

[0096] In step S2036, the database access logging and security auditing functions are enabled to monitor user access behavior and permission change records. By enabling the logging function, the system can record each user's operation history, including data access, modification, and deletion operations, and generate audit reports. These logs are crucial for subsequent data security monitoring, helping system administrators promptly identify abnormal behavior, trace potential security threats, and provide a basis for compliance reviews.

[0097] In step S204, the storage objects are imported into the corresponding data tables in the database of the corresponding storage object, based on their data types and storage requirements. In this embodiment, data such as basic system data is stored in the corresponding data tables in the database of storage object I to ensure efficient access and management within the relational database management system. Simultaneously, unstructured or semi-structured data, such as deep learning analysis data, is imported into the corresponding data tables in the database of storage object II, leveraging the flexibility and scalability of non-relational databases to achieve precise data management and rapid response.

[0098] In step S205, to ensure the continued stable operation of the data tables in both databases, an effective data backup strategy is configured based on the structured nature of the stored data, access frequency, data volume, and business requirements. This strategy is customized based on the importance, update frequency, sensitivity, and business needs of the data tables. First, through needs analysis and assessment, key backup requirements are determined. Next, the appropriate backup type is selected to ensure data integrity and reliability. Next, a reasonable backup frequency is set and automated backup tasks are configured. Finally, the most appropriate backup storage method and location are selected to ensure data security and recoverability.

[0099] Specifically, develop a data backup strategy for each data table to ensure data durability and rapid recovery after an outage. The backup strategy should clearly define the frequency and types of backups, including full, incremental, and differential backups. Choosing the appropriate backup type is crucial to ensure smooth data recovery in the event of an issue, and setting appropriate times and frequencies. Furthermore, the storage location for backup data must be clearly defined. This strategy not only helps prevent accidental data loss or corruption but also ensures that business operations can quickly resume normal operations in the event of emergencies such as system failures, hardware damage, or natural disasters.

[0100] More specifically, according to step S204, the relevant data of storage object I and storage object II are input into their respective corresponding database tables. Figure 5 , is a detailed diagram of data backup configuration in accordance with an embodiment of the present invention. Data backup policies are set based on the importance, update frequency, and sensitivity of the data type to ensure data security, integrity, and recoverability. The specific steps are as follows:

[0101] In step S2051, before setting up a data backup strategy, first clarify the data types and frequency required for backup of the two separately stored databases. Based on the frequency of use, importance, and sensitivity of the data, analyze and determine which data tables require backup. For basic system data in Storage Object I, due to its high structural requirements and business dependencies, a higher backup frequency is required. Deep learning data in Storage Object II, on the other hand, requires less frequent backup, but a reasonable backup cycle should be determined based on data update frequency and system requirements.

[0102] In step S2052, depending on the selected database management system backup method, you can choose to write an automated script to perform the backup task, or manually perform the task based on system requirements. For regular and large-scale data backups, scripting is recommended to reduce human error and improve backup efficiency. The backup script can automatically run, regularly backing up the specified database and its tables, and recording information such as the backup time and data volume for subsequent tracking and management.

[0103] Step S2053 selects appropriate backup strategies for different storage objects, namely, storage object I and storage object II. Backup strategies include full backup, incremental backup, and differential backup. When selecting a backup strategy, the data type, business requirements, and the frequency of data changes must be considered. For storage object I, which contains core system data or critical information, a full backup strategy should be adopted. This strategy ensures that each backup includes all data in the database, facilitating rapid recovery in the event of a catastrophic failure. For storage object II, since its data size is typically large and the update frequency may be low, an incremental backup strategy should be adopted. Incremental backup only backs up the changes since the last backup, saving storage space and improving backup efficiency.

[0104] Step S2054, set the time and frequency (for example, daily, weekly, monthly) of automatic backup for different storage objects, namely storage object I and storage object II. The time and frequency of backup should be determined based on the frequency of data updates, business needs, and the importance of the data. For storage object I, whose content is critical business data and is updated frequently, it should be set to daily backup to ensure that data loss at any time can be minimized. For storage object II, which is large-scale deep learning analysis data, the data involves real-time analysis and prediction, and can be set to daily or weekly backup. The specific time for the backup should be selected during a period when the system is less frequently used to avoid affecting normal business operations.

[0105] In step S2055, when setting the storage locations for backup files for different storage objects, namely, Storage Object I and Storage Object II, it is necessary to ensure their security, reliability, and ease of data recovery. Backup files can be stored in a variety of locations, including local backup servers, external storage devices, or cloud storage platforms. The most appropriate storage location can be flexibly selected based on data importance, access requirements, and recovery requirements. If higher access speed and control are required, local backup may be preferred. If disaster recovery and data redundancy are a concern, cloud storage platforms can be selected to ensure data security and recoverability.

[0106] Step S2056: Execute the backup task. After setting the backup strategy, time, frequency, and storage location, the system will automatically execute the backup task according to the preset plan.

[0107] S3: Connect the databases of different separately stored storage objects, namely Storage Object I and Storage Object II, with back-end services, namely the back-end application development system, deep learning analysis system, etc. By establishing stable and efficient interfaces, it is possible to ensure seamless interaction between these databases and back-end services, enabling efficient sharing and secure use of data between systems. This connection allows the back-end application development system to access the data in the database in real time, thereby supporting business logic and user requests. Each separately stored database can be connected to multiple back-end services simultaneously, or individually to specific back-end services to achieve direct data interaction; for example, a storage object with time-series data characteristics can be connected to a deep learning analysis system and a back-end application service, and the deep learning analysis system will synchronize the real-time analysis results to the back-end application service, thereby displaying the analysis results in real time on the front-end.

[0108] Back-end applications can also be integrated with deep learning. This involves connecting one of the storage objects, a database containing large amounts of time-series data, to a deep learning analytics system. By feeding this data into the deep learning model, the system can perform more accurate analysis and predictions. Ultimately, the back-end application can display the analytical results generated by the deep learning model, further improving decision-making accuracy and business response speed, while enabling efficient data sharing and secure utilization across systems.

[0109] Specifically, first, configure the databases of Storage Objects I and II to connect with the back-end application to ensure smooth data transfer from the database to the front-end page. Simultaneously, connect the database of Storage Object II to the deep learning analysis system to enable efficient data transmission and analysis. This connection enables the system to leverage the massive amount of data in Storage Object II for training, prediction, and result analysis, providing strong data-driven support for business decision-making. Furthermore, the analysis results can be displayed on the front-end through the back-end application, providing users with intuitive data visualization.

[0110] In summary, the embodiments of the present invention provide a security-enhanced database design method based on a storage object separation mechanism. By physically isolating different types of data storage objects, this method significantly improves the security of data storage and the flexibility of management. At the same time, a multi-level access control mechanism is introduced in each database instance, and hierarchical management is performed according to user roles, permission levels and data sensitivity to ensure that only authorized users can access the corresponding data objects, thereby further strengthening the security protection of the system. In addition, to prevent the risk of data loss or damage, the method designs an independent data backup strategy for each data storage object to ensure a high level of data security and reliability during storage, access and recovery, and can meet the needs of data security and business continuity in complex application scenarios.

[0111] In the embodiments provided herein, storage objects can be divided into multiple types, not limited to the two data types of Storage Object I and Storage Object II. When processing multiple storage objects, multiple database management systems can be employed, or a single database management system can be used. Ultimately, different types of data must be stored separately to achieve more efficient database management. For example, business data and real-time data can be stored in the same database management system, with independent database instances created for each. Multi-level access control and data backup policies can then be set for each database, thereby enhancing data security and management flexibility.

[0112] The preferred embodiments of the present invention are described in detail above in conjunction with the accompanying drawings. However, the present invention is not limited to the specific details in the above embodiments. Within the technical concept of the present invention, various simple modifications can be made to the technical solution of the present invention, and these simple modifications all fall within the scope of protection of the present invention.

[0113] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction. To avoid unnecessary repetition, the present invention will not further describe various possible combinations.

[0114] In addition, the various embodiments of the present invention may be arbitrarily combined, and as long as they do not violate the concept of the present invention, they should also be regarded as the contents disclosed by the present invention.

Claims

1. A security-enhanced database design method based on a storage object separation mechanism, characterized in that: The following steps are involved: S1: Select the same or different database management systems for different storage objects based on the data structure, access frequency, data volume, and business needs. Once the database management system is determined, install and configure a cloud server or local server to provide the foundation for separate storage. S2: In the selected database management system, create an independent database and corresponding data table for each storage object based on the separation mechanism, and import different storage objects into the data table separately. By setting up independent databases for different data types and storing them separately, the physical separation of sensitive data and non-sensitive data is achieved, reducing the risk of data leakage; S3 connects the databases of different storage objects that are stored separately with back-end services, enabling efficient sharing and secure use of data between systems.

2. The security-enhanced database design method based on the storage object separation mechanism according to claim 1, characterized in that: The storage objects include: Storage object I: system basic data; Storing Objects II: Deep Learning to Analyze Data.

3. The security-enhanced database design method based on the storage object separation mechanism according to claim 2, characterized in that: The types of database management systems include: Relational databases: MySQL, PostgreSQL, Oracle databases; Non-relational databases: NoSQL, MongoDB, Cassandra, and Elasticsearch databases; Time series database: InfluxDB database; Data warehouse: Snowflake, BigQuery database.

4. The security-enhanced database design method based on the storage object separation mechanism according to claim 3, characterized in that: Said S1 comprises: Step S101: Identify and classify the data types of storage objects, determine the degree of structure of different storage objects, analyze the appropriate database management system, and further confirm the sensitivity and usage requirements of the storage object data; Step S102, selecting the database management system type required for each storage object based on the classification result; Step S103: Install and configure the selected database management system on the cloud server or local server to ensure the security and efficient operation of the database.

5. The security-enhanced database design method based on the storage object separation mechanism according to claim 4, characterized in that: In step S102: For storage, choose a relational database that supports structured data, high reliability, and fast query. For storage object II, choose a non-relational database with optimized performance and strong scalability; Through this detailed classification and reasonable selection of database systems, separate storage of data can be achieved, suitable storage solutions can be provided for different types of data, and the security of the overall system, the flexibility of data management and the efficiency of resource utilization can be improved.

6. The security-enhanced database design method based on the storage object separation mechanism according to claim 3, characterized in that: The S2 includes: Step S201: creating independent databases for different storage objects in a database management system; Step S202: After the independent database is created, corresponding data tables are created in the databases of different storage objects; Step S203: Configure multi-level access control permissions for the data tables in the independent database. Design a reasonable permission classification mechanism based on the sensitivity and usage requirements of the stored objects. Based on the role-based access control model, set strict permissions on the database to ensure that only authorized users can access sensitive data. Step S204: import the storage objects into corresponding data tables in the database of the corresponding storage objects according to their data types and storage requirements; Step S205 : To ensure that the data tables in the database can continue to operate stably, an effective data backup strategy is configured based on the structured degree, access frequency, data volume, and business requirements of the storage object data.

7. The security-enhanced database design method based on the storage object separation mechanism according to claim 6, characterized in that: In step S201: Creating a database suitable for storing object I in a relational database management system; In a non-relational database management system, a dedicated database is created for storing object II; In step S202: In the database storing object I, data tables are designed according to the specifications of relational databases, and primary keys, foreign keys, and index structures of the tables are set to ensure efficient storage and access of data; In the non-relational database of storage object II, create data tables that conform to its specific data structure and configure appropriate indexes and query mechanisms to meet the needs of fast processing and retrieval of large-scale data; In step S204: The basic data of the system is stored in the data table corresponding to the database of the storage object 1 to ensure its efficient access and management in the relational database management system; Import deep learning analysis data into the data table corresponding to the database of storage object II to utilize the flexibility and scalability of non-relational databases to achieve accurate data management and rapid response.

8. The security-enhanced database design method based on the storage object separation mechanism according to claim 6, characterized in that: The step S203 includes: Step S2031: Identify the data tables, row-level, and column-level data in different storage objects for which user permissions to view, delete, modify, and insert need to be restricted. Step S2032: Based on the role-based access control model, different user roles are defined according to specific business needs and user responsibilities, and appropriate permissions are assigned to each role. Step S2033: After the roles and permissions are determined, the roles are created in the databases of different storage objects and the permissions of the roles are configured; Step S2034: Create user accounts in the databases of different storage objects and set the user's username and password. The administrator assigns the user to an appropriate role based on the user's position and job title. Step S2035: When a user initiates an access request, the system automatically determines the user's role and performs permission verification according to the preset access control model; Step S2036: Enable the access log record and security audit function of the database to monitor the user's access behavior and permission change records.

9. The security-enhanced database design method based on the storage object separation mechanism according to claim 6, characterized in that: The step S205 includes: Step S2051, clarify the data type and frequency of the separately stored database that needs to be backed up; Step S2052: Based on the selected database management system backup method, choose to write an automated script to perform the backup task, or perform manual operation according to system requirements; Step S2053: Select appropriate backup strategies for different storage objects. Backup strategies include full backup, incremental backup, and differential backup. Step S2054, setting the time and frequency of automatic backup for different storage objects; Step S2055, setting storage locations of backup files for different storage objects; Step S2056, executing the backup task.

10. The security-enhanced database design method based on the storage object separation mechanism according to claim 9, characterized in that: In step S2051: For the basic system data in storage object I, the backup frequency is high; Deep learning data in storage object II does not need to be frequently backed up; In step S2053: For storage object I, a full backup strategy is adopted to ensure that each backup contains all data in the database, facilitating rapid recovery in the event of a catastrophic failure; For storage object II, an incremental backup strategy is used to back up only the changes since the last backup, which can save storage space and improve backup efficiency; In step S2054: For storage object I, set up daily backup to ensure that data loss at any time is minimized; For Storage Object II, set up daily or weekly backups; The specific backup time should be selected during a period when the system is less frequently used to avoid affecting normal business operations.

Images