CN112256390B - Measurement management method and related equipment - Google Patents

Abstract

The embodiment of the invention provides a measurement management method and related equipment, wherein the measurement management method acquires a sampling command for sampling a measurement reference value of a program after the program is loaded, and the sampling command comprises a code start-stop address corresponding to the code of the program; and measuring codes in the code start-stop addresses in response to the sampling command, setting a measured measurement value as a measurement reference value of the program to measure whether the program is abnormal or not based on the measurement reference value, thereby setting the measurement reference value corresponding to the program in real time, realizing measurement of the program without being limited to a measurement target with the measurement reference value set in advance, and being flexible and convenient to use.

Description

A measurement management method and related equipment

technical field

Embodiments of the present invention relate to the technical field of trusted metrics, and in particular to a metric management method and related equipment.

Background technique

Metrics is a key technology widely used in trusted computing. It can be used to judge whether the state of the program is abnormal. Specifically, by extracting the characteristic value of the program as the measurement benchmark value, the state of the program can be judged based on the uniqueness of the characteristic value Is it abnormal.

Measurement can be divided into static measurement and dynamic measurement. Static measurement is carried out when the program (including system programs and application programs) is loaded to ensure the safety of the program when it starts; metric to ensure the safety of the program at runtime.

However, the existing measurement methods need to customize the system. Specifically, pre-select the program that can be measured as the measurement target, calculate the measurement reference value of the measurement target, and pre-set the calculated measurement reference value in the entity that implements the measurement In order to measure the program in the subsequent measurement process.

Apparently, the measurement method in the prior art can only be applied to the measurement of the program in the customized system whose measurement reference value is preset, which is inconvenient to use.

Contents of the invention

In view of this, the embodiments of the present invention provide a metric management method and related equipment, which are not limited to the metric of programs with pre-set metric reference values, and are flexible and convenient to use.

In order to achieve the above purpose, embodiments of the present invention provide the following technical solutions:

In the first aspect, an embodiment of the present invention provides a metric management method applied to a security processor, including:

After the program is loaded, acquire a sampling command for sampling the metric reference value of the program, where the sampling command includes a code start and end address corresponding to the code of the program;

In response to the sampling command, measure the code in the start and end addresses of the code, and set the measured measurement value as the measurement reference value of the program, so as to measure whether the program is abnormal based on the measurement reference value.

In a second aspect, an embodiment of the present invention provides a metric management method applied to a processor, including:

After the program is loaded, a sampling command is sent, the sampling command includes the code start and end address corresponding to the code of the program, and the sampling command is used to instruct to sample the code in the code start and end address, and the sampled metric The value is set as a metric benchmark value of the program, so as to measure whether the program is abnormal based on the metric benchmark value;

A response notification of the sampling command is acquired, and it is determined that the program sets the metric reference value.

In a third aspect, an embodiment of the present invention provides a security processor configured to execute the metric management method described in the first aspect.

In a fourth aspect, an embodiment of the present invention provides a security processor, the security processor includes a metric command processing module, a metric target list, and a metric engine, and the metric command processing module is configured to perform the metric management described in the first aspect method.

In a fifth aspect, an embodiment of the present invention provides a processor configured to execute the metric management method described in the second aspect.

In a sixth aspect, an embodiment of the present invention provides a processor, where the processor includes a metric software stack, and the metric software stack is configured to execute the metric management method described in the second aspect.

In a seventh aspect, an embodiment of the present invention provides a computer system, including: the security processor described in any one of the third to fourth aspects and the processor described in any one of the fifth to sixth aspects.

In an eighth aspect, an embodiment of the present invention provides a storage medium, which can store a program implementing the metric management method described in the first aspect, or a program implementing the metric management method described in the second aspect.

In the metric management method and related equipment provided by the embodiments of the present invention, after the program is loaded, the method acquires a sampling command for sampling the metric reference value of the program, wherein the sampling command includes the start and end of the code corresponding to the code of the program address, and then responding to the sampling command, measure the code in the start and end addresses of the code, and set the obtained measurement value as the measurement reference value of the program, so as to measure whether the program is abnormal based on the measurement reference value. It can be seen that, in the embodiment of the present invention, after the program is loaded, the metric reference value used to determine whether the program is abnormal during the metric process of the program is sampled, so that the metric reference value corresponding to the program can be set in real time to realize the measurement of the program. The measurement of the program is not limited to the measurement of the program with the measurement benchmark value set in advance, which is flexible and convenient to use.

Moreover, based on the metric reference value obtained after the program is loaded, it is not necessary to consider the changes in the code or parameters before the program is loaded, so that the metric management method described in the embodiment of the present invention can be applicable to uncertain code storage locations and operating parameters before loading. Programs (such as virtual machine programs) have a wider scope of application.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present application, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

FIG. 1 is a schematic diagram of a system architecture of a virtualized environment;

FIG. 2 is a schematic diagram of the architecture of a computer system according to an embodiment of the present invention;

FIG. 3 is a flow chart of an optional method for generating a metric reference value for a program in an embodiment of the present invention;

FIG. 4 is a flow chart of an optional method for creating a measurement target for a program in an embodiment of the present invention;

FIG. 5 is a flow chart of another optional method for creating a measurement target for a program in an embodiment of the present invention;

Fig. 6 is a flow chart of an optional method for starting and stopping the measurement program according to the embodiment of the present invention;

FIG. 7 is a flow chart of an optional method for deleting a measurement target corresponding to a program in an embodiment of the present invention;

FIG. 8 is a flow chart of an optional method for querying the abnormal state of a measurement target according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a measurement command parameter and a measurement response parameter according to an embodiment of the present invention;

Fig. 10 is a flow chart of verifying commands according to an embodiment of the present invention;

Fig. 11 is a flow chart of checking a response according to an embodiment of the present invention;

Fig. 12 is a measurement flowchart of a measurement target.

Detailed ways

It can be seen from the background technology that the existing measurement method can only be applied to the measurement of a fixed program in a custom system with a preset measurement reference value, which is inconvenient to use.

For example, in a virtualized environment, before the virtual machine is obtained by virtualization, the code storage location and operating parameters of the virtual machine program are uncertain, making it difficult to pre-set the benchmark value of the corresponding virtual machine program in the virtualized environment. Therefore, the measurement of the virtual machine program cannot be realized.

Based on this, an embodiment of the present invention provides a metric management method and related equipment. After the program is loaded, the method acquires a sampling command for sampling the metric reference value of the program, and the sampling command includes the code corresponding to the program. code starting and ending addresses; in response to the sampling command, measure the code in the code starting and ending addresses, and set the measured measurement value as the measurement reference value of the program, so as to measure the program based on the measurement reference value Is it abnormal.

It can be seen that, in the embodiment of the present invention, after the program is loaded, the metric reference value used to determine whether the program is abnormal during the metric process of the program is sampled, so that the metric reference value corresponding to the program can be set in real time to realize the measurement of the program. The measurement of the program does not need to be limited to the measurement target with the measurement benchmark value set in advance, which is flexible and convenient to use.

Moreover, based on the metric reference value obtained after the program is loaded, it is not necessary to consider the changes in the code or parameters before the program is loaded, so that the metric management method described in the embodiment of the present invention can be applicable to uncertain code storage locations and operating parameters before loading. Programs (such as virtual machine programs) have a wider scope of application.

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Virtualization technology (Virtualization) is a way to virtualize multiple virtual machines (Virtual Machine, VM) through a physical host to maximize the use of hardware resources of the physical host; in a virtualized environment, the process of creating a virtual machine In the virtual machine, the hardware resources and operating parameters allocated to the virtual machine are determined according to actual needs, so that the operating location and operating parameters of the virtual machine cannot be determined in advance. Correspondingly, the storage location of the program code of the created virtual machine, Operating parameters and the like change dynamically as creation requirements change, so that it is difficult to pre-set a measurement benchmark value corresponding to a virtual machine program in a virtualization environment. In this embodiment of the present invention, a virtualization environment is taken as an example to describe the measurement management method of the present invention.

As an optional example, FIG. 1 shows a schematic diagram of a system architecture of a virtualization environment. As shown in FIG. 1, the system architecture of a virtualization environment may include: a processor (Central Processing Unit, CPU) 1, a memory 2, an Set 3 and secure processor 4;

Wherein, the processor 1 is a very large scale integrated circuit, which can be used to interpret computer instructions and process data in computer software. The processor 1 can virtualize multiple virtual machines 11 through the virtualization technology, and the running locations and running parameters of the multiple virtual machines 11 can be configured according to actual user requirements and device status.

The security processor 4 is a specially configured processor responsible for processing security-related operations of the virtual machine. For example, the security processor 4 can perform operations such as memory encryption and decryption (for example, the security processor encrypts the initial data of the virtual machine). The security processor 4 usually has higher system authority and can directly access the hardware resources of the system, such as system memory, peripherals, etc.; at the same time, in order to ensure the data security of the security processor 4, the security processor 4 can also be configured with a dedicated Hardware resources such as internal memory and non-volatile storage (NVRAM) ensure that the data in the secure processor cannot be tampered with.

The processor 1 may be configured with a dedicated API (Application Programming Interface, Application Programming Interface) interface for communicating with the security processor 4 , so as to implement data interaction between the processor 1 and the security processor 4 . Wherein, the data interaction between the processor and the security processor can be realized by using an interrupt mechanism. For example, the process of sending can trigger an interrupt for the sender, and the receiver can respond to the interrupt process, wherein the interrupt comes with the data required for interaction.

Optionally, the security processor 4 can be arranged outside the chip of the processor 1 or integrated on the chip of the processor 1 . In a preferred example, the security processor 4 can be integrated on the chip of the processor 1 .

In this example, the security processor can be made to provide metering services. Based on the security processor configured with dedicated hardware resources, using the security processor to provide the measurement service can ensure the data security of the measurement service provided by the security processor; based on the configuration of a dedicated API interface between the security processor and the processor, the measurement can be maintained In the process, the data transmission between the security processor and the processor is safe; and, based on the system authority that the security processor can directly access the hardware resources of the system, such as system memory, peripherals, etc., it is convenient to realize the measurement of the measurement target.

As an optional example, referring to the schematic architecture diagram of a computer system shown in FIG. 2 , the security processor 4 may include a measurement command processing module 41 , a measurement target list 42 and a measurement engine 43 . Among them, the measurement command processing module 41 can process the measurement-related commands sent by the CPU, and maintain the measurement target list 42, which functions as the front end of the measurement service; the measurement target list 42 is used to save the set measurement target and the corresponding Encrypted information, address information, reference information, enabling status information and abnormal status information, etc., such as the master key corresponding to the measurement target, address range, reference value and measurement status abnormal information, etc.; the measurement engine 43 can realize the measurement target Take periodic measurements.

In the processor 1, a metric software stack 12 for interacting with the security processor 4 is configured correspondingly, for encapsulating the metric service provided on the security processor, and providing standards upward after shielding specific implementation details The metrics interface API.

It should be noted that the program used as the measurement target may be an operating system loader, an operating system kernel, an operating system, and an application program running in the operating system of a virtual machine.

As an optional implementation, FIG. 3 shows an optional method flow for generating a metric benchmark value for a program. The method flow can be executed by the system architecture shown in FIG. 2. Specifically, after the virtual machine is created, the program of the virtual machine Execute after loading, with reference to Figure 3, the method may include:

Step S01: The measurement software stack sends a sampling command for sampling the measurement reference value of the program, and the sampling command includes the start and end address of the code corresponding to the code of the program.

It can be understood that after the program is loaded, the code address of the program and the operating parameters of the program are determined. At this time, sending the sampling command to sample the measurement reference value to obtain the measurement reference value can avoid the inconsistency of the relevant data before the program is loaded. The measurement benchmark value caused by determinism is difficult to determine, so as to realize the measurement of the program.

The metric software stack may invoke sampling commands based on commands from a metric service caller. The caller of the measurement service may be a program manager in the system, or a security manager in the system. Optionally, the caller of the measurement service may also be an application program loader or a kernel module loader. Specifically, the measurement service caller may issue a corresponding command after detecting that the program is loaded, so that the measurement software stack invokes the sampling command, or, after the measurement service caller issues a command, the measurement software stack detects the program Whether the loading is complete, and after the program is loaded, call the sampling command.

Before the program is loaded, the starting and ending addresses of the corresponding codes are uncertain, but after the program is loaded, the corresponding starting and ending addresses of the codes have been determined. Correspondingly, the starting and ending addresses of the codes corresponding to the codes of the program carried in the sampling command are used to determine the measurement measurement range.

In an optional example, before sending the sampling command, the measurement command parameter of the command may be encrypted or a verification code may be generated for verification, so as to prevent command data from being stolen and tampered with.

Step S02: The measurement command processing module acquires a sampling command for sampling the measurement reference value of the program;

After the measurement software stack sends the sampling command, correspondingly, the measurement command processing module can receive the sampling command, so as to obtain the sampling command.

It should be noted that when the measurement command parameter of the command has been encrypted or verified, this step can further obtain the measurement value of the command after decrypting the measurement command parameter or generating a verification code for verification. command parameters.

Step S03: The measurement command processing module measures the code in the start and end addresses of the code in response to the sampling command, and sets the measured measurement value as the measurement reference value of the program, so as to measure the code based on the measurement reference value. Whether the above program is abnormal;

The measurement reference value is used in the measurement process of the program as a reference value for determining whether the program is abnormal.

Wherein, a preset algorithm may be used to measure the codes in the start and end addresses of the codes to obtain a corresponding measurement value, and use the measurement value as a measurement reference value.

After the measurement reference value corresponding to the program is obtained, the measurement reference value may be further stored in a measurement target list, wherein the measurement target list stores a measurement target corresponding to the program, and the measurement reference value is the same as the measurement target list. corresponding to the measurement target. Wherein, in the measurement object list, if there is already a measurement reference value corresponding to the measurement object, the measurement reference value is updated.

It should be noted that, after obtaining the metric reference value corresponding to the program, the metric command processing module further sends a response notification of the sampling command to the metric software stack.

In an optional example, before sending the response notification of the sampling command, the measurement command processing module may encrypt the measurement response parameter of the response or generate a verification code for verification, thereby preventing the response data from being stolen and tampered with.

Step S04: The measurement software stack obtains a response notification of the sampling command;

The measurement software stack may obtain the response notification of the sampling command by receiving the response notification of the sampling command sent by the measurement command processing module.

Wherein, the response notification of the sampling command is obtained, so that it can be determined that the program sets the measurement reference value, and then it can indicate that the subsequent process can perform program measurement.

It should be noted that, when the corresponding measurement response parameters are encrypted or verification codes are generated for verification, this step may further decrypt or verify the measurement response parameters, so as to obtain the measurement response parameters of the response.

It can be seen that, in the embodiment of the present invention, after the program is loaded, the metric reference value used to determine whether the program is abnormal during the metric process of the program is sampled, so that the metric reference value corresponding to the program can be set in real time to realize the measurement of the program. The measurement of the program is not limited to the measurement of the program with the measurement benchmark value set in advance, which is flexible and convenient to use.

Moreover, based on the metric reference value obtained after the program is loaded, it is not necessary to consider the changes in the code or parameters before the program is loaded, so that the metric management method described in the embodiment of the present invention can be applicable to uncertain code storage locations and operating parameters before loading. Programs (such as virtual machine programs) have a wider scope of application.

Furthermore, the measurement benchmark value of the measurement target is usually obtained based on a preset algorithm. Based on security considerations, different devices usually correspond to different calculation methods and parameters. If the measurement benchmark value is pre-calculated based on the existing technology and set in the measurement In the entity, the calculation process of the measurement reference value of the measurement target is cumbersome and inconvenient to use. However, in this application, the sampling calculation of the measurement reference value after the program is loaded can avoid the above process, thereby improving the convenience of program measurement .

In an optional example, after the program is loaded and before the measurement benchmark value is sampled, the measurement target may be further created. Specifically, FIG. 4 shows an optional method flow for creating a measurement target for a program. Referring to FIG. 4, the flow includes:

Step S11: the measurement software stack sends the measurement target creation command of the program;

The metric target creation command is used to create a metric target corresponding to the program in the metric target list, so as to record relevant parameters corresponding to the metric target based on the metric target, such as the metric reference value and status of the metric target Information and encrypted information, etc., and measure the measurement target.

The measurement target creation command may be based on the measurement service caller's command to call the measurement target creation command. Specifically, the measurement service caller may issue a corresponding command after detecting that the program is loaded, so that the measurement software stack Invoking the measurement target creation command, or, after the measurement service caller issues the command, the measurement software stack detects whether the program is loaded, and calls the measurement target creation command after the program is loaded.

It should be noted that, in order to enable the program to create the corresponding measurement target, when the measurement target creation command is invoked, the encryption or verification of the measurement command parameters may not be performed.

Step S12: the measurement command processing module acquires the measurement target creation command of the program;

After the measurement software stack sends the measurement target creation command, correspondingly, the measurement command processing module may receive the measurement target creation command, so as to obtain the measurement target creation command.

Step S13: the measurement command processing module responds to the measurement target creation command, and creates a measurement target corresponding to the program in the measurement target list;

After creating the measurement target corresponding to the program, the measurement command processing module may further initialize the measurement target, so as to realize the initial configuration of the measurement target.

It should be noted that, after creating the measurement target corresponding to the program, the measurement command processing module further sends a response notification of the measurement target creation command to the measurement software stack.

Step S14: The measurement software stack obtains the response notification of the measurement target creation command, and determines to create the measurement target of the program;

The measurement software stack may obtain the response notification of the measurement target creation command by receiving the measurement target creation command response notification sent by the measurement command processing module.

Wherein, the measurement reference value, the code start and end address and the measurement target are correspondingly stored in the measurement target list, and the measurement engine measures whether the program is abnormal based on the data in the measurement target list.

It can be understood that, in the prior art, usually before the program is loaded, a preset measurement target is created on the dedicated hardware, and further before the program is loaded, the measurement benchmark value and encrypted information of the corresponding measurement target are set, so that The measurement target cannot be dynamically created, deleted, etc., so that the adaptive adjustment of the measurement target cannot be performed. However, in this example, the measurement target can be created after the program is loaded, so that the dynamic adjustment of the measurement target can be realized.

In an optional example, after the measurement target is created by the measurement command processing module, the master key can be further negotiated to encrypt or verify the relevant measurement commands, so as to prevent the commands from being illegally invoked or tampered with. For security protection.

Specifically, with reference to the flow shown in Figure 5, after creating the measurement target based on Figure 4, before sampling the measurement reference value, steps S15 and S16 can be executed, so that the measurement management requesting party and the measurement management execution party negotiate to obtain the master key, And store the master key, so as to realize the encryption or verification of the measurement-related commands by using the master key. Wherein, the metric management requester may be the CPU side, specifically, the metric software stack. Specifically, the measurement command processing module may negotiate with the measurement software stack to obtain a master key, and correspondingly store the master key at the measurement command processing module side in the measurement target list.

The master key can provide the basis for encryption or authentication of subsequent interactions. Wherein, the specific negotiation process can be performed according to a key negotiation protocol (such as ECDH, SM2), and the master key can be used for authorization protection of commands. Optionally, within the security processor, the master key can be bound to the measurement task.

In an optional example, after sampling the measurement reference value, the startup control of the measurement task may be further performed. Specifically, FIG. 6 shows an optional method flow for starting and stopping the measurement program. Referring to FIG. 6, the flow includes:

Step S21: the measurement software stack sends the start measurement command of the program;

After sampling the measurement reference value, the measurement task of the program can be executed. Wherein, the start measurement command is used to instruct the measurement command processing module to start the measurement task of the program.

The measurement software stack may call the start measurement command of the program based on the command of the measurement service caller, and send the start measurement command, or may call the start measurement command of the program after detecting the response notification of the sampling command of the program. measure command, and send the start measure command.

In an optional example, before sending the start measurement command, the measurement command parameter of the command may be encrypted or a verification code may be generated for verification, thereby preventing command data from being stolen and tampered with.

Step S22: the measurement command processing module obtains the start measurement command of the program;

After the measurement software stack sends the measurement start command, correspondingly, the measurement command processing module may receive the measurement start command, so as to obtain the measurement start command.

It should be noted that when the measurement command parameter of the command has been encrypted or verified, this step can further obtain the measurement command of the command after decrypting the measurement command parameter or generating a verification code for verification parameter.

Step S23: In response to the start measurement command of the program, the measurement command processing module updates the enabled state of the measurement target corresponding to the program in the measurement target list to yes.

The enable state of the measurement object is yes, which is used to instruct the measurement engine to execute the measurement task on the measurement object. Optionally, the measurement task may measure the measurement target periodically.

Wherein, the enabling status of the measurement target is stored in the measurement target list, and correspondingly, the enabling status of the corresponding measurement target in the measurement target list may be updated to Yes.

Correspondingly, when the measurement engine executes the measurement task, when it determines that the enable state corresponding to the measurement object is yes, it executes the measurement of the codes in the code start and end addresses corresponding to the measurement object. In an optional example, the measurement engine may be used to perform measurement on the measurement target, and when the measurement result is abnormal, the measurement engine may send abnormal status information to the measurement software stack, and update the abnormal status information to the measurement target list.

It should be noted that, after updating the enable state of the measurement target to yes, the measurement command processing module further sends a response notification of starting the measurement command to the measurement software stack.

In an optional example, the measurement command processing module can also encrypt the measurement response parameters of the response or generate a check code for verification before sending the response notification to start the measurement command, so as to prevent the response data from being stolen and tampered with .

Step S24: The measurement software stack obtains the response notification of the start measurement command, and determines that the enabling status of the measurement target corresponding to the program is Yes;

The measurement software stack may obtain the response notification of the measurement start command by receiving the response notification of the measurement start command sent by the measurement command processing module.

It should be noted that, when the corresponding measurement response parameters are encrypted or verification codes are generated for verification, this step may further decrypt or verify the measurement response parameters, so as to obtain the measurement response parameters of the response.

Correspondingly, in this example, the stop control of the measurement task can be further performed. Continue referring to FIG. 6 , the process includes:

Step S25: the measurement software stack sends the stop measurement command of the program;

After the measurement task is started, this example can further stop the measurement task. Wherein, the stop measurement command is used to instruct the measurement command processing module to stop the measurement task of the program.

The measurement software stack may call the stop measurement command of the program based on the command of the measurement service caller and send the stop measurement command, or may call the stop measurement command of the program according to preset conditions and send the stop measurement command. Describe the stop measurement command. As an example, the measurement software stack may call the stop measurement command of the program according to the state of the program, for example, the stop measurement command of the program may be called when the program is set to sleep.

Optionally, before sending the stop measurement command, encryption or verification of the measurement command parameters of the command may be performed.

Step S26: the measurement command processing module acquires the stop measurement command of the program;

After the measurement software stack sends the stop measurement command, correspondingly, the measurement command processing module may receive the stop measurement command, so as to obtain the stop measurement command.

Optionally, when the measurement command parameter has been encrypted or verified, this step may further obtain the measurement command parameter of the command after decrypting the measurement command parameter or generating a verification code for verification.

Step S27: In response to the stop measurement command of the program, the measurement command processing module updates the enable status of the measurement target corresponding to the program in the measurement target list to No.

The enable state of the measurement target is no, which is used to instruct the measurement engine to stop the measurement target from executing the measurement task. Wherein, the enabling status of the measurement target may be stored in the measurement target list, and correspondingly, the enabling status of the corresponding measurement target in the measurement target list may be updated to No.

Correspondingly, when the measurement engine executes the measurement task, if it determines that the enable state corresponding to the measurement object is No, it stops executing the measurement of the codes in the code start and end addresses corresponding to the measurement object. Wherein, the measurement target is stopped to execute the measurement task, and the information corresponding to the measurement target (such as address range information and measurement reference value) is not deleted. After the measurement task is stopped, the measurement software stack can still resume execution of the measurement target by starting the measurement command. corresponding measurement tasks.

It should be noted that, after updating the enable state of the measurement target to No, the measurement command processing module further sends a response notification of the stop measurement command to the measurement software stack.

Optionally, before sending the sampling command response notification, the measurement response parameter of the response may also be encrypted or verified.

Step S28: The measurement software stack obtains the response notification of the stop measurement command, and determines whether to update the enable state of the measurement target corresponding to the program;

The measurement software stack may obtain the response notification of the stop measurement command by receiving the response notification of the stop measurement command sent by the measurement command processing module.

Optionally, when the measurement response parameter is encrypted or a verification code is generated for verification, this step may further decrypt or verify the measurement response parameter, so as to obtain the measurement response parameter of the response.

It can be understood that, in the prior art, the measurement tasks corresponding to the measurement targets are usually automatically executed based on the preset measurement targets and related parameters created on dedicated hardware, so that the measurement targets cannot be dynamically started, stopped, etc., thereby Unable to adjust the measurement task. However, in this example, the enabling state of the measurement target may be adjusted after sampling the measurement reference value, so as to realize the adaptive adjustment of the measurement task.

In an optional example, after the corresponding measurement target is created, the corresponding measurement target may be further deleted. Specifically, FIG. 7 shows an optional method flow for deleting a measurement target corresponding to a program. Referring to FIG. 7, the flow includes:

Step S31: the measurement software stack sends the end measurement command of the program;

The measurement task for the program can be ended after the corresponding measurement task has been created. Wherein, the end measurement command is used to instruct the measurement command processing module to end the measurement task of the program.

The measurement software stack may call the end measurement command of the program based on the command of the measurement service caller, and send the end measurement command, or call the end measurement command of the program according to a preset condition, and send the end measurement command. Describe the end measurement command. As an example, the measurement software stack may call the program end measurement command according to the state of the program, for example, the program end measurement command may be called when the program is in an end state.

Optionally, before sending the end measurement command, the measurement command parameter of the command may be encrypted or a check code may be generated for verification, thereby preventing command data from being stolen and tampered with.

Step S32: the measurement command processing module obtains the end measurement command of the program;

After the measurement software stack sends the end measurement command, correspondingly, the measurement command processing module may receive the end measurement command, so as to obtain the end measurement command.

When the measurement command parameter of the command has been encrypted or verified, this step can further obtain the measurement command parameter of the command after decrypting the measurement command parameter or generating a verification code for verification.

Step S33: The measurement command processing module deletes the measurement object corresponding to the program and the data information corresponding to the measurement object from the measurement object list in response to the end measurement command of the program.

The end measurement command is used to delete the measurement target and its corresponding data information, including the master key, address range, reference value, etc. corresponding to the measurement target. In an optional example, the measurement target It also corresponds to a random number used for information verification, and correspondingly, when corresponding to the end measurement command, the random number is also deleted at the same time.

Wherein, the measurement target and its corresponding data information are stored in the measurement target list, correspondingly, when the measurement command processing module responds to the end measurement command of the program, deletes the measurement target and the measurement target in the measurement target list its corresponding data information.

In an optional example, the deleting the measurement target and its corresponding data information may further be destroying the measurement target and its corresponding data information.

It should be noted that, after deleting the measurement target and the data information corresponding to the measurement target, the measurement command processing module further sends a response notification of ending the measurement command to the measurement software stack.

Optionally, the measurement command processing module may also encrypt the measurement response parameter of the response or generate a check code for verification before sending the response notification of the end measurement command, so as to prevent the response data from being stolen and tampered with.

Step S34: The measurement software stack obtains the response notification of the end measurement command, and determines to delete the measurement object corresponding to the program and the data information corresponding to the measurement object;

The measurement software stack may obtain the response notification of the stop measurement command by receiving the response notification of the stop measurement command sent by the measurement command processing module.

Optionally, when the corresponding measurement response parameter is encrypted or a verification code is generated for verification, this step may further decrypt or verify the measurement response parameter, so as to obtain the measurement response parameter of the response.

It can be understood that, in the prior art, the measurement tasks corresponding to the measurement targets are usually automatically executed based on the creation of preset measurement targets and related parameters on dedicated hardware, so that the measurement targets cannot achieve the corresponding deletion process, and thus cannot be measured Target adjustments. However, in this example, after the measurement target is created, the measurement target can also be deleted, so that the adaptive adjustment of the measurement target can be realized.

In an optional example, after measuring the corresponding measurement target, when the measurement result is abnormal, the measurement software stack may query the abnormal status information of the corresponding measurement target to confirm the status of the measurement target. Specifically, FIG. 8 shows an optional method flow for querying the abnormal state of a measurement target. Referring to FIG. 8 , the flow includes:

Step S41: the measurement software stack sends the measurement state query command of the program;

Wherein, the measurement status query command is used to instruct the measurement command processing module to query the status information of the measurement target corresponding to the program.

In an optional example, when the measurement engine measures the measurement target, if the measurement result is abnormal, the abnormal status information is updated to the measurement target list, and the CPU is notified to perform exception processing. To confirm that the measurement target is The abnormal state can make the measurement engine send abnormal state information to the measurement software stack, and the measurement software stack can query the measurement state.

After receiving the abnormal state information that the measurement result is abnormal, the measurement software stack may trigger the measurement software stack to invoke the measurement state query command of the program, and send the end measurement command to the measurement command processing module.

Wherein, the measurement software stack queries the abnormal status information of the measurement target to determine whether the abnormal status information of the measurement target is true.

Optionally, before sending the measurement status query command, the measurement command parameter of the command is encrypted or a check code is generated for verification, so as to prevent the command data from being stolen and tampered with.

Step S42: the measurement command processing module obtains the measurement status query command of the program;

After the measurement software stack sends the measurement status query command, correspondingly, the measurement command processing module can receive the measurement status query command.

Optionally, when the measurement command parameter of the command has been encrypted or verified, this step can further obtain the measurement command of the command after decrypting the measurement command parameter or generating a verification code for verification parameter.

Step S43: The metric command processing module queries the metric target list to obtain the status of the metric target corresponding to the program in response to the metric status query command of the program.

After obtaining the status of the measurement target, the measurement command processing module further sends a response notification including the status information of the measurement target to the measurement software stack.

Optionally, before sending the response notification, the measurement command processing module may encrypt the measurement response parameter of the response or generate a verification code for verification, so as to prevent the response data from being stolen and tampered with.

Step S44: The measurement software stack obtains the response notification of the measurement state query command, and determines the abnormal state information of the measurement target;

The measurement software stack can obtain the status information of the measurement target by receiving the measurement status query command response notification sent by the measurement command processing module, and confirm whether the measurement result of the measurement target is abnormal.

Wherein, when the measurement result of the measurement object is abnormal, the abnormal processing of the corresponding program is performed, for example, the program is terminated, and when the measurement result of the measurement object is not abnormal, the process is ended.

Optionally, when the corresponding measurement response parameter is encrypted or a verification code is generated for verification, this step may further decrypt or verify the measurement response parameter, so as to obtain the measurement response parameter of the response.

It can be understood that it is confirmed whether the measurement result of the measurement object is abnormal, so as to avoid the possibility of using false measurement state information to attack the system and improve the security of the system.

In an optional example, the security protection of the interface may be implemented in a verification manner.

Specifically, as shown in FIG. 9 , an authorization protection field is attached to each measurement command parameter and measurement response parameter except the creation measurement command, and the authorization protection field may include a random number and a check code.

Wherein, the random number is used to participate in the calculation to generate the verification code in the authorization protection domain, and the random number can be a Nonce random number (Number once, that is, an arbitrary or non-repeating random value that is only used once), and in the measurement command parameter The random number may be the random number of the caller of the measurement service on the CPU, and the random number in the measurement response parameter may be the random number corresponding to the measurement task on the security processor. The CPU measurement caller updates its own random number after completing a response verification, that is, the random number corresponding to the measurement command parameter updates the random number after each verification of the measurement response parameter data, and the security processor updates the corresponding measurement after completing the verification of a measurement command The random number of the task, that is, the random number corresponding to the measurement response parameter is updated every time the measurement command parameter is verified. The application of the random number can effectively prevent replay attacks.

The check code is used to confirm that the command or response has not been tampered with, and at the same time realize the authorization of the specified measurement task for invoking the command operation. Wherein, the verification code may be HMAC authorization code (Hash Message Authentication Code, hash message authorization code), and the elements involved in calculating the verification code corresponding to the measurement command parameter may include: measurement command parameter, the measurement command parameter The corresponding random number, the random number corresponding to the previous measurement response parameter, and one or more parameters in the consensus secret key; the elements involved in the calculation and generation of the verification code corresponding to the measurement response parameter may include: measurement response parameter, the item The random number in the command corresponding to the response, the random number corresponding to the parameter of the metric response, and one or more parameters in the consensus key. The consensus key is usually derived from the master key.

In an optional example, the generation of the authorization protection domain on the CPU, and the encryption and verification corresponding to the related commands and responses can be completed by the measurement software stack, thereby simplifying the use of the measurement service.

In an optional example, a verification process of related commands is provided. Specifically, referring to FIG. 10, the verification process of commands may include:

Step S51: the measurement software stack generates a check code of the measurement command parameter to obtain the measurement command parameter data;

After the measurement software stack calls the relevant command, before sending the relevant command, it can be based on the measurement command parameter, the random number corresponding to the measurement command parameter, the random number corresponding to the previous measurement response parameter, and one or more of the consistency key. parameters to generate a check code corresponding to the parameters of the measurement command.

After the check code of the measurement command parameter is generated, the measurement command parameter data is composed of the measurement command parameter, the check code and the random number corresponding to the measurement service caller, and the measurement command parameter data is sent.

Wherein, the measurement command parameter may be a command parameter in a sampling command, a start measurement command, a stop measurement command, an end measurement command, or a measurement status query command.

Step S52: The measurement command processing module receives the parameter data of the measurement command.

Step S53: The measurement command processing module verifies the measurement command parameter data according to the verification code, and determines the measurement command parameter corresponding to the measurement command.

Based on the measurement command parameter in the measurement command parameter data, the random number corresponding to the measurement command parameter, and the random number and consistency key corresponding to the previous measurement response parameter in the security processor, the verification code can be realized verification.

In another optional example, a verification process of related responses is provided. Specifically, referring to FIG. 11, the verification process of responses may include:

Step S54: the measurement command processing module generates a check code of the measurement response parameter, and obtains measurement response parameter data;

After the measurement command processing module responds to the relevant command, before sending the relevant response notification, it can be based on the measurement response parameter, the random number in the command corresponding to the response, the random number corresponding to the measurement command parameter, and the consistency key. One or more parameters, generating a check code corresponding to the parameters of the measurement command.

After the check code of the measurement response parameter is generated, the measurement response parameter data, the check code and the random number corresponding to the measurement command parameter are used to form measurement response parameter data, and the measurement response parameter data is sent.

Wherein, the measurement response parameter may be a response parameter obtained after responding to the sampling command, start measurement command, stop measurement command, end measurement command, or measurement status query command.

Step S55: The measurement software stack receives measurement response parameter data.

Step S56: The metric response software stack verifies the metric response parameter data according to the check code, and determines the metric command parameter corresponding to the metric response.

Based on the metric response parameter in the metric response parameter data, the random number corresponding to the metric response parameter, and the random number and consistency key corresponding to the previous metric response parameter on the CPU side, the verification of the check code can be realized .

In an optional example, the embodiment of the present invention also provides a measurement process of the measurement engine. Specifically, referring to FIG. 12 , the measurement process of the measurement target may include:

Step S61: Obtain the measurement target;

The measurement engine can periodically obtain the measurement target from the measurement target list, so as to measure the measurement target.

It can be understood that, while acquiring the measurement target, the start and end addresses of the code corresponding to the measurement target are also obtained from the measurement target list, so as to measure the program code.

Step S62: Determine the enabling status of the measurement target, and determine whether the measurement target is enabled.

Optionally, the measurement engine may query the enabling state of the measurement target from the measurement target list, so as to determine whether the measurement target is enabled.

Wherein, if the enabled state of the measurement target is Yes, continue to perform subsequent steps to measure the measurement target; if the enabled state of the measurement target is No, return to step S61 to obtain the measurement target again.

Step S63: Measure the measurement target to obtain the measurement value of the measurement target.

Measurement is usually implemented by calculating the Hash value of the measurement target. From the Hash value, it can be judged whether the measurement target has been tampered with. In this example, the Hash algorithm can be SM3, SHA1 or SHA256.

Step S64: Compare the measurement value of the measurement target with the measurement reference value, and determine whether the measurement target is abnormal.

Wherein, when the measurement target is abnormal, execute step S65, and when the measurement target is not abnormal, return to step S61 to obtain the measurement target again.

Step S65: Send out an exception handling notification, and update the abnormal state information of the measurement target.

When the measurement target is abnormal, an exception handling notification is sent to the CPU side, and at the same time, the abnormal state information of the corresponding measurement target in the measurement target list is updated as abnormal.

In the embodiment of the present invention, after the program is loaded, the measurement reference value used to determine whether the program is abnormal during the measurement process of the program is sampled, so that the measurement reference value corresponding to the program can be set in real time, and the measurement of the program is realized. Instead of being limited to the measurement of programs with preset measurement benchmark values, it is flexible and convenient to use.

Moreover, based on the metric reference value obtained after the program is loaded, it is not necessary to consider the changes in the code or parameters before the program is loaded, so that the metric management method described in the embodiment of the present invention can be applicable to uncertain code storage locations and operating parameters before loading. Programs (such as virtual machine programs) have a wider scope of application.

Optionally, the embodiments of the present invention may further provide a security processor, configured to execute the above-mentioned metric management method based on the perspective of the security processor.

Optionally, an embodiment of the present invention may further provide a security processor, the security processor may include a measurement command processing module, a measurement target list, and a measurement engine, and the measurement command processing module is used to execute the above security processor-based In the measurement management method of an angle, the measurement target list is used to store the measurement target and data information corresponding to the measurement target, and the measurement engine is used to perform measurement on the measurement target according to the measurement target list.

Optionally, this embodiment of the present invention may further provide a processor, where the processor is configured to execute the foregoing metric management method based on a processor perspective.

Optionally, an embodiment of the present invention may further provide a processor, where the processor includes a metric software stack, and the metric software stack is configured to execute the foregoing metric management method based on a processor perspective.

Optionally, an embodiment of the present invention may further provide a computer system, including: any one of the above-mentioned security processors and any one of the above-mentioned processors.

Optionally, an embodiment of the present invention may further provide a storage medium, which may store a program for implementing the above-mentioned metric management method based on a security processor perspective, or a program for implementing the above-mentioned metric management method based on a processor perspective.

Multiple embodiment solutions provided by the embodiments of the present invention are described above, and the optional modes introduced by each embodiment solution can be combined and cross-referenced without conflict, thereby extending a variety of possible embodiment solutions, All of these can be regarded as the embodiment disclosures of the present invention and the disclosed embodiment solutions.

Although the embodiments of the present invention are disclosed above, the present invention is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, so the protection scope of the present invention should be based on the scope defined in the claims.

Claims (24)

1. A method of metric management, applied to a secure processor, comprising:

after a program is loaded, acquiring a measurement target creation command of the program;

creating a metrology target corresponding to the program in a metrology target list in response to the metrology target creation command;

acquiring a sampling command for sampling a measurement reference value of the program, wherein the sampling command comprises a code start-stop address corresponding to a code of the program;

measuring codes in the code start-stop addresses in response to the sampling command, and setting a measured measurement value as a measurement reference value of the program to measure whether the program is abnormal or not based on the measurement reference value;

the measurement standard value, the code start-stop address, the enabling state of the measurement target, the main key of the measurement target and the measurement target are correspondingly stored in the measurement target list, and a measurement engine measures whether the program is abnormal or not based on data in the measurement target list; the enabling state of the measurement target is used for indicating a measurement engine to stop or execute the measurement task of the measurement target; the master key of the metrology target is used to encrypt or verify the metrology related commands.

2. The method according to claim 1, further comprising, after creating a metrology target corresponding to the program in a metrology target list, before the acquiring a sample command:

negotiating with a measurement management requester to obtain a master key corresponding to the measurement target, wherein the master key is used for encrypting or verifying interaction data with the measurement management requester;

the master key is stored in the measurement target list, and the master key is stored corresponding to the measurement target.

3. The method of claim 1, wherein after setting the metric reference value of the program, the method further comprises:

acquiring a start measurement command of the program;

and in response to a start measurement command of the program, updating the enabling state of the measurement target corresponding to the program in the measurement target list to be yes, wherein the enabling state of the measurement target is yes and is used for indicating a measurement engine to execute measurement tasks on the measurement target.

4. The method of claim 1, wherein after setting the metric reference value of the program, the method further comprises:

acquiring a stop measurement command of the program;

And in response to a stopping measurement command of the program, updating whether the enabling state of the measurement target corresponding to the program is in the measurement target list, and indicating that a measurement engine stops the measurement task of the measurement target if the enabling state of the measurement target is in the NO state.

5. The method of claim 1, wherein after setting the metric reference value of the program, the method further comprises:

acquiring a measurement state query command of the program;

inquiring abnormal state information of a measurement target corresponding to the program in the measurement target list in response to a measurement state inquiry command of the program;

and sending a response notice of the measurement state query command, wherein the response notice comprises abnormal state information of the measurement target.

6. The method of claim 1, wherein after setting the metric reference value of the program, the method further comprises:

acquiring an ending measurement command of the program;

and deleting a measurement target corresponding to the program and data information corresponding to the measurement target in the measurement target list in response to an ending measurement command of the program.

7. The method of claim 2, wherein after storing the master key in the metrics goal list, the method further comprises:

receiving measurement command parameter data, wherein the measurement command parameter data comprises measurement command parameters, a check code and a random number of a measurement service caller, and the check code is generated according to one or more parameters of the measurement command parameters, the random number corresponding to the last measurement response parameter and a consistency secret key; the consistency secret key is derived from the master secret key; the measurement command parameter is a command parameter in a sampling command, a start measurement command, a stop measurement command, an end measurement command or a measurement state query command;

and according to the check code, checking the measurement command parameter data to determine the measurement command parameter of the corresponding command.

8. The method of claim 7, wherein after storing the master key in the metrics goal list, the method further comprises:

generating a check code of a measurement response parameter to obtain measurement response parameter data, wherein the measurement response parameter data comprises measurement response parameters, the check code and random numbers corresponding to measurement response, the check code is generated according to the measurement response parameters, the random numbers in a command corresponding to the measurement response parameters, the random numbers corresponding to the measurement response parameters and one or more parameters in a consistency secret key; the measurement response parameters are response parameters obtained after responding to the sampling command, the start measurement command, the stop measurement command, the end measurement command or the measurement state query command;

And sending the measurement response parameter data.

9. The method of claim 8, wherein the random number corresponding to the metric command parameter is updated once per check of the metric response parameter data, and the random number corresponding to the metric response parameter is updated once per check of the metric command parameter.

10. A method of metric management, applied to a processor, comprising:

after a program is loaded, a measurement target creation command of the program is sent, wherein the measurement target creation command is used for indicating to create a measurement target corresponding to the program in a measurement target list;

acquiring a response notice of the measurement target creation command, and determining to create a measurement target of the program;

a sampling command is sent, the sampling command comprises a code start-stop address corresponding to the code of the program, the sampling command is used for indicating to sample the code in the code start-stop address, and a measurement value obtained by sampling is set as a measurement reference value of the program so as to measure whether the program is abnormal or not based on the measurement reference value;

acquiring a response notice of the sampling command, and determining that the program sets the measurement reference value;

The measurement standard value, the code start-stop address, the enabling state of the measurement target, the main key of the measurement target and the measurement target are correspondingly stored in the measurement target list, and a measurement engine measures whether the program is abnormal or not based on data in the measurement target list; the enabling state of the measurement target is used for indicating a measurement engine to stop or execute the measurement task of the measurement target; the master key of the metrology target is used to encrypt or verify the metrology related commands.

11. The method of claim 10, further comprising, after obtaining a response notification of the metrology target creation command, prior to sending a sample command:

negotiating with a measurement management executive party to obtain a master key corresponding to the program, wherein the master key is used for encrypting or verifying interaction data with the measurement management executive party;

storing a master key corresponding to the program.

12. The method of claim 10, wherein after the obtaining the response notification of the sampling command, the method further comprises:

transmitting a start measurement command of the program, wherein the start measurement command is used for indicating that the enabling state of a measurement target corresponding to the program is updated in the measurement target list, and the enabling state of the measurement target is yes and is used for indicating a measurement engine to execute a measurement task on the measurement target;

And acquiring response notification of the start measurement command, and determining that the enabling state of the measurement target corresponding to the program is yes.

13. The method of claim 10, wherein after the obtaining the response notification of the sampling command, the method further comprises:

a stopping measurement command of the program is sent, the stopping measurement command is used for indicating whether the enabling state of the measurement target corresponding to the program is updated in the measurement target list, and the enabling state of the measurement target is not used for indicating a measurement engine to stop the measurement task of the measurement target;

and acquiring response notification of the stopping measurement command, and determining whether the enabling state of the measurement target corresponding to the program is updated.

14. The method of claim 10, wherein after the obtaining the response notification of the sampling command, the method further comprises:

a measurement state query command of the program is sent, and the measurement state query command is used for indicating to query abnormal state information of a measurement target corresponding to the program in the measurement target list;

and acquiring response notification of the measurement state query command, and determining abnormal state information of the measurement target.

15. The method of claim 10, wherein after the obtaining the response notification of the sampling command, the method further comprises:

transmitting an end metric command of the program, wherein the end metric command is used for indicating to delete a metric target corresponding to the program in the metric target list and data information corresponding to the metric target;

and acquiring a response notice of the ending measurement command, determining to delete a measurement target corresponding to the program, and determining data information corresponding to the measurement target.

16. The method of claim 11, wherein after storing the master key corresponding to the program, the method further comprises:

generating a check code of the measurement command parameter to obtain measurement command parameter data; the measurement command parameter data comprises measurement command parameters, check codes and random numbers of measurement service callers, wherein the check codes are generated according to one or more parameters of the measurement command parameters, the random numbers corresponding to the last measurement response parameters and the consistency secret keys; the consistency secret key is derived from the master secret key; the measurement command parameter is a command parameter in a sampling command, a start measurement command, a stop measurement command, an end measurement command or a measurement state query command;

And sending the measurement command parameter data.

17. The method of claim 16, wherein after storing the master key corresponding to the program, the method further comprises:

receiving a check code of a metric response parameter to obtain metric response parameter data, wherein the metric response parameter data comprises the metric response parameter, the check code and a random number corresponding to the metric response, and the check code is generated according to the metric response parameter, the random number in a command corresponding to the response, the random number corresponding to the metric response parameter and one or more parameters in a consistency secret key; the measurement response parameters are response parameters obtained after responding to a sampling command, a start measurement command, a stop measurement command, an end measurement command or a measurement state query command;

and according to the check code, checking the metric response parameter data, and determining the metric response parameter of the corresponding response.

18. The method of claim 17, wherein the random number corresponding to the metric command parameter is updated once per check of the metric response parameter data, and the random number corresponding to the metric response parameter is updated once per check of the metric command parameter.

19. A security processor for performing the metric management method of any of claims 1 to 9.

20. A security processor, characterized in that the security processor comprises a metric command processing module for executing the metric management method of any one of claims 1 to 9, a metric target list for storing metric targets and data information corresponding to the metric targets, and a metric engine for executing metrics on the metric targets according to the metric target list.

21. A processor for performing the metric management method of any of claims 10 to 18.

22. A processor, characterized in that it comprises a metrics software stack for executing the metrics management method of any of claims 10-18.

23. A computer system, comprising: a secure processor as claimed in any one of claims 19 to 20 and a processor as claimed in any one of claims 21 to 22.

24. A storage medium storing a program for implementing the metric management method according to any one of claims 1 to 9, or a program for implementing the metric management method according to any one of claims 10 to 18.