Approval methods and approval systems

By generating a unique encryption key in the security domain and using the system's central module for file transfer, the security issues in the approval process from the security domain to the personal domain are resolved, enabling secure transmission and decryption control of encrypted files and improving data security.

CN117220901BActive Publication Date: 2026-11-17XIAMEN WANGSU CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310891472.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-07-19
Publication Date
2026-11-17
Estimated Expiration
2043-07-19

AI Technical Summary

Technical Problem

In existing technologies, the approval process for documents moving from a security domain to a personal domain has insufficient security and is prone to vulnerabilities, leading to the risk of sensitive data leakage.

Method used

By generating a unique encryption key in the secure domain upload module to encrypt the target file, and then interacting with the personal domain through the system center module, direct interaction between the secure domain and the personal domain is avoided, ensuring that the encrypted file is only decrypted in the system center module and preventing the decryption key from being leaked.

Benefits of technology

It improves the security of files from the security domain to the personal domain, prevents unauthorized users from accessing file content, and enhances data security and the reliability of the approval process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117220901B_ABST
    Figure CN117220901B_ABST
Patent Text Reader

Abstract

This application relates to the field of security technology and discloses an approval method and system. The method includes: obtaining user information of a security domain user through a security domain upload module; generating a unique encryption key based on the user information; encrypting a target file in the security domain using the unique encryption key; generating an approval request carrying the user information of the security domain user and the encrypted target file; and sending the request to a system center module. Upon approval of the approval request, the system center module then sends the encrypted target file to a personal domain download module. The system center module is located on a server outside the first user terminal. This method at least improves the security of sending files from a security domain to a personal domain.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of security technology, and in particular to an approval method and approval system. Background Technology

[0002] A personal domain represents the permissions and control scope possessed by an end user. A security domain is typically set by the administrator according to security policies and procedures to ensure that users can only access terminal resources within their authorized scope. Personal and security domains influence the security domain of a terminal. Files in a personal domain can often be transferred to the security domain, provided certain security policies are met, improving user efficiency. Conversely, users should also be able to read, write, and edit secure files in the security domain; however, to prevent the leakage of sensitive data in the security domain, the transfer of files from the security domain to the personal domain is usually prohibited.

[0003] However, users do have a need to download files from the secure domain in certain scenarios. To address this, current solutions include: adding file access policies to the file distribution channels; however, this often requires many additional policies and is prone to issues such as users forging files to bypass security mechanisms. Based on the former approach, a further approval mechanism has been proposed: when a file in the secure domain needs to be distributed to a personal domain, the distributor must obtain approval from the administrator. Only after approval is granted is access to the secure domain permitted, and the approved file distributed to the personal domain.

[0004] However, the above methods often fail to adequately consider the security of the approval process, which in turn makes the approval process a loophole, introduces some unstable factors, and poses security risks. Summary of the Invention

[0005] This application provides an approval method and system, which at least helps to improve the security of sending files from a security domain to a personal domain.

[0006] According to some embodiments of this application, one aspect of this application provides an approval method applied to a first user terminal. The first user terminal includes a secure domain upload module and a personal domain download module. The secure domain upload module is located in the secure domain of the first user terminal, and the personal domain download module is located in the personal domain of the first user terminal. The method includes: obtaining user information of a user in the secure domain through the secure domain upload module; generating a unique encryption key based on the user information of the user in the secure domain; encrypting a target file in the secure domain based on the unique encryption key; generating an approval request carrying the user information of the user in the secure domain and the encrypted target file and sending it to a system center module; and having the system center module send the encrypted target file to the personal domain download module after the approval request is approved. The system center module is located on a server outside the first user terminal.

[0007] According to some embodiments of this application, another aspect of this application provides an approval method applied to a system center module located on a server. The method includes: receiving an approval request sent by a security domain upload module, the approval request carrying user information of a security domain user and an encrypted target file encrypted with a unique encryption key generated from the user information of the security domain user; forwarding the approval request to an approval domain module, so that the approval domain module can return an approval result based on the approval request; if the approval result is approved, generating an approval identifier for the encrypted target file and issuing the approval identifier to a personal domain download module, so that after the personal domain download module sends a download request carrying the approval identifier, the encrypted target file can be returned to the personal domain download module.

[0008] According to some embodiments of this application, another aspect of this application provides an approval method applied to an approval domain module located in a second user terminal. The method includes: receiving an approval request sent by a system center module, the approval request carrying user information of a security domain user and an encrypted target file encrypted with a unique encryption key generated from the user information of the security domain user; approving the approval request based on the user information of the security domain user and the encrypted target file; and sending the approval result to the system center module.

[0009] According to some embodiments of this application, another aspect of this application provides an approval system, including: a security domain upload module, a system center module, an approval domain module, and a personal domain download module. The security domain module is located in the security domain of a first user terminal, the system center module is located on a server, the approval domain module is located in a second user terminal, and the personal domain download module is located in the personal domain of the first user terminal. The first user terminal is used to implement the approval method described above for the security domain module based on the security domain upload module and the personal domain download module; the system center module is used to implement the approval method described above for the system center module; the approval domain module is used to implement the approval method described above for the approval domain module; and the personal domain download module is used to implement the approval method described above for the personal domain download module.

[0010] According to some embodiments of this application, another aspect of this application provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the approval method as described in any of the above embodiments.

[0011] According to some embodiments of this application, another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the approval method as described in any of the above embodiments.

[0012] The technical solution provided in this application has at least the following advantages:

[0013] During the process of sending the target file from the security domain to the personal domain, the interaction between the security domain and the personal domain is realized through a system center module located outside the first user terminal where the security domain upload module is located. This eliminates direct interaction between the security domain and the personal domain, which helps ensure the security of data in the security domain. Simultaneously, the target file is encrypted with a unique encryption key generated based on the user information in the security domain before it travels from the security domain to the system center module, and then flows to the personal domain through the system center module. Furthermore, the security domain upload module and the system center module do not directly exchange encryption and decryption keys, and the system center module does not send the user information from the security domain along with the encrypted target file to the personal domain download module. Therefore, the decryption key will not be leaked, further ensuring security. If the personal domain download module cannot obtain information consistent with the user information in the security domain, it will be unable to generate the correct decryption key, resulting in decryption failure. This prevents the file from being leaked to unauthorized users, further enhancing security. Attached Figure Description

[0014] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0015] Figure 1 This is a flowchart of an approval method provided in one embodiment of this application;

[0016] Figure 2 This is another flowchart of the approval method provided in one embodiment of this application;

[0017] Figure 3 This is another flowchart of the approval method provided in one embodiment of this application;

[0018] Figure 4 This is another flowchart of the approval method provided in one embodiment of this application;

[0019] Figure 5 This is an interactive flowchart of an approval method provided in an embodiment of this application;

[0020] Figure 6 This is a schematic diagram of the structure of an approval system provided in one embodiment of this application;

[0021] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been presented in the various embodiments of this application to enable readers to better understand this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments.

[0023] The division of the following embodiments is for ease of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0024] This application provides an approval method applied to a first user terminal. The first user terminal includes a security domain upload module and a personal domain download module. The security domain upload module is located in the security domain of the first user terminal, and the personal domain download module is located in the personal domain of the first user terminal. The first user terminal is a terminal of an ordinary user, specifically an electronic device such as a computer, PC, or server.

[0025] It should be noted that the secure domain upload module can be understood as a logical module within the first user terminal. In practical applications, it can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Being located within a secure domain means that its related functions are provided based on the secure domain; for example, its internally deployed algorithms run within the secure domain.

[0026] It should also be noted that the personal domain download module can be understood as a logical module within the first user terminal. In practical applications, it can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Being located in the personal domain means that its related functions are provided based on the personal domain; for example, its internally deployed algorithms run within the personal domain.

[0027] In some embodiments, such as Figure 1 As shown, the approval method applied to the first user terminal includes the following steps:

[0028] Step 101: Obtain user information of security domain users through the security domain upload module.

[0029] In this embodiment, the security domain user is the user currently accessing the security domain. The user information of the security domain user is information used to uniquely identify the security domain user, which may be the account used by the user to access the security domain (such as username and password), the security domain user's mobile phone number, etc.

[0030] Step 102: Generate a unique encryption key based on the user information of the security domain user through the security domain upload module.

[0031] In this embodiment, the unique encryption key is a key that corresponds one-to-one with the user information of the user in the security domain.

[0032] It should be noted that this embodiment does not limit the method of generating the unique encryption key. It can be any mapping that can realize a one-to-one correspondence between the user information of the security domain user and the key corresponding to the user information of the security domain user.

[0033] In some embodiments, the user information of the security domain user can be processed by calling a digest algorithm, and the result can be used as a unique encryption key.

[0034] In some embodiments, the system may also report the user information of the security domain user to the system center module, so that the system center module can generate a globally unique string based on the user information of the security domain user and return it as a unique encryption key, etc.

[0035] Of course, the above is only an example of how to generate a unique encryption key. Other methods can be used in other embodiments, which will not be elaborated here.

[0036] Step 103: The target file in the security domain is encrypted using the unique encryption key via the security domain upload module.

[0037] This embodiment does not limit the encryption; it can be any key-based encryption method, such as the Data Encryption Standard (DES) encryption algorithm, the Advanced Encryption Standard (AES) algorithm, etc.

[0038] Step 104: Generate an approval request carrying the user information of the security domain user and the encrypted target file through the security domain upload module and send it to the system center module. After the system center module approves the request, it will send the encrypted target file to the personal domain download module. The system center module is located on a server outside the first user terminal.

[0039] This embodiment does not limit the request type or format of the approval request, and it can be any request that indicates the request for approval and carries user information of the user in the security domain and an encrypted target file, such as an HTTP request.

[0040] It is important to emphasize that the system's central module is located on a server outside the first user terminal, the secure domain upload module is located in the secure domain of the first user terminal, and the personal domain download module is located in the personal domain of the first user terminal. In other words, the encrypted target file is first sent from the secure domain of the first user terminal to the server, and then downloaded from the server to the personal domain of the first user terminal. Instead of establishing a connection between the secure domain and the personal domain within the same first user terminal, the target file is sent from the secure domain to the personal domain through a server outside the first user terminal. This avoids security issues caused by direct communication between the personal domain and the secure domain within the terminal, such as preventing attacks due to leaked access to the secure domain.

[0041] In some embodiments, the approval request also carries at least one of the following information: the time when the security domain user initiated the approval, and the reason why the security domain user initiated the approval.

[0042] Both the timing of the approval process and the reason for initiating the approval can help obtain more information about the approval of sending target files from outside the security domain to the personal domain. This allows for a more comprehensive consideration and more accurate approval decisions, improving the accuracy of the approval process, further enhancing the security of the approval process, and ensuring the security of data within the security domain.

[0043] Understandably, even if the outward transmission of a file has been approved, as long as the file is sent directly from the security domain to the personal domain, it actually creates a direct connection between the personal domain and the security domain. This provides the personal domain with a direct path to access the security domain, and this path becomes a vulnerability in the security domain that can be exploited by unauthorized personnel. For example, unauthorized personnel can use relevant technical means to use this path to directly access the security domain from the personal domain and tamper with the data in the security domain, thus posing a security risk to the data in the security domain.

[0044] The approval method provided in the above embodiments does not involve direct interaction between the security domain and the personal domain during the process of sending the target file from the security domain to the personal domain. Instead, the interaction occurs through the system central module, which helps ensure the security of the security domain. Furthermore, the target file is encrypted using an encryption key generated based on the user information of the security domain, and then travels from the security domain to the system central module and finally to the personal domain. The security domain upload module and the system central module do not directly exchange encryption keys; instead, they exchange the user information of the security domain user used to generate the encryption key. Also, the system central module sends the encrypted target file to the personal domain, excluding the user information from the security domain. Therefore, the personal domain download module cannot directly obtain the decryption key. If the personal domain download module cannot obtain user information consistent with the user information from the security domain—that is, if the user information obtained during decryption differs from the user information used during encryption—it will result in a mismatch between the encryption and decryption keys, making decryption impossible. This prevents the file from being leaked to unauthorized users and improves the security of the approval process.

[0045] In some embodiments, such as Figure 2 As shown, the approval method applied to the personal domain download module includes the following steps:

[0046] Step 105: Receive the approval identifier issued by the system center module through the personal domain download module.

[0047] In this embodiment, different encrypted target files have different approval identifiers, that is, the approval identifier can uniquely identify the encrypted target file.

[0048] Step 106: Generate a download request carrying an approval identifier through the personal domain download module and send the download request to the system center module, so that the system center module can return the encrypted target file according to the download request.

[0049] This embodiment does not limit the format or type of the download request; it can be any request that can request download content and carries an approval identifier, such as an HTTP request.

[0050] Step 107: Obtain user information of personal domain users through the personal domain download module.

[0051] In this embodiment, the personal domain user is the user currently accessing the personal domain. The user information of the personal domain user is information used to uniquely identify the personal domain user, which may be the account (such as username and password) used by the user to access the personal domain, the mobile phone number of the security domain user, etc.

[0052] Step 108: Generate a unique decryption key based on the user information of the personal domain through the personal domain download module.

[0053] In this embodiment, the unique decryption key is a key that corresponds one-to-one with the user information of the personal domain user.

[0054] It should be noted that this embodiment does not limit the method of generating the unique decryption key. It can be any mapping that can realize a one-to-one correspondence between the user information of a personal domain user and the user information of the personal domain user.

[0055] In some embodiments, a digest algorithm can be invoked to process the user information of a personal domain user, and the result can be used as a unique encryption key.

[0056] In some embodiments, the system may also report the user information of the personal domain user to the system center module, so that the system center module can generate a globally unique string based on the user information of the personal domain user and return it as a unique decryption key, etc.

[0057] Of course, the above is only an example of how to generate a unique decryption key. Other methods can be used in other embodiments, which will not be elaborated here.

[0058] It should be noted that, when both the unique encryption key and the unique decryption key are obtained by calling a digest algorithm without interacting with other modules, the methods for generating the unique encryption key based on the user information of the personal domain user and the unique decryption key based on the user information of the security domain user should be the same, and the encryption of the target file should use a symmetric encryption algorithm; otherwise, the encrypted target file will not be able to be decrypted.

[0059] Step 109: Decrypt the encrypted target file using the unique decryption key via the personal domain download module.

[0060] In some embodiments, after decrypting the encrypted target file according to the unique decryption key, the approval method applied to the personal domain download module further includes the following steps: before presenting the target file to the user, adding a blind watermark to the target file according to the file association information, the file association information including at least one of the following: user information of the personal domain user, download time, and approval identifier.

[0061] Understandably, user information and approval identifiers of personal domain users can directly indicate the user source of a file, and download time combined with download records can also determine the user source. Therefore, after generating a blind watermark based on file association information such as user information, download time, and approval identifiers of personal domain users, once a target file is leaked, the source of the leak can be determined based on the content of the blind watermark, allowing for targeted protection and further improving the security of the approval process.

[0062] In some embodiments, the personal domain download module is also deployed with a filter driver and / or a hook mechanism, which can protect the personal domain download module from process debugging, memory dumping, packet capture, and hooking.

[0063] In other words, the approval method applied to the personal domain download module also includes the following steps: invoking the filter driver and / or hook mechanism. This enables proactive security protection, safeguarding the security of the approval process.

[0064] The approval method provided in the above embodiments does not involve direct interaction between the security domain and the personal domain during the process of sending the target file from the security domain to the personal domain. Instead, the interaction occurs through the system central module, which helps ensure the security of the security domain. Simultaneously, the system central module receives the encrypted target file and the user information of the security domain user sent by the security domain upload module, but does not include the unique encryption key generated from the user information of the security domain user used to encrypt the target file. That is, the encryption key is not directly exchanged. Furthermore, the system central module only sends the encrypted target file to the personal domain download module, without decrypting and sending the decrypted target file. This ensures that if the user information obtained by the personal domain download module is inconsistent with the user information of the security domain user, decryption will fail, and the content of the encrypted target file cannot be obtained, thus guaranteeing the security of data in the security domain. Furthermore, notifying the personal domain download module of the approval identifier allows the personal domain download module to accurately identify the downloaded file without being aware of other information, which also helps ensure data security.

[0065] It should be noted that although the first user terminal includes a security domain upload module and a personal domain download module in the above embodiments, this does not mean that the methods implemented on the security domain upload module and the methods implemented on the personal domain download module must be on the same first user terminal. It is understood that since the encryption and decryption of the target files involved in the approval process utilize user information, which is not bound to the terminal but to the user, when the same user logs into different security domains and personal domains on different terminals, the steps implemented by the security domain upload module and the steps implemented by the personal domain download module in the above embodiments are implemented on different first user terminals. That is to say, the approval method provided in the above embodiments can be implemented on the same first user terminal's security domain upload module and personal domain download module, or the corresponding steps of the approval method provided in the above embodiments can be implemented on different first user terminals' security domain upload modules and personal domain download modules respectively.

[0066] Another aspect of this application embodiment provides an approval method applied to a system central module, which is located on a server. The server can be a standalone server device or a cluster of server devices, etc.

[0067] It should be noted that the system central module can be understood as a logical module in the server. In practical applications, it can be a physical unit, a part of a physical unit, or a combination of multiple physical units.

[0068] In some embodiments, such as Figure 3 As shown, the approval method applied to the system's central module includes the following steps:

[0069] Step 301: Receive the approval request sent by the security domain upload module. The approval request carries the user information of the security domain user and the encrypted target file obtained by encrypting the target file with the unique encryption key generated by the user information of the security domain user.

[0070] In this embodiment, "approval request", "security domain user", "user information", "unique encryption key", and "encrypted target file" are largely the same as in the previous embodiment, and will not be described in detail here.

[0071] Step 302: Forward the approval request to the approval domain module, so that the approval domain module can return the approval result based on the approval request.

[0072] In this embodiment, the approval request can be processed before being forwarded to the approval domain module, or the approval request can be forwarded directly to the approval domain module.

[0073] In some embodiments, the processing of approval requests can involve security checks; only approval requests that pass the checks are forwarded to the approval domain module. This further ensures the security of the approval process and helps protect the security of data within the security domain.

[0074] In some embodiments, processing the approval request can also involve modifying the address of the security domain upload module in the source address to the address of the system central module. This avoids the security domain upload module and the approval domain module being aware of each other, which helps protect the security of both modules and further ensures the security of data within the security domain.

[0075] In some embodiments, there are multiple approval domain modules, and the system central module can forward approval requests to less busy approval domain modules. This facilitates load balancing among the approval domain modules and improves approval efficiency.

[0076] Of course, the above are just specific examples. In some embodiments, approval requests can be processed in other ways, which will not be elaborated here.

[0077] Step 303: If the approval result is passed, generate an approval identifier for the encrypted target file and send the approval identifier to the personal domain download module so that after the personal domain download module sends a download request carrying the approval identifier, return the encrypted target file to the personal domain download module.

[0078] In this embodiment, different encrypted target files have different approval identifiers, that is, the approval identifier can uniquely identify the encrypted target file.

[0079] It is understandable that, since the security domain and personal domain do not interact directly in this embodiment, the personal domain download module cannot be aware of the operation of the security domain upload module. Therefore, the system center module needs to notify the personal domain download module.

[0080] In other words, the approval identifier can notify the personal domain download module to download files in a timely manner, and can also accurately identify the encrypted target file, enabling the personal domain download module to accurately request the encrypted target file based on the approval identifier, thus preventing the leakage of other files and related information.

[0081] In some embodiments, the approval method applied to the system center module further includes the following step: generating a first approval record based on the first approval information.

[0082] In this embodiment, the first approval information may include at least one of the following: user information of the security domain user and the encrypted target file, approval result, download request, and approval identifier.

[0083] The information included in the approval process is the user information of the security domain user, the encrypted target file, the approval result, the download request, and the approval identifier. In other words, the first approval record essentially records the information generated during the approval process. This way, if a security issue such as a leaked target file occurs, the first approval record can be used to trace back and pinpoint the location of the security problem, allowing for targeted protection and improving the security of the approval process.

[0084] In some embodiments, the system central module is also deployed with a filter driver and / or a hook mechanism, which enables the system central module to be protected against process debugging, memory dumping, packet capture, and hooking.

[0085] In other words, the approval methods applied to the system's central module also include: invoking filter drivers and / or hook mechanisms. This enables proactive security protection, safeguarding the security of the approval process.

[0086] The approval method provided in the above embodiments does not involve direct interaction between the security domain and the personal domain during the process of sending the target file from the security domain to the personal domain. Instead, the interaction occurs through the system central module, which helps ensure the security of the security domain. Simultaneously, the system central module receives the encrypted target file and the user information of the security domain user sent by the security domain upload module, but does not include the unique encryption key generated from the user information of the security domain user used to encrypt the target file. That is, the encryption key is not directly exchanged. Furthermore, the system central module only sends the encrypted target file to the personal domain download module, without decrypting and sending the decrypted target file. This ensures that if the user information obtained by the personal domain download module is inconsistent with the user information of the security domain user, decryption will fail, and the content of the encrypted target file cannot be obtained, thus guaranteeing the security of data in the security domain. Furthermore, notifying the personal domain download module of the approval identifier allows the personal domain download module to accurately identify the downloaded file without being aware of other information, which also helps ensure data security.

[0087] Another aspect of this application embodiment provides an approval method applied to an approval domain module located in a second user terminal. The second user terminal is a terminal for administrators, specifically an electronic device such as a computer, PC, or server. Administrators are primarily users who manually approve approval requests.

[0088] It should be noted that the terms "first" and "second" in the aforementioned "second user terminal" and the "first user terminal" in the previous and subsequent embodiments are mainly used to distinguish user terminals with different characteristics and do not have any actual meaning. For example, a user of a certain terminal usually approves approval requests from other terminals as an administrator, but may still have the need to send files from outside the security domain to the personal domain at times. In this case, the system center can forward the approval request to other terminals for users of those terminals to approve as administrators. This will not be elaborated further here.

[0089] It should also be noted that the system approval domain module can be understood as a logical module in the second user terminal. In practical applications, it can be a physical unit, a part of a physical unit, or a combination of multiple physical units.

[0090] In some embodiments, such as Figure 4 As shown, the approval method applied to the approval domain module may include the following steps:

[0091] Step 401: Receive the approval request sent by the system center module. The approval request carries the user information of the security domain user and the encrypted target file obtained by encrypting the target file with the unique encryption key generated by the user information of the security domain user.

[0092] In this embodiment, "approval request," "security domain user," "user information," "unique encryption key," and "encrypted target file" are largely the same as in the previous embodiments, and will not be described in detail here.

[0093] Step 402: Approve the approval request based on the user information of the security domain user and the encrypted target file.

[0094] In this embodiment, step 402 involves using the user information of the security domain user and the encrypted target file as the basis for approval to determine whether the approval request can be approved.

[0095] In some embodiments, a human-involved approval process can be introduced. That is, the approval request can be approved based on the user information of the security domain user and the encrypted target file. This can be achieved by prompting the administrator to approve the approval request based on the user information of the security domain user and the encrypted target file, so that the administrator can obtain the approval result.

[0096] The notification methods can include SMS, email, ringtone, and voice. In some cases, the approval domain module can also provide a visual interface, displaying text notifications to the user indicating pending approval requests. When the user selects the request in the visual interface, they can view the user information of the security domain user corresponding to the request and the encrypted target file. Based on this information, the user can then input their information on the visual interface to inform the approval domain module administrator of their decision on whether to approve the request.

[0097] In some embodiments, the approval domain module can also deploy some approval policies, and then automatically match the corresponding policies based on the user information of the security domain user and the encrypted target file to approve the approval request.

[0098] Of course, the above is only an example of step 402. In some embodiments, step 402 can also be implemented in other ways, which will not be described in detail here.

[0099] Understandably, the information presented by the encrypted target file is relatively limited. Sometimes, to more accurately approve approval requests, the content of the target file is used as the basis for approval. Specifically, in some embodiments, approval requests are processed based on the user information of the security domain user and the encrypted target file, which can be achieved as follows: a unique decryption key is generated based on the user information of the security domain user; the encrypted target file is decrypted using the unique decryption key to obtain the target file; and the approval request is processed based on the user information of the security domain user and the target file.

[0100] In other words, the encrypted target file is decrypted based on the user information received from the security domain user to obtain the target file. This allows the approval process to refer to the content of the target file to make decisions, enabling more accurate approvals based on more comprehensive information and further ensuring the security of the approval process.

[0101] It should be noted that, in order to ensure the information security of the target file, the decryption performed by the approval domain module is temporary. For example, the decrypted file needs to be deleted in time after decryption, which will not be elaborated here.

[0102] Step 403: Send the approval result to the system central module.

[0103] This embodiment does not limit the form of the approval result. It may be that the system central module returns information containing "pass" (or "fail"), or information containing "success" or "failure".

[0104] Of course, the above are just specific examples. In some embodiments, a response may be sent to the system center when passage is possible, but no response is sent when passage is not possible. These will not be elaborated upon further here.

[0105] In some embodiments, the approval method applied to the approval domain module further includes the following step: generating a second approval record based on the second approval information.

[0106] In this embodiment, the second approval information may include at least one of the following: user information of the security domain user, encrypted target file, approval result, and information of the administrator.

[0107] The information included in the approval process is the user information of the security domain user, the encrypted target file, the approval result, the download request, and the approval identifier. In other words, the first approval record essentially records the information generated during the approval process. This way, if a security issue such as a leaked target file occurs, the first approval record can be used to trace back and pinpoint the location of the security problem, allowing for targeted protection and improving the security of the approval process.

[0108] In some embodiments, after generating a second approval record based on the second approval information, the approval method applied to the approval domain module further includes: sending the second approval record to the system center module for the system center module to store the received second approval record.

[0109] In other words, the approval records generated by the approval domain module must also be reported to the system's central module for further storage. This way, even if the approval domain module experiences record leaks or tampering, the system's central module can still be used to trace back to the point where the security issue occurred. This facilitates better maintenance of relevant records, protects record security, and further enhances overall security.

[0110] In some embodiments, the approval method applied to the approval domain module further includes the following steps: during the approval process of the administrator, restricting the administrator's external operations, which include at least one of the following: cutting, screenshotting, taking pictures, and sending.

[0111] It is understandable that the approval domain module may also have problems, such as information leakage caused by administrators. Therefore, restrictions are also placed on the administrator's external operations, which can further improve the security of approval from the administrator's side.

[0112] The approval method provided in the above embodiments, when approving whether a target file is allowed to be sent from the security domain to the personal domain, does not allow the approval domain module to interact directly with the security domain, but instead interacts through the system center module. This helps ensure the security of the security domain. Simultaneously, the approval domain module receives the encrypted target file and the user information of the security domain user sent by the system center module, but does not include the unique encryption key generated from the security domain user's user information used to encrypt the target file. That is, it does not directly exchange the encryption key, so if the user information obtained by the personal domain download module is inconsistent with the user information of the security domain user, it will be unable to decrypt the file and thus unable to obtain the content of the encrypted target file, ensuring the security of data in the security domain.

[0113] To help those skilled in the art better understand the approval method provided in the above embodiments, its interaction process will be described below.

[0114] In some embodiments, such as Figure 5 As shown, the approval methods include:

[0115] Step 501: The secure domain upload module obtains the user information of the secure domain user and generates an encrypted target file based on the user information of the secure domain user.

[0116] Step 502: The security domain upload module sends an approval request to the system center module, carrying the user information of the security domain user and the encrypted target file.

[0117] Step 503: The system center module forwards the received approval request to the approval domain module.

[0118] Step 504: The approval field module approves the approval request.

[0119] Step 505: The approval domain module returns the approval result to the system center module.

[0120] Step 506: If the received approval result is "passed", the system center module generates an approval identifier for the encrypted target file.

[0121] Step 507: The system center module sends an approval identifier to the personal domain download module.

[0122] Step 508: The personal domain download module sends a download request to the system center module based on the received approval identifier.

[0123] Step 509: The system center module sends the encrypted target file to the personal domain download module according to the download request.

[0124] Step 510: The personal domain download module obtains the user information of the personal domain user and decrypts the received encrypted target file based on the user information of the personal domain user.

[0125] The secure domain upload module is located in the secure domain of the first user terminal, the system center module is located on the server, the approval domain module is located in the second user terminal, and the personal domain download module is located in the personal domain of the first user terminal.

[0126] It should be noted that since the users of the security domain and personal domain of a terminal are mobile—for example, a user can log in to the security domain of terminal A at time 1 and then log in to the personal domain of terminal B at the next time—the first user terminals to which the security domain upload module and the personal domain download module belong in this embodiment can be the same terminal or different terminals. This embodiment does not limit this; that is, a user can initiate an approval request through the security domain upload module on first user terminal C, and then obtain the encrypted target file through the personal domain download module on another first user terminal D. Whether the first user terminals to which the security domain upload module and the personal domain download module belong are the same or different terminals has no impact on the success of decryption. The main factor affecting the success of decryption is whether the security domain user and the personal domain user are the same user.

[0127] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this patent.

[0128] Another aspect of this application embodiment also provides an approval system, such as Figure 6 As shown, it includes: a security domain upload module 601, a system center module 602, an approval domain module 603, and a personal domain download module 604. The security domain module 601 is located in the security domain of the first user terminal 600, the system center module 602 is located on the server 700, the approval domain module 603 is located on the second user terminal 800, and the personal domain download module 604 is located in the personal domain of the first user terminal 600.

[0129] Specifically, the security domain upload module 601 is used to implement the approval method applied to the security domain upload module as described in any of the above embodiments; the system center module 602 is used to implement the approval method applied to the system center module as described in any of the above embodiments; the approval domain module 603 is used to implement the approval method applied to the approval domain module as described in any of the above embodiments; and the personal domain download module 604 is used to implement the approval method applied to the personal domain download module as described in any of the above embodiments.

[0130] In some embodiments, such as Figure 6 As shown, the number of secure domain upload modules 601 and personal domain download modules 604 is N. There is a one-to-one correspondence between secure domain upload modules 601 and personal domain download modules 602. The corresponding secure domain upload modules 601 and personal domain download modules 602 are located in the same first user terminal 600, where N is an integer greater than 2.

[0131] In this way, multiple secure domain upload modules and multiple personal domain download modules are deployed in the approval system to provide the function of uploading encrypted target files from the secure domain to the system central module and downloading encrypted target files from the system central module to the personal domain. This enables the target files to be sent from the secure domain to the personal domain, which helps to improve the high availability and carrying capacity of the approval system.

[0132] It is not difficult to see that this embodiment is a system embodiment corresponding to the foregoing embodiments, and this embodiment can be implemented in conjunction with the foregoing method embodiments. The relevant technical details mentioned in the foregoing method embodiments are still valid in this embodiment, and will not be repeated here to reduce repetition. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the foregoing method embodiments.

[0133] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this application, this embodiment does not introduce units that are not closely related to solving the technical problems proposed in this application; however, this does not mean that other units are absent in this embodiment.

[0134] Another aspect of this application embodiment also provides an electronic device, such as... Figure 7 As shown, it includes: at least one processor 701; and a memory 702 communicatively connected to at least one processor 701; wherein the memory 702 stores instructions executable by at least one processor 701, the instructions being executed by at least one processor 701 to enable at least one processor 701 to perform the approval method described in any of the above method embodiments.

[0135] The memory 702 and processor 701 are connected via a bus, which can include any number of interconnecting buses and bridges. The bus connects various circuits of one or more processors 701 and memory 702 together. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 701 is transmitted over a wireless medium via an antenna, which further receives data and transmits it to processor 701.

[0136] Processor 701 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory 702 can be used to store data used by processor 701 during operation.

[0137] Another aspect of this application provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the above-described method embodiments.

[0138] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0139] Those skilled in the art will understand that the above embodiments are specific embodiments for implementing this application, and in practical applications, various changes can be made to them in form and detail without departing from the spirit and scope of this application.

Claims

1. An approval method, characterized in that, The method is applied to a first user terminal, which includes a secure domain upload module and a personal domain download module. The secure domain upload module is located in the secure domain of the first user terminal, and the personal domain download module is located in the personal domain of the first user terminal. The method includes: The system obtains user information of the security domain user through the security domain upload module, generates a unique encryption key based on the user information, encrypts the target file in the security domain using the unique encryption key, generates an approval request carrying the user information of the security domain user and the encrypted target file, and sends it to the system center module. The system center module forwards the approval request to the approval domain module for approval. After the approval domain module approves the approval request, the system center module sends the encrypted target file to the personal domain download module. The system center module is located on a server outside the first user terminal.

2. The approval method according to claim 1, characterized in that, After generating an approval request carrying the user information of the security domain user and the encrypted target file through the security domain upload module and sending it to the system center module, the method further includes: The personal domain download module receives the approval identifier issued by the system center module, generates a download request carrying the approval identifier, and sends the download request to the system center module, so that the system center module can return the encrypted target file according to the download request; The personal domain download module obtains the user information of the personal domain user, generates a unique decryption key based on the personal domain user information, and decrypts the encrypted target file based on the unique decryption key to obtain the target file.

3. The approval method according to claim 2, characterized in that, After decrypting the encrypted target file using the unique decryption key, the method further includes: Before presenting the target file to the user, a blind watermark is added to the target file based on the file association information, which includes at least one of the following: the user information of the personal domain user, the download time, and the approval identifier.

4. The approval method according to any one of claims 1 to 3, characterized in that, The approval request also carries at least one of the following information: the time when the security domain user initiated the approval, and the reason why the security domain user initiated the approval.

5. An approval method, characterized in that, Applied to a system central module, wherein the system central module is located on a server, the method includes: Receive an approval request sent by the security domain upload module. The approval request carries the user information of the security domain user and the encrypted target file obtained by encrypting the target file with a unique encryption key generated by the user information of the security domain user. The approval request is forwarded to the approval domain module, which then returns the approval result based on the approval request. If the approval result is passed, an approval identifier for the encrypted target file is generated and sent to the personal domain download module, so that after the personal domain download module sends a download request carrying the approval identifier, the encrypted target file is returned to the personal domain download module; Both the secure domain upload module and the personal domain download module are located in the first user terminal.

6. The approval method according to claim 5, characterized in that, The method further includes: Based on the first approval information, a first approval record is generated. The first approval information includes at least one of the following: the user information of the security domain user and the encrypted target file, the approval result, the download request, and the approval identifier.

7. An approval method, characterized in that, The method, applied to an approval domain module located in a second user terminal, includes: The system receives an approval request forwarded by the security domain upload module from the system center module. The approval request carries the user information of the security domain user and the encrypted target file obtained by encrypting the target file with a unique encryption key generated from the user information of the security domain user. The approval request is approved based on the user information of the security domain user and the encrypted target file; The system center module sends the approval result to the system center module so that after the system center module receives the approval result of the approval domain module for the approval request and the approval request is approved, the system center module will send the encrypted target file to the personal domain download module. Both the secure domain upload module and the personal domain download module are located in the first user terminal.

8. The approval method according to claim 7, characterized in that, The step of approving the approval request based on the user information of the security domain user and the encrypted target file includes: The administrator is prompted to approve the approval request based on the user information of the security domain user and the encrypted target file, and the approval result is obtained.

9. The approval method according to claim 8, characterized in that, The method further includes: A second approval record is generated based on the second approval information, which includes at least one of the following: user information of the security domain user, the encrypted target file, the approval result, and the information of the administrator.

10. The approval method according to claim 9, characterized in that, After generating the second approval record based on the second approval information, the method further includes: The second approval record is sent to the system center module, so that the system center module can store the received second approval record.

11. The approval method according to any one of claims 8 to 10, characterized in that, The method further includes: During the approval process of the management personnel, the disclosure of their operations is restricted. The disclosure operations include at least one of the following: cutting, screenshotting, taking pictures, and sending.

12. The approval method according to claim 7, characterized in that, The step of approving the approval request based on the user information of the security domain user and the encrypted target file includes: A unique decryption key is generated based on the user information of the security domain user; The encrypted target file is decrypted using the unique decryption key to obtain the target file; The approval request is approved based on the user information of the security domain user and the target file.

13. An approval system, characterized in that, include: The system includes a secure domain upload module, a system center module, an approval domain module, and a personal domain download module. The secure domain module is located in the secure domain of the first user terminal, the system center module is located on the server, the approval domain module is located in the second user terminal, and the personal domain download module is located in the personal domain of the first user terminal. Wherein, the first user terminal is used to implement the approval method as described in any one of claims 1 to 4 based on the security domain upload module and the personal domain download module; The system central module is used to implement the approval method as described in claim 5 or 6; The approval domain module is used to implement the approval method as described in any one of claims 7 to 12.

14. The approval system according to claim 13, characterized in that, The number of secure domain upload modules and personal domain download modules is N. The secure domain upload modules and personal domain download modules correspond one-to-one, and the corresponding secure domain upload modules and personal domain download modules are located on the same first user terminal. N is an integer greater than 2.

Citation Information

Patent Citations

  • Document outgoing control system and method

    CN103561091A

  • File outgoing method and file outgoing system

    CN110351329A