Safety management method of hidden area, hidden area file system, equipment and medium

Abstract

The invention relates to the technical field of computers, and discloses a security management method of a hidden area, a hidden area file system, equipment and a medium. The method is used for a hidden area file system and comprises the steps of receiving a target operation request of a target user for a hidden area; verifying the permission of the target user or the permission and the password according to a preset security policy in the security layer; the preset security policy in the security layer is obtained by mapping according to a mandatory access control policy of the security layer; and when the verification is passed, executing the target operation request. According to the technical scheme, the file system is customized by hiding sector formatting, an operation interface independent of a common file system is adopted, a security layer auditing permission mechanism is added, and a specific storage option is added compared with the common file system and a user permission mechanism. The method can effectively prevent the network from attacking the user system, and can effectively prevent the data security attack behavior on key information in the system through the file system after entering the interior to privilege.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a hidden area security management method, a hidden area file system, a device and a medium. Background Art

[0002] Large-scale project delivery is often delivered together with the software and the hardware platform on which it runs, forming a simple and easy-to-use chassis box with a relatively closed operation entrance. This allows all user operations to be within a controllable range, forming a stable human-computer interaction function boundary. At the same time, only the debugging interface for developers is reserved for the system inside the device for maintenance and upgrade.

[0003] In the delivered equipment, the system integrated in the chassis is generally provided with upgrade functions according to the service life provided. However, the protection of core data and applications is generally achieved by closing the access rights of the built-in operating system. If the other party forcibly dismantles the machine and removes the disk for mounting and reading, it will easily lead to the leakage of important data and cause property losses to the manufacturer.

[0004] Therefore, there is an urgent need for a security management method for hidden areas that can reduce data risks and improve data security. Summary of the invention

[0005] Therefore, the technical problem to be solved by the present invention is to overcome the problem of low data security in related technologies.

[0006] In order to solve the above technical problems, the present invention provides a hidden area security management method, which is applied to a hidden area file system, comprising:

[0007] Receive a target operation request for a hidden area from a target user; the target user includes a security administrator or an ordinary user; the target operation request is at least one of a preset number of types of operation requests divided according to business scenarios; the preset number of types of operation requests include a first operation request, a second operation request, a third operation request and a fourth operation request; the first operation request represents a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request represents an ordinary user's request for a change operation on an attribute of a hidden area, the third operation request represents a security administrator's request for a configuration operation on permissions and passwords of all ordinary users, and the fourth operation request represents an ordinary user's request for a regular operation on a file in a hidden area;

[0008] Verify the authority, or authority and password, of the target user according to the preset security policy in the security layer; the preset security policy is the preset security policy corresponding to the hidden area; the preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer;

[0009] When the authority of the target user, or the authority and password are verified, the target operation request is executed.

[0010] In an optional implementation, when the target operation request is a first operation request, receiving a target operation request of a target user for a hidden area includes:

[0011] Receive a request from a security administrator to add a new operation to a hidden area or a request from a security administrator to delete an operation to a hidden area;

[0012] The new operation request includes: the name of the target disk partition and the target space capacity;

[0013] The deletion operation request includes: the name of the hidden area to be deleted;

[0014] After receiving a request from a security administrator for a new operation on a hidden area, the method further includes:

[0015] Determine whether the remaining space capacity of the target disk partition is greater than or equal to the target space capacity based on the name of the target disk partition in the new operation request. When the remaining space capacity of the target disk partition is greater than or equal to the target space capacity, divide the remaining space capacity of the target disk partition according to the target space capacity to obtain the target sector.

[0016] In an optional implementation, when the target operation request is a first operation request, verifying the authority of the target user, or the authority and password, according to a preset security policy in the security layer includes:

[0017] After obtaining the target sector, verifying the attribute configuration authority of the security administrator according to the preset security policy in the security layer;

[0018] Or, the attribute modification authority of the security administrator is verified according to a preset security policy in the security layer.

[0019] In an optional implementation manner, executing the target operation request when the authority, or the authority and password verification of the target user passes includes:

[0020] When the attribute configuration authority of the security administrator is verified to be passed, the target sector is initialized, and the security policy of the initialized target sector is configured according to the pre-acquired mandatory access control policy to obtain a newly added hidden area;

[0021] Or, when the attribute change permission check of the security administrator is passed, the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted to determine the first disk partition; the first disk partition is the disk partition obtained after the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted; the first attribute information in the attribute of the first disk partition is deleted, and the first disk partition is formatted; the first attribute information includes attribute information related to the hidden area.

[0022] In an optional implementation, when the target operation request is a second operation request, receiving the target operation request of the target user for the hidden area includes:

[0023] A request for modifying the properties of a hidden area from a common user is received; the request for modifying the properties of the hidden area includes the name of the hidden area to be modified, a modification command, and corresponding parameters to be modified.

[0024] In an optional implementation, when the target operation request is a third operation request, before receiving the target operation request of the target user for the hidden area, the method further includes:

[0025] Determine whether the target user is a security administrator; wherein, when the target user is a security administrator, receive a configuration operation request of the security administrator for permissions and passwords of all common users;

[0026] When the target user's authority, or the authority and password verification passes, executing the target operation request includes:

[0027] When the security administrator's authority verification is passed, the security administrator's configuration operation request for all common users' authority and passwords is executed.

[0028] In an optional implementation, when the target operation request is a fourth operation request, receiving the target operation request of the target user for the hidden area includes:

[0029] Receive regular operation requests from ordinary users for files in the hidden area;

[0030] When the target user's authority, or the authority and password verification passes, executing the target operation request includes:

[0031] When the authority and password of the ordinary user are verified, the ordinary user's regular operation request for the files in the hidden area is executed.

[0032] In a second aspect, the present invention provides a hidden area file system, comprising:

[0033] Initialization module, application interface module and execution module;

[0034] The initialization module is used to initialize the disk sectors;

[0035] The application interface module is used to receive a target operation request of a target user on a hidden area; the target user includes a security administrator or an ordinary user; the target operation request is at least one of a preset number of types of operation requests divided according to business scenarios; the preset number of types of operation requests include a first operation request, a second operation request, a third operation request and a fourth operation request; the first operation request represents a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request represents an ordinary user's request for a change operation on an attribute of a hidden area, the third operation request represents a security administrator's request for a configuration operation on permissions and passwords of all ordinary users, and the fourth operation request represents an ordinary user's request for a regular operation on a file in a hidden area;

[0036] The execution module is used to verify the authority, or the authority and password, of the target user according to the preset security policy in the security layer; the preset security policy is the preset security policy corresponding to the hidden area; the preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer; when the authority, or the authority and password of the target user are verified, the target operation request is executed.

[0037] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method for secure management of a hidden area of ​​the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0038] In a fourth aspect, the present invention provides a computer-readable storage medium, on which a single computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for secure management of a hidden area of ​​the first aspect or any corresponding embodiment thereof.

[0039] In a fifth aspect, the present invention provides a computer program product, including computer instructions, which are used to enable a computer to execute the method for secure management of a hidden area of ​​the first aspect or any corresponding embodiment thereof.

[0040] The technical solution provided by the present invention has the following technical effects: by distinguishing the permissions of security administrators and ordinary users, it is ensured that only authorized users can operate the hidden area, thereby enhancing the security of the system. The preset number of types of operation requests allows the system to perform more detailed access control on different types of operations, making the permission management more flexible and accurate. The permissions and passwords of the target users are verified by the preset security policy of the security layer to ensure that only legitimate users can perform operations, which improves the security and anti-attack capabilities of the system. The preset security policy of the security layer is obtained according to the mandatory access control policy mapping, which means that the system can enforce the security policy to prevent unauthorized access and data leakage. The security policy of the hidden area is compatible with and inherits the mandatory access control policy configuration by default, which makes the security management of the hidden area consistent with the security policy of the entire system, and is convenient for centralized management and maintenance. The security administrator can configure the permissions and passwords of all ordinary users, which provides flexibility in access control for ordinary users and can be adjusted according to business needs and security requirements. The regular operation requests (addition, deletion, modification, and query) of ordinary users to files in the hidden area are also controlled by the security management method to ensure that these operations are performed within the scope allowed by the security policy. By strictly controlling access to hidden areas, abuse and misoperation of system resources are reduced, thereby improving the stability and reliability of the system. The security management method for hidden areas provided by the technical solution of the present invention improves the security, flexibility and stability of the system through detailed authority control and implementation of mandatory access control strategies. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0042] Figure 1 is a schematic diagram of the framework of the hidden area file system according to an embodiment of the present invention;

[0043] Figure 2 is a flow chart of a method for managing a hidden area security according to an embodiment of the present invention;

[0044] Figure 3 It is a schematic diagram of the overall process of the security management method of the hidden area according to an embodiment of the present invention;

[0045] Figure 4 is a schematic diagram of the structure of a hidden area file system according to an embodiment of the present invention;

[0046] Figure 5It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0048] In the computer field, intellectual property protection and anti-tampering protection of commercial software are important measures for manufacturers to form a closed business loop while providing software services to users.

[0049] Large-scale project delivery is often delivered together with the software and the hardware platform on which it runs, forming a simple and easy-to-use chassis box with relatively closed operation entrances. This allows all user operations to be within a controllable range, forming a stable human-computer interaction function boundary. At the same time, only the debugging interface for developers is reserved for the system inside the device for maintenance and upgrade use.

[0050] In the delivered equipment, the system integrated in the chassis is generally provided with upgrade functions according to the service life provided. However, the protection of core data and applications is generally achieved by closing the access rights of the built-in operating system. If the other party forcibly dismantles the machine and removes the disk to read the data by mounting and reading, there is a chance that important business data will be leaked, and the data security is poor.

[0051] In the relevant technologies, there are generally the following ways to protect device data security and corresponding upgrade and maintenance methods:

[0052] (1) All are achieved through the multi-user permission control of the operating system.

[0053] This method is the most common, because the operating system itself has a user permission system. By presetting user permissions based on the operating needs of its own equipment and providing customers with specified ordinary user permissions at the time of delivery, the user's access scope and operating boundaries to the built-in operating system can be controlled.

[0054] Correspondingly, when upgrading and maintenance are required, another dedicated user account can be used to obtain higher permissions to modify core data.

[0055] The disadvantage of this approach is that it may lead to loss of account information and uncontrollable boundaries of human operations, especially changes in maintenance personnel and products, which will lead to increased user account management costs and risks, and cause data security risks from social engineering.

[0056] (2) This is achieved through user authority control of the operating system and secondary development of the operating system’s interactive interface.

[0057] This method is a supplement to the single user permission system method. What is also delivered to the user is a device equipped with a customized operating system. Not only is the user's access rights configured, but the operation UI is also customized and developed separately, which blocks the general operating system login and access interaction interface, allowing users to interact in a specific UI interface.

[0058] Similarly, a separate operation UI will be developed for maintenance personnel, and a separate interaction boundary will be provided for maintenance personnel, which will only be used for upgrades and maintenance.

[0059] This method is common in devices with strong business and functional orientation, such as firewalls and switches. Due to its professional industry usage scenarios and relatively fixed business operation boundaries, developers can sort out the operation logic and develop UI interfaces based on the operation scenarios that do not change much. However, the disadvantages are obvious, such as low versatility, high development costs, and short update cycles. It is only suitable for large-scale manufacturers in specific industries.

[0060] (3) It is implemented by combining user permission control with permission verification components.

[0061] This method adds a permission verification component to a single method of controlling user permissions to avoid the implementation risks of key links of permission control introduced by operators' social engineering.

[0062] A universal standard device is provided at the time of delivery, and a firmware device is provided as a token. Different tokens are used to activate the user's corresponding business function usage rights and upgrade the maintenance personnel's operation rights.

[0063] However, this method is essentially still a user permission system configuration method at the software level, and has no control over the specific operations of various personnel and the protection of sensitive data.

[0064] The above protection mechanisms and corresponding upgrade and maintenance methods are all at the software level. If the device is directly disassembled, the disk is removed and mounted on another host to read data, the device information will be leaked, tampered with, and malicious programs will be implanted. When the device is put back into use, there will be security risks.

[0065] To this end, manufacturers will design protection mechanisms that meet their own needs or the needs of specific users to achieve data security protection in multiple forms using hardware and software.

[0066] The technical solution of the present invention is to build a hard disk sector into the working machine under the framework of "device data security protection mechanism", format it into a customized file system, that is, a hidden area file system, so that it cannot be recognized by the ordinary file system, so that the hard disk cannot be loaded in the upper operating system, and the access and operation of the hidden area can only be realized through the basic library SDK of the application interface module provided by the kernel, so as to achieve the purpose of data hiding. At the same time, a "security layer" is encapsulated on the operation of this sector. The security layer obtains the security lock every time a process accesses the hidden area, and verifies the password to unlock it. After the verification is passed, the operation of the hidden area can be obtained. In this way, a storage unit that can only be accessed by a password and through a special API interface outside the ordinary file system and user authority system in the operating system is realized to protect confidential information. By protecting data in a combination of software and hardware, the acquisition of data when the device is disassembled can be effectively avoided, thereby effectively improving the security of data.

[0067] A method for managing a hidden area security provided by an embodiment of the present invention is applied to Figure 1 The hidden area file system shown is used as a basic system function for use by operating system users (security administrators and ordinary users).

[0068] like Figure 1 The framework of the hidden area file system shown includes: an initialization module (CQFFS-Init), an application interface module (CQFFS-API) and an execution module (ChangQing Fidden File System, CQFFS).

[0069] The initialization module is used to initialize the disk sectors. The initialization module exists in the system application layer. In the form of a system built-in tool set, it calls the system call of the execution module CQFFS to implement the initialization of ordinary disk sectors. For example, initialize the target sector.

[0070] The application interface module is used to receive a target operation request from a target user for a hidden area. The target user includes a security administrator or an ordinary user. The target operation request is at least one of a preset number of types of operation requests divided according to business scenarios. The preset number of types of operation requests include a first operation request, a second operation request, a third operation request, and a fourth operation request. The first operation request represents a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request represents an ordinary user's request for a change operation on the attributes of a hidden area, the third operation request represents a security administrator's request for a configuration operation of permissions and passwords for all ordinary users, and the fourth operation request represents an ordinary user's request for a general operation on files in the hidden area. The application interface module belongs to the system basic library and is an interface used by upper-level applications to operate the hidden area to perform business functions.

[0071] The execution module is used to verify the target user's authority, or authority and password according to the preset security policy in the security layer. The preset security policy is the preset security policy corresponding to the hidden area. The preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer. When the target user's authority and password are verified, the target operation request is executed. The execution module exists in the kernel module of the operating system and is the execution core of the entire hidden area file system. It is parallel to the ordinary file system and provides system calls for various operations on the corresponding drive letter of the hidden area.

[0072] The embodiments of the present invention provide a hidden area security management method, a hidden area file system, a device and a medium to solve the above problems.

[0073] According to an embodiment of the present invention, an embodiment of a method for secure management of a hidden area is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer device such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0074] Figure 2 It is a flowchart of a method for safely managing a hidden area according to an embodiment of the present invention.

[0075] like Figure 2 As shown, in an embodiment of the present invention, a hidden area security management method is provided, which is applied to a hidden area file system. The framework of the hidden area file system includes: an initialization module (CQFFS-Init), an application interface module (CQFFS-API) and an execution module (ChangQing Fidden File System, CQFFS). The hidden area security management method includes:

[0076] S101: receiving a target operation request of a target user on a hidden area.

[0077] In this embodiment, the target user includes a security administrator or a common user. The target operation request is at least one of a preset number of types of operation requests divided according to business scenarios.

[0078] As an example, operations on the hidden area can be divided into four types according to business scenarios, and the corresponding preset number of types of operation requests include a first operation request, a second operation request, a third operation request, and a fourth operation request. The first operation request represents a security administrator's request for a new operation on the hidden area or a security administrator's request for a deletion operation on the hidden area. The security administrator can format a disk sector as a hidden area or remove a hidden area. The second operation request represents an ordinary user's request for changing the attributes of the hidden area. Ordinary users can perform business operations on the CQFFS mount point as a unit. The third operation request represents the security administrator's request for configuring the permissions and passwords of all ordinary users. The security administrator implements user permission configuration and user password configuration operations. The fourth operation request represents an ordinary user's request for a regular operation on files in the hidden area. Ordinary users can perform regular operations on files in the hidden area (visible, read and write operations, etc.).

[0079] S102: Verify the authority, or authority and password, of the target user according to the preset security policy in the security layer, and execute the target operation request when the authority, or authority and password of the target user are verified.

[0080] In this embodiment, the preset security policy is the preset security policy corresponding to the hidden area. The preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer.

[0081] In this embodiment, when the target user's authority, or the authority and password verification fails, the current operation request is terminated and a prompt message is given, such as a prompt message indicating that the authority verification has not passed, or a prompt message indicating that the password verification has not passed. The preset security policy includes ordinary users, operation requests, ordinary users' authority, passwords, security administrators, operation requests, and security administrators' authority. The preset security policy can specifically be an access control list, which is usually a permission list containing multiple entries, each of which defines a subject (user or group) and corresponding permissions. For example, an entry can indicate that ordinary user A can modify the attributes of a hidden area, and the corresponding ordinary user A's permission verification for the operation request to change the attributes of the hidden area passes. In this embodiment, when permissions and passwords need to be verified, permissions and passwords are verified in sequence.

[0082] In this embodiment, the mandatory access control policy (CYSE security policy configuration file) is a control module built into the operating system and secondary developed for the native SELinux mandatory access control module of Linux. It is compatible with SELinux operations in terms of operation, and expands fields such as "complete set" in the attribute fields of the subject and object. In conjunction with the control command, the free switching of the Biba access control model and the BLP access control model can be realized. The preset security policy corresponding to the hidden area, or the hidden area access control policy file, is a file of a separate module, but in order to simplify user operations and improve the reusability of the module. The security attributes of the hidden area are directly compatible with the CYSE security policy. When creating a hidden area, the default access configuration is to set the mandatory access control policy to the preset security policy corresponding to the hidden area, inherit the mandatory access control policy, and convert it to the configuration of the hidden area to achieve the effect. Support security administrators to modify the attributes of the hidden area so that security control is concentrated in one account. The permissions of ordinary users to read, write, be visible or not, mount, and uninstall the hidden area are all changed by the security administrator. Compatibility is achieved in effect. After all, the actual execution is two modules, so there is a mapping process, that is, mapping the CYSE security policy to the hidden area's own permission control configuration. The preset security policy configuration file records which subject classes can perform which operations on which access object classes. Among them, the subject class (i.e., the executor) can add users and manage them uniformly. This is the "user GID". The "user GID" and the GID of the Linux user management module are two different files. The "user GID" can be understood as a group.

[0083] The technical solution of the present invention enhances the security of the system by distinguishing the permissions of security administrators and ordinary users, and classifying and processing different types of operation requests. The permissions and passwords of security administrators and ordinary users are verified. The password is verified when the security administrator account logs in or switches from an ordinary user to the security administrator account. The technical solution of the present invention mainly involves the verification of the security administrator's permissions when the target user is a security administrator, and the verification of the ordinary user's permissions and passwords when the target user is an ordinary user after receiving the target operation request of the hidden area from the target user, thereby improving the security of the system. The preset number of types of operation requests are divided according to the business scenario, allowing the system to perform more detailed access control on different types of operations, making the permission management more flexible and accurate. The execution module CQFFS verifies the user's permissions and passwords according to the preset security policy of the security layer, ensuring that the system can enforce the security policy and prevent unauthorized access and data leakage. The application interface module CQFFS-API provides an easy-to-use interface for the upper-level application, allowing developers to easily integrate the operation functions of the hidden area and improve development efficiency. The execution module CQFFS works in parallel with the normal file system as part of the operating system kernel, which allows the hidden area file system to be seamlessly integrated into the existing operating system without large-scale modifications to the existing system architecture. Permission and password verification will be performed before any operation is performed, which adds a layer of security to ensure that only legitimate users can perform operations. The technical aspects of the present invention allow the security policy of the hidden area to be compatible with the mandatory access control policy of the operating system, which is convenient for centralized management and maintenance.

[0084] The target operation request is the first operation request (a security administrator's request for adding a new operation to a hidden area or a security administrator's request for deleting an operation to a hidden area):

[0085] In an optional implementation, when the target operation request is a first operation request, receiving the target operation request of the target user for the hidden area in S101 specifically includes:

[0086] Receive a security administrator's request for adding a new operation to a hidden area or a security administrator's request for deleting an operation to a hidden area.

[0087] In this embodiment, the add operation request includes: the name of the target disk partition and the target space capacity, and also includes the name of the newly added hidden area. The delete operation request includes: the name of the hidden area to be deleted.

[0088] After receiving a new operation request for a hidden area from a security administrator, the hidden area security management method further includes:

[0089] Determine whether the remaining space capacity of the target disk partition is greater than or equal to the target space capacity based on the name of the target disk partition in the new operation request. When the remaining space capacity of the target disk partition is greater than or equal to the target space capacity, divide the remaining space capacity of the target disk partition according to the target space capacity to obtain the target sector.

[0090] When the target operation request is a first operation request, the step S102 of verifying the authority of the target user, or the authority and password, according to the preset security policy in the security layer specifically includes:

[0091] After obtaining the target sector, the attribute configuration permission of the security administrator is verified according to the preset security policy in the security layer. The attribute configuration permission of the security administrator corresponding to the new operation request is added.

[0092] Alternatively, the security administrator's property change permission is verified according to the preset security policy in the security layer. The delete operation request corresponds to the security administrator's property change permission.

[0093] When the target operation request is a first operation request, when the authority of the target user, or the authority and password are verified, executing the target operation request in S102 specifically includes:

[0094] When the attribute configuration authority check of the security administrator passes, the target sector is initialized, and the security policy of the initialized target sector is configured according to the pre-acquired mandatory access control policy to obtain a newly added hidden area.

[0095] Or when the attribute change permission check of the security administrator is passed, the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted to determine the first disk partition. The first disk partition is the disk partition obtained after the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted. The first attribute information in the attribute of the first disk partition is deleted, and the first disk partition is formatted. The first attribute information includes attribute information related to the hidden area.

[0096] For the addition and deletion of hidden areas, when you need to configure a common disk sector as a hidden area or change the original hidden area to a common sector, the upper-layer application software calls the CQFFS-API interface, or the user enters commands in the shell terminal to send configurations and parameters. The parameters included in the new operation request are:

[0097] The name of the target disk partition: the actual disk sector, such as / dev / sda1, etc. (only required when adding a new partition).

[0098] Target space capacity, partition space size, only needs to be entered when adding.

[0099] It may also include the name of the newly added hidden area: the name of the virtual disk used to mount the hidden area file system.

[0100] After the background preprocesses the command and identifies the new operation request and the deletion operation request of the hidden area, it first loads the hardware devices recognized by the current system and selects the storage devices from them. The hardware devices refer to the overall device list, including input and output devices, network devices, storage devices, computing devices, etc. Identifying the hardware devices is to find the storage device from a bunch of existing overall device lists and proceed to the next step of processing.

[0101] If a hidden area is added, the following steps are performed:

[0102] According to the name of the target disk partition in the new operation request, determine whether the remaining space capacity of the target disk partition is greater than or equal to the target space capacity, that is, it is necessary to first search whether the input disk letter (name of the target disk partition) has space available for allocation.

[0103] When the remaining space of the target disk partition is greater than or equal to the target space capacity, the remaining space of the target disk partition is divided according to the target space capacity to obtain the target sector. That is, if there is space, the fdisk tool can be used to divide the sector to obtain the target sector.

[0104] In this embodiment, the sectors are divided according to the current system default configuration or the parameters specified by the administrator user, and the parameters may include partition size, partition format, partition number, etc. In this embodiment, the specific method of dividing sectors can be implemented using conventional technology, which will not be repeated here.

[0105] After obtaining the target sector, check whether the target user (security administrator) has the authority to configure the properties of the hidden area. Specifically, the attribute configuration authority of the security administrator can be checked according to the preset security policy of the security layer, that is, query in the "user GID" to determine whether the security administrator has the authority to configure the properties of the hidden area.

[0106] When the attribute configuration permission check of the security administrator passes, the target sector is initialized, and the security policy of the initialized target sector is configured according to the mandatory access control policy obtained in advance to obtain a newly added hidden area. Specifically, the target sector can be initialized according to the format of the hidden area file system. However, the newly initialized hidden area needs to be configured with who can access the partition and who cannot access it, that is, the security policy of the newly added hidden area needs to be configured. In the present invention, the security policy of the hidden area is compatible with and inherits the CYSE security policy configuration by default. Therefore, the default CYSE security policy configuration file can be obtained in advance. Then after initialization, the permission configuration in the CYSE security policy configuration file is converted into the security attribute parameters of the newly added hidden area, thereby realizing the configuration of the security policy corresponding to the newly added hidden area.

[0107] Initialize the target sector according to the format of the hidden area file system, which may include specifying the appropriate file system type. For example, format the newly created target sector (such as / dev / sda4) as the ext4 file system: sudomkfs.ext4 / dev / sda4. Common other file system formatting commands include formatting as xfs, btrfs, vfat, etc. After formatting, the newly added hidden area can be mounted to the system directory for access. First create a mount point, and then use the mount command to mount the newly added hidden area.

[0108] If the hidden area is converted to a normal sector, the following steps are performed:

[0109] After receiving the security administrator's request to delete the hidden area, the security administrator's attribute change permission is verified according to the preset security policy of the security layer, and the "user GID verification" permission link is directly entered. It is determined whether the user's group has the permission to change the attributes of the hidden area. If they do not match, it means that the permission is insufficient and the verification fails. If they match, it means that the modification can be made and the verification passes.

[0110] When the attribute change permission verification of the security administrator passes, the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted to determine the first disk partition. The first disk partition is the disk partition obtained after the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted. Delete the first attribute information in the attributes of the first disk partition, and format the first disk partition. The first attribute information includes attribute information related to the hidden area. When the verification passes, an attempt will be made to demount. If no other process is occupied, the demounting can be successful. After demounting, the first disk partition is obtained, and the attribute field of the hidden area of ​​the first disk partition is removed. And the first disk partition is formatted according to the ordinary disk partition. At this time, the formatted first disk partition is an ordinary disk sector that can be directly mounted.

[0111] In a disk partition, the attribute fields indicating that the partition is a hidden area are as follows:

[0112] For Windows systems: In the GUID partition table, there is a special area (8 bytes, i.e. 64 bits) used to indicate partition attributes. The following are some attribute fields related to hidden partitions: 0x0000000000000001 (0 bits): Indicates that the partition is a required partition and the user is not allowed to change the data (it will be marked as an OEM partition under Windows). 0x8000000000000000 (63 bits): When the hard disk is mounted to another computer, no drive letter is assigned by default. 0x4000000000000000 (62 bits): Indicates that the partition cannot be detected. 0x2000000000000000 (61 bits): Indicates that the partition is a shadow copy of another partition. 0x100000000000000 (60 bits): Set the read-only attribute for the partition.

[0113] For Linux systems: In Linux, the hidden attribute of a disk partition can be achieved by modifying the file attributes, such as using the chattr command to add the +i attribute to a file or directory to make it an immutable file, thereby achieving the hidden effect. In addition, the universal unique identifier in the Linux system is an attribute of the disk partition, which is crucial when managing a server with hundreds of drives, but the universal unique identifier itself does not directly indicate whether the partition is hidden.

[0114] The above attribute fields and methods can be used to identify and manage hidden areas to ensure the security and privacy of partitions.

[0115] The target operation request is the second operation request (a request by a common user to change the properties of a hidden area):

[0116] In an optional implementation, when the target operation request is a second operation request, receiving the target operation request of the target user for the hidden area in S101 specifically includes:

[0117] Receive a request from an ordinary user to change the properties of a hidden area. The change request includes the name of the hidden area to be changed, the change command, and the corresponding parameters to be changed. The change command is a hidden area operation subcommand. For example, you can use the mount command to mount the hidden area to a specified mount point sudo mount / dev / vdb1 / mnt / partition1, and you can use the mount command to unmount the mounted hidden area sudo umount / mnt / partition1.

[0118] When there is a need to change the attributes of the hidden area (such as mounting, unmounting, changing the mount point, etc.), first send parameters through the application interface module CQFFS-API or shell command. The parameters are as follows:

[0119] The name of the hidden area to be changed, the change command and the corresponding parameters to be changed.

[0120] In this embodiment, when the target operation request is a second operation request, S102 verifies the authority, or the authority and password of the target user according to the preset security policy in the security layer, and executes the target operation request when the authority, or the authority and password of the target user pass the verification, specifically including:

[0121] At this time, the preset security policy is obtained in advance, and the "user GID" is verified to determine whether the ordinary user has the right to change the attributes of the hidden area. After the judgment is passed, if the password is configured, it is necessary to enter the user password and perform identity authentication. After the identity authentication is passed, the operation request to change the attributes of the hidden area is executed. Since the change of the hidden area attributes requires the corresponding module of the kernel to process, the processing module needs to be temporarily loaded and the module is released after the modification is completed. That is to say, when the target operation request is the second operation request, the authority and password of the target user (ordinary user) are verified according to the preset security policy in the security layer, and when the authority and password of the target user (ordinary user) are verified, the target operation request is executed.

[0122] The target operation request is the third operation request (the security administrator's configuration operation request for the permissions and passwords of all ordinary users):

[0123] In an optional implementation, when the target operation request is a third operation request, before receiving the target operation request of the target user for the hidden area, the security management method of the hidden area further includes:

[0124] Determine whether the target user is a security administrator. If the target user is a security administrator, receive a configuration operation request from the security administrator for permissions and passwords of all common users.

[0125] Receiving a target operation request of a target user on a hidden area in S101 specifically includes:

[0126] Receive configuration operation requests from security administrators for permissions and passwords of all common users.

[0127] S102 verifies the authority, or authority and password, of the target user according to the preset security policy in the security layer, and executes the target operation request when the authority, or authority and password of the target user passes the verification, specifically including:

[0128] Verify the security administrator's permissions according to the preset security policies in the security layer.

[0129] When the security administrator's authority verification is passed, the security administrator's configuration operation request for all common users' authority and passwords is executed.

[0130] In the operating system, the security administrator is originally the management user of the security access module of the mandatory access control module. It is a built-in security administrator account of the system. The configuration of security permissions and passwords in the hidden area are all assigned to this user.

[0131] First, confirm whether the target user who sends the third operation request is a security administrator. If the target user is a security administrator, load the current security policy module and allow the configuration of adding, deleting, modifying, and updating passwords of users who access the hidden area. This part saves the password verification of the security administrator because the user itself borrows the system's built-in security administrator account, and the verification has been done when the user switches to this account.

[0132] The target operation request is the fourth operation request (a regular operation request of an ordinary user to a file in a hidden area):

[0133] In an optional implementation, when the target operation request is the fourth operation request, receiving the target operation request of the target user for the hidden area in S101 specifically includes:

[0134] Receive regular operation requests from ordinary users for files in the hidden area.

[0135] S102 verifies the authority, or authority and password, of the target user according to the preset security policy in the security layer, and executes the target operation request when the authority, or authority and password of the target user passes the verification, specifically including:

[0136] The authority and password of the common user are verified according to the preset security policy in the security layer. When the authority and password of the common user are verified, the common user's regular operation request for the file in the hidden area is executed.

[0137] In this embodiment, whether a common user can see a hidden area, and whether they have read, write, and execute permissions, is determined according to the preset security policy in the security layer. When a user accesses a hidden area, first the user GID needs to be verified, and secondly, if an access password is configured, the access password needs to be entered the first time or after the password-free time configured by the security policy, so that the operation can be carried out like a normal file directory.

[0138] In the present invention, when the upper-level application calls the interface in the basic library or the tool set provided by the system to operate, the interface and the tool set only pre-process the data to be processed, and then must pass the security layer to review the authority, and then send it to the kernel for execution. Among them, the security administrator does not operate the business, and does not need a password subsequently, while ordinary users can only perform business operations, and when calling, if the password is enabled, it is necessary to enter the password for verification. The technical solution of the present invention uses a customized file system with hidden sector formatting, adopts an operating interface independent of the ordinary file system, and adds a mechanism for security layer review authority, which has one more specific storage option than the ordinary file system and user authority mechanism. It can effectively prevent network attacks on user systems, effectively prevent internal privilege escalation, and effectively prevent data security attacks on key information in the system through the file system.

[0139] The overall flow diagram of the safety management method for hidden areas of the present invention is as follows: Figure 3 shown.

[0140] It should be noted that the contents not described in detail in the specification of the present invention belong to the common knowledge of those skilled in the art.

[0141] In this embodiment, a hidden area file system is also provided. A single system is used to implement the above-mentioned embodiment and optional implementation methods. The descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0142] Figure 4 It is a schematic diagram of the structure of the hidden area file system according to an embodiment of the present invention.

[0143] The present invention provides a hidden area file system, such as Figure 4 As shown, the hidden area file system includes:

[0144] An initialization module 11 , an application interface module 12 and an execution module 13 .

[0145] The initialization module 11 is used to initialize the disk sectors.

[0146] The application interface module 12 is used to receive a target operation request from a target user for a hidden area. The target user includes a security administrator or an ordinary user. The target operation request is at least one of a preset number of types of operation requests divided according to business scenarios. The preset number of types of operation requests include a first operation request, a second operation request, a third operation request, and a fourth operation request. The first operation request represents a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request represents an ordinary user's request for a change operation on the attributes of a hidden area, the third operation request represents a security administrator's request for a configuration operation on permissions and passwords for all ordinary users, and the fourth operation request represents an ordinary user's request for a regular operation on files in a hidden area.

[0147] The execution module 13 is used to verify the authority, or the authority and password of the target user according to the preset security policy in the security layer. When the authority, or the authority and password of the target user are verified, the target operation request is executed. The preset security policy is the preset security policy corresponding to the hidden area. The preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer.

[0148] In the present invention, each module is divided into a security function class and a storage function class according to the function type.

[0150] The security function class runs through disk initialization, system calls, upper-layer interfaces, and the access control mechanism for the hidden area. Its effect is achieved through the concept of security layer and hidden area user password.

[0151] Every time a business operation is performed on the hidden area, the user's permissions or permissions and passwords need to be verified through the security layer. The "Security Administrator" user controls the operation permissions and operation passwords assigned to ordinary users in the hidden area. Even if ordinary users use the interface of the basic library, they need to verify the password of the process running user in the security layer when the process loads the module before they can be released. In the initialization phase, it is necessary to initialize the attribute configuration of the corresponding mount point of the hidden area file system in the security layer. When in use, the security layer operation, user permission verification, encryption and other instructions are issued through the basic library, and are specifically executed in the execution module. The access control of the hidden area is not independent, but is included in another mandatory access control module built into the system that uniformly manages the operating permissions of the operating system. This makes the security management of the hidden area not conflict with the mandatory access control of the entire operating system, and is also easy to centrally manage. The storage function class also exists in the three modules, which meets most of the usage functions of the ordinary operating system for the file system, making it convenient for upper-level applications or secondary developers to get started quickly.

[0152] In an optional implementation, when the target operation request is the first operation request, the application interface module 12 is specifically configured to receive a security administrator's request for adding a new operation to a hidden area or a security administrator's request for deleting an operation to a hidden area.

[0153] The new operation request includes: the name of the target disk partition and the target space capacity.

[0154] The deletion operation request includes: the name of the hidden area to be deleted.

[0155] After receiving the security administrator's request for a new operation on the hidden area, the application interface module 12 or the initialization module 11 can be used to determine whether the remaining space capacity of the target disk partition is greater than or equal to the target space capacity based on the name of the target disk partition in the new operation request. When the remaining space capacity of the target disk partition is greater than or equal to the target space capacity, the remaining space capacity of the target disk partition is divided according to the target space capacity to obtain the target sector.

[0156] In an optional embodiment, when the target operation request is a first operation request, the execution module 13 is specifically used to verify the attribute configuration authority of the security administrator according to the preset security policy in the security layer after obtaining the target sector, or to verify the attribute modification authority of the security administrator according to the preset security policy in the security layer.

[0157] In an optional implementation, the execution module 13 is further configured to initialize the target sector when the attribute configuration authority check of the security administrator is passed, configure the security policy of the initialized target sector according to the pre-acquired mandatory access control policy, and obtain a newly added hidden area.

[0158] Or, when the attribute change permission of the security administrator is verified, the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted to determine the first disk partition. The first disk partition is the disk partition obtained after the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted. The first attribute information in the attribute of the first disk partition is deleted, and the first disk partition is formatted. The first attribute information includes attribute information related to the hidden area.

[0159] In an optional implementation, when the target operation request is a second operation request, the application interface module 12 or the initialization module 11 can be used to receive an ordinary user's request to change the attributes of the hidden area. The change operation request includes the name of the hidden area to be changed, the change command and the corresponding parameters to be changed.

[0160] In an optional implementation, when the target operation request is the third operation request, before receiving the target operation request of the target user for the hidden area, the execution module 13 is further used to determine whether the target user is a security administrator. Wherein, when the target user is a security administrator, the configuration operation request of the security administrator for the authority and password of all ordinary users is received. When the authority check of the security administrator is passed, the configuration operation request of the security administrator for the authority and password of all ordinary users is executed.

[0161] In an optional implementation, when the target operation request is the fourth operation request, the application interface module 12 or the initialization module 11 can be used to receive a common user's regular operation request for files in the hidden area. The execution module is further used to execute the common user's regular operation request for files in the hidden area when the authority and password of the common user are verified.

[0162] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0163] The hidden area file system in this embodiment is presented in the form of functional units, where the units refer to ASIC (Application Specific Integrated Circuit) circuits, processors and memories that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0164] The embodiment of the present invention also provides a computer device having the above Figure 4 The hidden area file system shown.

[0165] See also Figure 5 , Figure 5 Schematic diagram of the hardware structure of the computer device according to the embodiment of the present invention. Figure 5 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In an optional embodiment, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor device). Figure 5 A processor 10 is taken as an example.

[0166] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0167] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0168] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating device, an application required for at least one function. The data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage devices. In an optional embodiment, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0169] The memory 20 may include a volatile memory, such as a random access memory. The memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive. The memory 20 may also include a combination of the above-mentioned types of memory.

[0170] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0171] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc. Further, the storage medium can also include a combination of the above-mentioned types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0172] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0173] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A hidden area security management method, applied to a hidden area file system, characterized in that: include: Receiving a target operation request from a target user on the hidden area; The target users include security administrators or common users; The target operation request is at least one of a preset number of types of operation requests divided according to business scenarios; The preset number of types of operation requests include a first operation request, a second operation request, a third operation request and a fourth operation request; the first operation request indicates a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request indicates a common user's request for a change operation on a property of a hidden area, the third operation request indicates a security administrator's request for a configuration operation on permissions and passwords of all common users, and the fourth operation request indicates a common user's request for a regular operation on a file in a hidden area; Verify the target user's authority, or authority and password, according to the preset security policy in the security layer; The preset security policy is the preset security policy corresponding to the hidden area; The preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer; When the authority of the target user, or the authority and password are verified, the target operation request is executed.

2. The method according to claim 1, characterized in that When the target operation request is a first operation request, receiving the target operation request of the target user for the hidden area includes: Receive a request from a security administrator to add a new operation to a hidden area or a request from a security administrator to delete an operation to a hidden area; The new operation request includes: the name of the target disk partition and the target space capacity; The deletion operation request includes: the name of the hidden area to be deleted; After receiving a request from a security administrator for a new operation on a hidden area, the method further includes: Determine whether the remaining space capacity of the target disk partition is greater than or equal to the target space capacity based on the name of the target disk partition in the new operation request. When the remaining space capacity of the target disk partition is greater than or equal to the target space capacity, divide the remaining space capacity of the target disk partition according to the target space capacity to obtain the target sector.

3. The method according to claim 2, characterized in that When the target operation request is a first operation request, verifying the authority of the target user, or the authority and password, according to a preset security policy in the security layer includes: After obtaining the target sector, verifying the attribute configuration authority of the security administrator according to the preset security policy in the security layer; Or, the attribute modification authority of the security administrator is verified according to a preset security policy in the security layer.

4. The method according to claim 3, characterized in that When the authority, or the authority and password of the target user are verified, executing the target operation request includes: When the attribute configuration authority of the security administrator is verified to be passed, the target sector is initialized, and the security policy of the initialized target sector is configured according to the pre-acquired mandatory access control policy to obtain a newly added hidden area; Or, when the attribute change permission check of the security administrator is passed, the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted to determine the first disk partition; the first disk partition is the disk partition obtained after the hidden area corresponding to the name of the hidden area to be deleted in the deletion operation request is demounted; the first attribute information in the attribute of the first disk partition is deleted, and the first disk partition is formatted; the first attribute information includes attribute information related to the hidden area.

5. The method according to claim 1, characterized in that When the target operation request is a second operation request, receiving the target operation request of the target user for the hidden area includes: A request for modifying the properties of a hidden area from a common user is received; the request for modifying the properties of the hidden area includes the name of the hidden area to be modified, a modification command, and corresponding parameters to be modified.

6. The method according to claim 1, characterized in that When the target operation request is a third operation request, before receiving the target operation request of the target user for the hidden area, the method further includes: Determine whether the target user is a security administrator; wherein, when the target user is a security administrator, receive a configuration operation request of the security administrator for permissions and passwords of all common users; When the target user's authority, or the authority and password verification passes, executing the target operation request includes: When the security administrator's authority verification is passed, the security administrator's configuration operation request for all common users' authority and passwords is executed.

7. The method according to claim 1, characterized in that When the target operation request is a fourth operation request, receiving the target operation request of the target user for the hidden area includes: Receive regular operation requests from ordinary users for files in the hidden area; When the target user's authority, or the authority and password verification passes, executing the target operation request includes: When the authority and password of the ordinary user are verified, the ordinary user's regular operation request for the files in the hidden area is executed.

8. A hidden area file system, characterized in that: include: Initialization module, application interface module and execution module; The initialization module is used to initialize the disk sectors; The application interface module is used to receive a target operation request of a target user on a hidden area; the target user includes a security administrator or a common user; the target operation request is at least one of a preset number of types of operation requests divided according to business scenarios; The preset number of types of operation requests include a first operation request, a second operation request, a third operation request and a fourth operation request; the first operation request indicates a security administrator's request for a new operation on a hidden area or a security administrator's request for a deletion operation on a hidden area, the second operation request indicates a common user's request for a change operation on a property of a hidden area, the third operation request indicates a security administrator's request for a configuration operation on permissions and passwords of all common users, and the fourth operation request indicates a common user's request for a regular operation on a file in a hidden area; The execution module is used to verify the authority, or the authority and password of the target user according to the preset security policy in the security layer; The preset security policy is the preset security policy corresponding to the hidden area; The preset security policy in the security layer is obtained by mapping according to the mandatory access control policy of the security layer; when the authority of the target user, or the authority and password are verified, the target operation request is executed.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the hidden area security management method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the hidden area security management method according to any one of claims 1 to 7.

Images