Cloud scene application software security protection and efficient operation and maintenance method
By embedding security management components and working collaboratively with remote operation and maintenance centers in a PaaS scenario, real-time monitoring of application behavior and insertion of security check logic solve the application security challenges in cloud scenarios in existing technologies, achieving defense against zero-day vulnerabilities and efficient runtime security assurance.
Patent Information
- Application Number
- CN202411175490.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-26
- Publication Date
- 2024-11-22
AI Technical Summary
In PaaS scenarios, application security is difficult to defend against attacks that trigger program vulnerabilities by constructing inputs. Existing firewalls and control flow integrity technologies are not very applicable in cloud scenarios, making it difficult to guarantee the security and integrity of applications and systems.
By embedding security management components into program logic, combined with hardware root of trust and remote security operations and maintenance center, hierarchical verification strategies and trust models are implemented, application behavior is monitored in real time, security check logic is inserted in key locations, behavioral verification and environmental monitoring are performed, and multi-level security policies and trust mechanisms are used to improve verification efficiency.
It effectively defends against zero-day vulnerabilities, improves the runtime security and verification efficiency of applications in cloud scenarios, is suitable for different types of applications, and features low overhead and real-time performance.
Smart Images

Figure CN119004481A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of the combination of computer software security, software protection, and software operation and maintenance, and specifically relates to a cloud scenario application software security protection and efficient operation and maintenance method. Background Art
[0002] In recent years, with the development of cloud computing, big data and the Internet of Things, more and more information systems are deployed on the cloud, and Platform-as-a-Service (PaaS) is one of the popular deployment methods. In the PaaS scenario, the PaaS provider provides a cloud runtime environment including hardware architecture, operating system, and necessary software components, while the application provider can run its own application on the cloud at a lower cost through the environment provided by the former. However, while this cooperation method provides great convenience, security issues should not be underestimated. On the one hand, applications deployed on the cloud are naturally exposed to the complex Internet environment, and attackers can attack them through various management and maintenance interfaces without personally contacting the server; on the other hand, a single server in PaaS often runs programs from multiple different application providers. Once an attacker successfully disguises himself as an application provider and uploads a malicious program, it may attack other applications in the same environment or even the same LAN.
[0003] Through the introduction of trusted hardware (such as Trusted Platform Module) and trusted startup mechanisms, the security of the system and runtime environment controlled by the PaaS provider is easier to ensure, while the security of user application software is more challenging. When the application content and behavior logic are uncontrollable, the PaaS provider needs to protect the user's application from attacks from external attackers on the one hand, and on the other hand, it also needs to prevent malicious attackers from uploading and running malicious programs to the system as application providers and then breaking into the system and other applications running on the same node. Currently, a very common attack method is to construct the input of the application, such as constructing commands, codes, data, etc., to trigger specific vulnerabilities in the program, thereby achieving the attack effect. In protecting against this type of attack, the mechanism selected by the PaaS provider needs to ensure sufficient effectiveness on the one hand, and efficiency on the other hand to avoid introducing excessive overhead.
[0004] One of the main ideas for defending against this type of attack is to check input data, and the representative technology is firewalls. However, firewalls cannot truly analyze the impact of input data on the internal logic of the program, and it is difficult to distinguish and defend against inputs that can trigger zero-day vulnerabilities in the program. Another major technology is the control flow integrity technology embedded in the program, which defends against attacks by ensuring the control flow. However, in cloud scenarios, most applications are developed in high-level languages such as Java and Python, and vulnerability triggering is not reflected in the control flow. This technology is not very applicable in cloud scenarios. Summary of the invention
[0005] Under the above-mentioned scenario requirements and security goals, the purpose of the present invention is to provide an application software security protection and efficient operation and maintenance method for cloud scenarios, which protects the security integrity of applications and systems by collaboratively verifying the behavior of applications through embedded program logic and security management components, and improves the verification efficiency in multiple application scenarios by introducing credibility models and hierarchical verification strategies, thereby efficiently ensuring the runtime security of applications in cloud scenarios.
[0006] To achieve the above-mentioned purpose of the invention, an embodiment provides a method for security protection and efficient operation and maintenance of application software in a cloud scenario. The system implementing the method includes a hardware trusted root, a conventional functional component, a security management component, and a remote security operation and maintenance center. The method includes the following steps: Based on the hardware trusted root and through the trusted startup mechanism, the conventional functional components and security management components are started to ensure the integrity of the operation. After the security management component reveals its identity to the remote security operation and maintenance center, the security management component establishes a secure communication channel with the remote security operation and maintenance center. The security operation and maintenance center sends the latest security policy to the security management component through the secure communication channel to make it ready for configuration; When the user application starts running, the security management component inserts the security check logic into the key running position of the user application and uses it as the check logic position. When the user application runs to the check logic position, the verification operation is triggered. The security check logic packages the relevant running information into the verification request and sends it to the security management component. The security management component verifies based on the relevant running information in the verification request and the latest security policy, and returns the verification result to decide whether to allow the program to perform subsequent operations.
[0007] Preferably, the security management component performs identity disclosure to the remote security operation and maintenance center, including: pre-installing a unique identity ID and a disclosure key into a program package when distributing the security management component, encrypting the ID with the disclosure key after the security management component is run, and then disclosing itself to the remote security operation and maintenance center, thereby achieving identity authentication and node binding of the security management component; The security management component establishes a secure communication channel with the remote security operation and maintenance center, including: after the security management component completes identity disclosure, it negotiates with the remote security operation and maintenance center to reach a session key, and encrypts information with the session key to prevent information spoofing, so as to build a secure communication channel.
[0008] Preferably, the latest security policy issued is in the form of a black and white list, including a judgment strategy for abnormal behavior of the system and program, a processing strategy and a reporting strategy corresponding to the abnormal behavior, wherein the judgment strategy includes abnormal interface call parameter characteristics and abnormal file access behavior characteristics, and the processing strategy and reporting strategy corresponding to the abnormal behavior include only recording in the log, sending warnings to a remote security operation and maintenance center, and terminating abnormal programs.
[0009] Preferably, key running positions are divided into three categories: code / class loader, which is the entry point for code to enter the program running. Security check logic is inserted at this position to prevent the loading and running of some high-risk code / classes; program internal functions, which can prevent the running of some functions in a large library / large class or prevent some high-risk function internal logic; program external call interface, which can distinguish and prevent high-risk external call behaviors according to the application calling behavior.
[0010] Preferably, the relevant operation information is context information necessary for the security management component to perform verification, including a call stack, important global variables, and call parameters, and may also include other custom information collected in the application.
[0011] Preferably, the security management component performs verification according to the relevant operation information in the verification request and based on the latest security policy, and returns the verification result to determine whether to allow the program to perform subsequent operations, including: The security management component uses the relevant operating information in the verification request to match it with the latest security policy to determine whether the verification is successful and take further action based on the latest security policy. Specifically, when the verification is successful, the security check logic in the application will block the program before receiving the verification result and will continue to run after receiving the verification result. For verification failures, the security detection logic directly terminates subsequent operations and returns. The security management component can also alert the remote security operation and maintenance center or directly terminate the application through system signals.
[0012] Preferably, the method further comprises: the security management component maintains the real-time credibility of each of the multiple applications running on the same node according to a predefined policy, and verifies the real-time credibility of the application based on multiple level policies included in the latest security policy during the verification operation.
[0013] Preferably, the credibility is a real-time value that measures the trusted state of an application during its operation, which is between a predefined maximum and minimum value. During the operation, the probability of an application being hacked by an attacker will gradually increase, so the credibility decreases with the running time. Different applications have different credibility decrease rates due to their code volume and logic complexity, and the credibility of applications that are easily hacked decreases quickly. Accordingly, a credibility threshold is introduced, and the application is divided into a trusted state and an untrusted state by the credibility threshold, which is compatible with the existing binary concept. The multi-level strategy included in the latest security policy means that security policy rules are divided into two groups or more according to their importance and necessity. For applications with high real-time credibility, only the strict rule set can be used for verification, while applications with low real-time credibility can be verified using the broad rule set or the complete rule set. In the case of high concurrent verification requests, the time of rule matching and verification process is reduced, and the verification efficiency of the mechanism is improved.
[0014] Preferably, the method also includes: the security management component regularly performs environmental checks to ensure the integrity and security of the software operating environment, mainly checking important files of applications and systems running in parallel with the applications. The former identifies malicious processes by process scanning and checking process paths and resource usage characteristics, and the latter ensures that important executable files and configuration files have not been tampered with through file hash verification.
[0015] Preferably, the method also includes: the security management component regularly communicates with a remote security operation and maintenance center to report records, wherein the records include information about the security management component's own status and important configurations, information about interaction with user applications for verification, and information about important files in the environment and other process scan results; the records are encrypted in the file system and in the reported communication session to prevent information forgery, and the hash summary value of each new record is also extended to the TPM register, and the authenticity of the record is proved through TPM remote authentication.
[0016] Compared with the prior art, the present invention has the following beneficial effects: (1) The present invention implements a more effective runtime security detection mechanism through application behavior judgment, and has a certain ability to defend against zero-day vulnerabilities and bypass attacks.
[0017] (2) The present invention improves the verification efficiency in multi-application high-load scenarios through multi-level security strategies and credibility updates, and can ensure low overhead and real-time performance of application runtime metrics.
[0018] (3) The application defense mechanism implemented by the present invention has good versatility and can be applied to application programs of different types and logics, and can also be combined with other defense mechanisms. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0020] Figure 1 It is the relationship structure of each component in the initial establishment process and operation process of the system provided by the embodiment; Figure 2 It is an application layer protection implementation architecture diagram provided by an embodiment; Figure 3 It is an implementation diagram of the application layer security protection and efficient operation and maintenance provided by Implementationli to optimize the efficiency of multiple application scenarios. DETAILED DESCRIPTION
[0021] To make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific implementation methods described herein are only used to explain the present invention and do not limit the scope of protection of the present invention.
[0022] The embodiment of the present invention provides a cloud scenario application software security protection and efficient operation and maintenance system including hardware trusted root, conventional functional components, security management components, and remote security operation and maintenance center. The hardware trusted root is composed of a trusted hardware module (such as TPM) and a BIOS boot block. Through the isolation and anti-tampering characteristics at the hardware level, the integrity of the initial startup of the system is guaranteed, and the anti-counterfeiting and anti-tampering guarantee of log records is also provided during operation.
[0023] Conventional functional components include BIOS boot block, BIOS, boot loader, host operating system, user application and other functional components that are common in conventional systems. These components are the main bodies for realizing user functions and providing user services.
[0024] The security management component is a new component added at the application layer that is specifically responsible for the security of user applications. Its functions include performing environmental checks and maintaining environmental integrity, completing runtime verification based on configuration policies and in collaboration with application security detection logic, supporting real-time management of remote security operation and maintenance centers through record reporting and policy collection, and achieving efficient verification of applications by maintaining credibility information and multi-level security policies.
[0025] The remote security operation and maintenance center is a system administrator and maintainer who is set up on a node different from the application. It does not run on the same device as the system but is connected to the system through the Internet. The specific form can be the operation and maintenance personnel of the cloud service provider or the operation and maintenance terminal equipment directly managed by the user. It can realize runtime monitoring of multiple nodes by collecting log records, and adjust the security logic of the system in real time by issuing security policies.
[0026] Based on the above system embodiment, a cloud scenario application software security protection and efficient operation and maintenance method is provided. First, the initial integrity state of the system is guaranteed through a trusted startup mechanism. Then, during operation, the security check logic inserted in the application, the local security management component and the remote security operation and maintenance center jointly assume the functions of protection and operation and maintenance. Figure 1 As shown, the following steps are included: When the system starts, the conventional functional components are started based on the hardware trusted root and through the trusted startup mechanism to ensure the integrity of the operation. That is, each component will be checked for the integrity of the image hash by the previous component before loading and running, and the verification result is saved by the TPM register to prevent tampering. Specifically, during the trusted startup process, the BIOS startup block that is started first can ensure the integrity and trustworthiness of the execution code due to its read-only feature. This component will measure the remaining part of the BIOS and record the measurement value in the TPM, and then transfer the execution authority. Subsequent components such as the boot loader, host operating system, and user application all go through this measurement and recording process. The values recorded in the TPM cannot be tampered with or overwritten due to the functional characteristics of the TPM. Therefore, this process ensures the integrity of each component of the system during the startup process through the image measurement value, laying the foundation for the maintenance of the system integrity during the operation process.
[0027] During operation, the local security management component is first started through a trusted startup mechanism to ensure integrity, and then it reveals its identity to the remote security operation and maintenance center for subsequent management. To achieve this process, the security management components deployed on different nodes need to be configured with a unique identity ID and a disclosure key. After the security management component is running, the ID is encrypted with the disclosure key and then revealed to the remote security operation and maintenance center, thereby achieving identity authentication and node binding of the security management component, that is, the remote security operation and maintenance center verifies the authenticity of the communicating security management component through key-encrypted secure communication and identity ID matching. After that, the remote security operation and maintenance center and the local security management component will negotiate the communication key for subsequent secure communication, and distribute the latest security policy to the local security management component through this secure channel, and the security management component configuration is ready.
[0028] When the application starts running, the security management component will insert specific security check logic into the sensitive running locations and risk interfaces of the application to trigger security checks when the program runs to these locations. These insertion locations are selected based on the pre-analysis of known risk vulnerabilities and common attack mechanisms of the program. According to different locations and characteristics, the insertion locations can be divided into three categories: code / class loader, which is the entry point for code to enter the program running, and security checks are used here to prevent the loading and running of some high-risk code / classes; program internal functions, where security checks can be used to prevent some high-risk function calls and internal logic; program external call interfaces, including local binary runtime library calls and system calls, etc., which are the exits of the running logic from the function and the location where the attack effect extends outside the program. Security checks are used to discover and prevent the program's external malicious behavior. In particular, for Java applications commonly used in cloud scenarios, this logic insertion can be implemented using Java's Instrumentation mechanism, and the ASM tool can be used to conveniently check and modify Java bytecode.
[0029] When the security check logic is triggered, the security check logic will use the behavior that the program is currently attempting to perform and the related running information as context information, and together form a verification request and send it to the local security management component. The related running information mainly includes the call stack, important global variables, call parameters, etc., and can also include other custom information collected in the application. Through the difference in this information, the security management component can distinguish between normal and abnormal behaviors of the program, and return verification results that allow or block running based on pre-configured security policies. The security logic within the program will block the program waiting for the verification result, and continue to run or return directly according to the returned result. The security management component can also take further actions on the compromised application, such as by terminating the entire program operation, sending an alert to the remote security operation and maintenance center for further analysis, etc.
[0030] During operation, the security management component is also responsible for monitoring the local operating environment to prevent potential attacks, mainly monitoring processes running in parallel with applications and important system files. Malicious processes can be identified by their execution file path, resource usage and other characteristics; important executable files, configuration files and other important system files can be protected from malicious tampering by hash verification. The functional composition of the security management component and its interactive relationship with the application are shown in the figure. Figure 2 shown.
[0031] In addition, there is a remote security operation and maintenance center in the system that runs on a different node from the application. The security administrator or operation and maintenance administrator monitors and adjusts the operating status of each node through this node. During operation, the security management component needs to maintain its own operation records, including the results of application verification, environmental scan results, etc., and report them to the security operation and maintenance center regularly. This record needs to be summarized and expanded through the TPM's PCR, and encrypted and stored in the communication channel and on the disk to prevent the falsification and tampering of the recorded information. When the security policy is updated and adjusted, it is also distributed by the security operation and maintenance center to the security management components on each node.
[0032] In multi-application scenarios, in order to improve the efficiency of local security management components in verification and reduce verification overhead, a credibility mechanism is introduced for different applications. The local security management component can use different sets of security policies during verification based on the real-time credibility of different applications, and can also configure independent security policies for applications, such as Figure 3 shown.
[0033] Credibility is a real-time, continuous value that measures the trustworthy state of an application during operation. It is between a predefined maximum and minimum value (such as 1 and 0), corresponding to the expectation that the application is in a complete state.
[0034] When the system has just completed trusted boot and started each application that has been verified by the image hash, the real-time credibility of each program is the maximum value (for example, 1). After that, during the running process, the real-time credibility of the application will decay over time until the credibility reaches the minimum value (for example, 0). This decay rate is called the credibility decay rate, which is used to represent the application i The credibility decay rate.
[0035] app The real-time credibility can be expressed as a time is a function of the independent variable: ; in is the system startup time, is the sensitivity coefficient .
[0036] The purpose of runtime verification is to restore the credibility of the application. A successful runtime verification will restore the node credibility to the maximum value, that is, in the above function formula, It can also be the time of the last successful authentication.
[0037] In order to be compatible with the existing binary concepts of trust and untrust, this system also defines a trust threshold ,if , the application is considered trusted, otherwise it is untrusted.
[0038] In a multi-application scenario, multiple applications are started after image hash verification, and the initial credibility is the maximum value. As they are constantly exposed to the risk of being attacked during operation, their credibility gradually decreases until it drops below the credibility threshold at a certain moment, and the status changes from trusted to untrusted. At this time, the application urgently needs verification. Different applications have different credibility decay rates according to their own complexity, mechanism security, and exposure. The time span from trusted to untrusted is different, and the required verification frequency is also different. Through the credibility mechanism, unnecessary verification overhead can be reduced.
[0039] In the general model of the system, the adopted security policy should be applied to all application verifications. The public security policy covers the different vulnerabilities and risks involved in different applications, and its policy set is a superset of the policy set required for each application. The public security policy set can be divided into multiple levels of security policies, for example, strict policies and loose policies. Strict policies include policies related to the most dangerous and sensitive operations that are most likely to cause damage to the system, such as system calls; loose policies include other operations that are not directly harmful, such as internal function logic calls. For trusted applications with a trustworthiness higher than the threshold, only the strict policy needs to be checked during the verification operation, and its trustworthiness is not restored. The purpose of this check is to prevent serious security risks and zero-day vulnerabilities. For untrusted applications with a trustworthiness lower than the threshold, both the strict policy and the loose policy will be checked to confirm the integrity of the application, and the trustworthiness of the application will be restored to the maximum value after successful verification.
[0040] Multiple applications use a unified public security policy by default, which should cover the risk vulnerabilities of each application. In special cases, some applications may need to use specific security policies, such as after evaluation, it is determined that some known risk libraries need to be used, and this library has been disabled in the public security policy. In this case, the application can configure a unique security policy to override the default public security policy during the verification process to allow it to perform some less secure behaviors. This custom security policy can only override the loose policy in the existing policy, and the strict policy will always be executed to ensure the integrity of the system.
[0041] The specific implementation methods described above provide a detailed description of the technical solutions and beneficial effects of the present invention. It should be understood that the above is only the most preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, supplements and equivalent substitutions made within the scope of the principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A cloud scenario application software security protection and efficient operation and maintenance method, characterized in that: The system implementing the method includes a hardware trusted root, a conventional functional component, a security management component, and a remote security operation and maintenance center. The method includes the following steps: Based on the hardware trusted root and through the trusted startup mechanism, the conventional functional components and security management components are started to ensure the integrity of the operation. After the security management component reveals its identity to the remote security operation and maintenance center, the security management component establishes a secure communication channel with the remote security operation and maintenance center. The security operation and maintenance center sends the latest security policy to the security management component through the secure communication channel to make it ready for configuration; When the user application starts running, the security management component inserts the security check logic into the key running position of the user application and uses it as the check logic position. When the user application runs to the check logic position, the verification operation is triggered. The security check logic packages the relevant running information into the verification request and sends it to the security management component. The security management component verifies based on the relevant running information in the verification request and the latest security policy, and returns the verification result to decide whether to allow the program to perform subsequent operations.
2. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1 is characterized in that: The security management component discloses its identity to the remote security operation and maintenance center, including: pre-installing a unique identity ID and a disclosure key in the program package when distributing the security management component, encrypting the ID with the disclosure key after the security management component is running, and then disclosing itself to the remote security operation and maintenance center, thereby achieving identity authentication and node binding of the security management component; The security management component establishes a secure communication channel with the remote security operation and maintenance center, including: after the security management component completes identity disclosure, it negotiates with the remote security operation and maintenance center to reach a session key, and encrypts information with the session key to prevent information spoofing, so as to build a secure communication channel.
3. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1 is characterized in that: The latest security policy issued, in the form of a black and white list, includes the judgment strategy for abnormal behavior of the system and program, the corresponding processing strategy and reporting strategy for abnormal behavior. Among them, the judgment strategy includes abnormal interface call parameter characteristics and abnormal file access behavior characteristics. The corresponding processing strategy and reporting strategy for abnormal behavior include only recording in the log, sending warnings to the remote security operation and maintenance center, and terminating abnormal programs.
4. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1 is characterized in that: Key running locations are divided into three categories: code / class loader, which is the entry point for code to enter the program. Security check logic is inserted into this location to prevent the loading and running of some high-risk code / classes; program internal functions, which can prevent the running of some functions in a large library / class or prevent some high-risk function logic; Program external call interface. Security check logic is inserted into this location, which can distinguish and block high-risk external call behaviors based on application calling behaviors.
5. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1 is characterized in that: The relevant operation information is the context information necessary for the security management component to perform verification, including the call stack, important global variables, and call parameters, and may also include other custom information collected in the application.
6. The method for security protection and efficient operation and maintenance of cloud scenario application software according to claim 1, characterized in that: The security management component verifies the relevant operation information in the verification request based on the latest security policy and returns the verification result to decide whether to allow the program to perform subsequent operations, including: The security management component uses the relevant operating information in the verification request to match it with the latest security policy to determine whether the verification is successful and take further action based on the latest security policy. Specifically, when the verification is successful, the security check logic in the application will block the program before receiving the verification result and will continue to run after receiving the verification result. For verification failures, the security detection logic directly terminates subsequent operations and returns. The security management component can also alert the remote security operation and maintenance center or directly terminate the application through system signals.
7. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1, characterized in that: Also includes: The security management component maintains the real-time credibility of multiple applications running on the same node according to predefined policies, and verifies the real-time credibility of the applications based on the multiple level policies contained in the latest security policy during the verification operation.
8. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 7, characterized in that: Credibility is a real-time value that measures the trusted state of an application during its operation, which is between a predefined maximum and minimum value. During the operation, the probability of an application being hacked by an attacker will gradually increase, so the credibility decreases with the running time. Different applications have different credibility reduction rates due to their code volume and logic complexity. The credibility of applications that are easily hacked decreases quickly. Accordingly, a credibility threshold is introduced to divide applications into trusted and untrusted states, which is compatible with the existing binary concept. The multi-level strategy included in the latest security policy means that security policy rules are divided into two groups or more according to their importance and necessity. For applications with high real-time credibility, only the strict rule set is used for verification, while for applications with low real-time credibility, the broad rule set or complete rule set is used for verification. In the case of high concurrent verification requests, the time of rule matching and verification process is reduced, and the verification efficiency of the mechanism is improved.
9. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1, characterized in that: Also includes: The security management component regularly performs environmental checks to ensure the integrity and security of the software operating environment. It mainly checks important files of applications and systems that run in parallel with the applications. The former identifies malicious processes through process scanning and checks process paths and resource usage characteristics, while the latter ensures that important executable files and configuration files have not been tampered with through file hash verification.
10. The method for cloud scenario application software security protection and efficient operation and maintenance according to claim 1, characterized in that: Also includes: The security management component regularly communicates with the remote security operation and maintenance center to report records, where the records include information about the security management component's own status and important configurations, information about interaction with user applications for verification, and information about important files in the environment and other process scan results. The records are encrypted in the file system and in the reported communication session to prevent information forgery. At the same time, the hash summary value of each new record is also extended to the TPM register, and the authenticity of the record is proved through TPM remote authentication.
Citation Information
Patent Citations
Security policy management method, device and equipment and machine readable storage medium
CN113179252A
Software protection system and method, storage medium, equipment and program product
CN118503956A
Method for systematically and objectively assessing system security risk
US11238162B1
