A data comparison method, system and storage medium in a traffic playback process

Abstract

The application provides a data comparison method and system in a traffic playback process and a storage medium. The application sets an operation event log function in a software backend running program, stores event ID, an interface, input parameters and output parameters, and compares the event ID, the interface, the input parameters and the output parameters in the traffic playback process with data in the log, so as to determine whether the software backend running program and the traffic playback operation are modified or attacked, and improve the security of the software program.

Description

Technical Field

[0001] This invention relates to the field of data comparison technology in the process of traffic playback, and particularly to a data comparison method, system and storage medium in the process of traffic playback. Background Technology

[0002] As software projects iterate and optimize, the input and output parameters of front-end and back-end interfaces may change. To ensure data consistency, interface validation is necessary. This solution uses user log tracking to obtain interface usage data and compares the old version's interface request data with the new version's interface request data to detect whether the input and output parameters of the interface call have changed.

[0003] To address the aforementioned issues, this paper proposes a data comparison method, system, and storage medium for the traffic replay process. Summary of the Invention

[0004] To address the above problems, this invention proposes a data comparison method during traffic playback, the method specifically including the following steps:

[0005] S1. Add an operation event log function to the software backend program;

[0006] S2. When a user performs an operation on the software front-end interface, the software front-end program generates an operation event ID;

[0007] S3. The software front-end program writes the ID into the header of the interface request corresponding to the operation event;

[0008] S4. Upon receiving the request, the software backend program writes the ID corresponding to the request, the backend program interface name, the interface input parameters, and the interface output parameters to the operation event log.

[0009] S5. During the traffic replay process, the traffic replay script queries the ID corresponding to the event, queries the record corresponding to the ID from the operation event log, compares the input parameters and output parameters, and obtains the comparison result.

[0010] Furthermore, step S1 adds an operation event log function to the software backend running program, specifically including:

[0011] The software is divided into a front-end program and a back-end program;

[0012] The front-end program is used to display the operation interface to the user, receive user operation behavior, and generate operation events and operation event IDs based on user operation behavior.

[0013] The backend program is used to receive interface requests corresponding to operation events sent by the frontend program.

[0014] The backend program includes more than one interface, and each interface has an interface name;

[0015] Each interface receives input parameters, which are then processed by the corresponding running program, and the interface then outputs the parameters for the interface request corresponding to the operation event.

[0016] Add an operation event log function to the software backend program, including: the log records the data corresponding to the operation event.

[0017] Furthermore, in step S2, when the user performs an operation on the software front-end interface, the software front-end program generates an operation event ID, specifically including:

[0018] When a user interacts with the software's front-end interface, the software's front-end program starts the first generation thread.

[0019] The first generation thread generates an operation event ID for the user's operation;

[0020] The operation event ID is an identifier that can uniquely identify the operation event.

[0021] Further, in step S3, the software front-end program writes the ID into the header of the interface request corresponding to the operation event, specifically including:

[0022] Generate the interface request corresponding to the user's operation based on the user's operation;

[0023] The interface is the interface in the backend running program;

[0024] The first generation thread writes the ID into the header of the interface request.

[0025] Further, in step S4, the software backend program receives the request and writes the ID corresponding to the request, the backend program interface name, the interface input parameters, and the interface output parameters into the operation event log, specifically including the following steps:

[0026] S41. The software backend program receives the request, obtains the event ID in the header of the request, and obtains the interface name of the backend program corresponding to the request;

[0027] S42. The software backend program simultaneously starts the first write thread, the second write thread, and the third write thread;

[0028] S43. The software backend program randomly selects a write thread from the first write thread, the second write thread, and the third write thread, and uses this write thread to store the event ID, the backend program interface name, and the current time from step S41. The corresponding data should be written to the operation event log.

[0029] The event ID, the backend running program interface name, and the current time in step S41 are then included. The corresponding data is written to the operation event log, specifically including:

[0030] S431. Create a new row of data in the operation event log. The new row of data includes the following data: first moment, event ID, backend running program interface name, input parameters, and output parameters.

[0031] S432. Set the value of the first time point to the current time point. Set the event ID to the event ID described in step S43, and set the backend running program interface name to the backend running program interface name described in step S43.

[0032] Set the input and output parameters to empty;

[0033] S433. The backend running program starts the first blocking thread and uses the first blocking thread to set the storage location of the input parameters and output parameters to a non-writable state;

[0034] S44. The backend runtime interface receives the input parameters corresponding to the request, the software backend runtime executes the request, and after execution, the backend runtime interface feeds back the output parameters and records the current time. ;

[0035] S45. The writing thread randomly selected in step S43 continuously listens to the operation of the backend running program and writes the input parameters and output parameters in step S44 to the operation event log.

[0036] Furthermore, the characteristic feature is that step S45 specifically includes the following steps:

[0037] S451. When the write thread detects the output parameter, determine... With preset time threshold Size relationship; when When it is determined that the backend program is under attack, the execution of the backend program is terminated; when When the time comes, proceed to step S452;

[0038] S452. Obtain the decryption password stored in the write thread, and have the write thread send the decryption password to the first blocking thread;

[0039] S453. After receiving the decryption password, the first blocking thread compares and verifies the decryption password with the unblocking password stored inside the first blocking thread. When the decryption password is present in the unblocking password, the first blocking thread sets the storage location of the second moment, input parameters, and output parameters to a writable state.

[0040] S454. The writing thread writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431;

[0041] S455. The first blocking thread continuously monitors the execution object of data writing to the storage location of the input parameters and output parameters. When the execution object is the writing thread in step S452, it continues to monitor the execution object of data writing. When the execution object is not the writing thread in step S452, it determines that the backend running program is under attack and terminates the running of the backend running program.

[0042] S456. After the writing thread successfully writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431, the first blocking thread sets the storage location of the input parameters and output parameters in the new row of data to an unwritable state.

[0043] Furthermore, in step S5, during the traffic replay process, the traffic replay script queries the ID corresponding to the event, retrieves the record corresponding to the ID from the operation event log, compares the input parameters and output parameters, and obtains the comparison result. Specifically, this includes the following steps:

[0044] S51. Start the traffic replay operation and obtain the event ID corresponding to the traffic replay through the traffic replay script;

[0045] S52. Check if the event ID exists in the operation event log. If it exists, proceed to step S53. If it does not exist, determine that the traffic replay operation has been tampered with and terminate the traffic replay operation.

[0046] S53. Obtain the interface name and input parameters of the backend running program corresponding to the traffic replay operation;

[0047] S54. Store the event ID obtained in step S51, the backend running program interface name and input parameters obtained in step S53 into a temporary storage array;

[0048] Record the current moment ;

[0049] S55. The front-end and back-end programs of the software perform traffic replay operations to obtain the output parameters fed back by the interface of the back-end program.

[0050] S56. Store the output parameters fed back by the backend running program into the temporary storage array, and record the current time. ;

[0051] S57. The temporary storage array is locked by the second locking thread, so that the temporary storage array is changed to a read-only state;

[0052] S58. When When it is determined that the backend program is under attack, the execution of the backend program is terminated; when At that time, proceed to step S59;

[0053] in, The preset time threshold;

[0054] S59. The backend program retrieves a row of data from the operation event log that has the same event ID as the event in the temporary storage array, and retrieves the backend program interface name, input parameters, and output parameters stored in the row of data;

[0055] The backend program compares whether the backend program interface name, input parameters, and output parameters stored in the row of data are exactly the same as those in the temporary storage array.

[0056] If the results are the same, it indicates that the backend running program or traffic replay operation has not been modified or attacked.

[0057] If the results are different, it indicates that the backend running program or traffic replay operation has been modified or attacked.

[0058] The present invention also proposes a data comparison system for a traffic playback process, wherein the system executes a data comparison method for a traffic playback process.

[0059] For example, the system performs the following steps:

[0060] S1. Add an operation event log function to the software backend program;

[0061] S2. When a user performs an operation on the software front-end interface, the software front-end program generates an operation event ID;

[0062] S3. The software front-end program writes the ID into the header of the interface request corresponding to the operation event;

[0063] S4. Upon receiving the request, the software backend program writes the ID corresponding to the request, the backend program interface name, the interface input parameters, and the interface output parameters to the operation event log.

[0064] S5. During the traffic replay process, the traffic replay script queries the ID corresponding to the event, queries the record corresponding to the ID from the operation event log, compares the input parameters and output parameters, and obtains the comparison result.

[0065] The present invention also proposes a computer storage medium that stores instructions, which are executed by a processor, such as a data comparison method in a traffic playback process.

[0066] The beneficial effects of this invention are as follows:

[0067] 1. This invention adds an operation log function to the backend program of the software, associates and stores the backend program interface with the time ID, and stores the input and output parameters of the interface; by comparing the input and output parameters of the backend program interface corresponding to the event ID in the traffic replay process, it verifies whether the backend program and traffic replay operation have been modified or attacked.

[0068] 2. This invention further improves the accuracy of judging whether the software backend program has been attacked by determining whether the time between the time when the event ID and the time when the backend program interface are written to the operation event log and the time when the feedback output parameter is obtained exceeds a preset time.

[0069] 3. This invention sets the storage locations of input and output parameters in the operation event log to a non-writable state, and after verification by the decryption password of the writing thread, the first blocking thread controls the change of the writable and non-writable states of the above storage locations, thereby ensuring that the storage locations of input and output parameters can only be written by the writing thread specified by the system, thus avoiding unknown attacks.

[0070] 4. In the process of traffic playback, after obtaining the input and output parameters, the present invention writes the input and output parameters into a temporary storage array and changes the temporary storage array to a read-only state before starting the comparison of the input and output parameters. This avoids modification of the input and output parameters during the comparison process and improves the overall security of the system.

[0071] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above description and other objects, features and advantages of the present invention more obvious and understandable, preferred embodiments are provided and described in detail below. Attached Figure Description

[0072] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0073] Figure 1 This is a flowchart of a data comparison method during traffic playback. Detailed Implementation

[0074] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0075] In the description of this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," "fixing," etc., should be interpreted broadly. For example, they can refer to a connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0076] Example 1

[0077] This invention proposes a data comparison method during traffic playback, the method specifically including the following steps:

[0078] S1. Add an operation event log function to the software backend program;

[0079] Specifically, step S1, which adds an operation event log function to the software backend running program, includes:

[0080] The software is divided into a front-end program and a back-end program;

[0081] The front-end program is used to display the operation interface to the user, receive user operation behavior, and generate operation events and operation event IDs based on user operation behavior.

[0082] The backend program is used to receive interface requests corresponding to operation events sent by the frontend program.

[0083] The backend program includes more than one interface, and each interface has an interface name;

[0084] Each interface receives input parameters, which are then processed by the corresponding running program, and the interface then outputs the parameters for the interface request corresponding to the operation event.

[0085] Add an operation event log function to the software backend program, including: the log records the data corresponding to the operation event.

[0086] S2. When a user performs an operation on the software front-end interface, the software front-end program generates an operation event ID;

[0087] Furthermore, in step S2, when the user performs an operation on the software front-end interface, the software front-end program generates an operation event ID, specifically including:

[0088] When a user interacts with the software's front-end interface, the software's front-end program starts the first generation thread.

[0089] The first generation thread generates an operation event ID for the user's operation;

[0090] The operation event ID is an identifier that can uniquely identify the operation event.

[0091] S3. The software front-end program writes the ID into the header of the interface request corresponding to the operation event;

[0092] Further, in step S3, the software front-end program writes the ID into the header of the interface request corresponding to the operation event, specifically including:

[0093] Generate the interface request corresponding to the user's operation based on the user's operation;

[0094] The interface is the interface in the backend running program;

[0095] The first generation thread writes the ID into the header of the interface request.

[0096] S4. Upon receiving the request, the software backend program writes the ID corresponding to the request, the backend program interface name, the interface input parameters, and the interface output parameters to the operation event log.

[0097] Further, in step S4, the software backend program receives the request and writes the ID corresponding to the request, the backend program interface name, the interface input parameters, and the interface output parameters into the operation event log, specifically including the following steps:

[0098] S41. The software backend program receives the request, obtains the event ID in the header of the request, and obtains the interface name of the backend program corresponding to the request;

[0099] S42. The software backend program simultaneously starts the first write thread, the second write thread, and the third write thread;

[0100] The decryption password is stored in the first write thread, the second write thread, and the third write thread.

[0101] The decryption passwords stored in the first write thread, the second write thread, and the third write thread are different;

[0102] S43. The software backend program randomly selects a write thread from the first write thread, the second write thread, and the third write thread, and uses this write thread to store the event ID, the backend program interface name, and the current time from step S41. The corresponding data should be written to the operation event log.

[0103] The event ID, the backend running program interface name, and the current time in step S41 are then included. The corresponding data is written to the operation event log, specifically including:

[0104] S431. Create a new row of data in the operation event log. The new row of data includes the following data: first moment, event ID, backend running program interface name, input parameters, and output parameters.

[0105] S432. Set the value of the first time point to the current time point. Set the event ID to the event ID described in step S43, and set the backend running program interface name to the backend running program interface name described in step S43.

[0106] Set the input and output parameters to empty;

[0107] S433. The backend running program starts the first blocking thread and uses the first blocking thread to set the storage location of the input parameters and output parameters to a non-writable state;

[0108] S44. The backend runtime interface receives the input parameters corresponding to the request, the software backend runtime executes the request, and after execution, the backend runtime interface feeds back the output parameters and records the current time. ;

[0109] S45. The writing thread randomly selected in step S43 continuously listens to the operation of the backend running program and writes the input parameters and output parameters in step S44 to the operation event log.

[0110] Furthermore, step S45 specifically includes the following steps:

[0111] S451. When the write thread detects the output parameter, determine... With preset time threshold Size relationship; when When it is determined that the backend program is under attack, the execution of the backend program is terminated; when When the time comes, proceed to step S452;

[0112] The value of T can be flexibly set according to the actual software.

[0113] S452. Obtain the decryption password stored in the write thread, and have the write thread send the decryption password to the first blocking thread;

[0114] S453. After receiving the decryption password, the first blocking thread compares and verifies the decryption password with the unblocking password stored inside the first blocking thread. When the decryption password is present in the unblocking password, the first blocking thread sets the storage location of the second moment, input parameters, and output parameters to a writable state.

[0115] The first blocking thread stores three decryption passwords, which are the decryption passwords for the first writing thread, the second writing thread, and the third writing thread, respectively.

[0116] S454. The writing thread writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431;

[0117] S455. The first blocking thread continuously monitors the execution object of data writing to the storage location of the input parameters and output parameters. When the execution object is the writing thread in step S452, it continues to monitor the execution object of data writing. When the execution object is not the writing thread in step S452, it determines that the backend running program is under attack and terminates the running of the backend running program.

[0118] S456. After the writing thread successfully writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431, the first blocking thread sets the storage location of the input parameters and output parameters in the new row of data to an unwritable state.

[0119] S5. During the traffic replay process, the traffic replay script queries the ID corresponding to the event, queries the record corresponding to the ID from the operation event log, compares the input parameters and output parameters, and obtains the comparison result.

[0120] Furthermore, step S5 specifically includes the following steps:

[0121] S51. Start the traffic replay operation and obtain the event ID corresponding to the traffic replay through the traffic replay script;

[0122] S52. Check if the event ID exists in the operation event log. If it exists, proceed to step S53. If it does not exist, determine that the traffic replay operation has been tampered with and terminate the traffic replay operation.

[0123] S53. Obtain the interface name and input parameters of the backend running program corresponding to the traffic replay operation;

[0124] S54. Store the event ID obtained in step S51, the backend running program interface name and input parameters obtained in step S53 into a temporary storage array;

[0125] Record the current moment ;

[0126] S55. The front-end and back-end programs of the software perform traffic replay operations to obtain the output parameters fed back by the interface of the back-end program.

[0127] S56. Store the output parameters fed back by the backend running program into the temporary storage array, and record the current time. ;

[0128] S57. The temporary storage array is locked by the second locking thread, so that the temporary storage array is changed to a read-only state;

[0129] S58. When When it is determined that the backend program is under attack, the execution of the backend program is terminated; when At that time, proceed to step S59;

[0130] in The preset time threshold is T; the value of T can be flexibly set according to the actual software.

[0131] S59. The backend program retrieves a row of data from the operation event log that has the same event ID as the event in the temporary storage array, and retrieves the backend program interface name, input parameters, and output parameters stored in the row of data;

[0132] The backend program compares whether the backend program interface name, input parameters, and output parameters stored in the row of data are exactly the same as those in the temporary storage array.

[0133] If the results are the same, it indicates that the backend running program or traffic replay operation has not been modified or attacked.

[0134] If the results are different, it indicates that the backend running program or traffic replay operation has been modified or attacked.

[0135] Example 2

[0136] This invention proposes a data comparison system for traffic playback, characterized in that the system executes a data comparison method for traffic playback as described in Embodiment 1.

[0137] Example 3

[0138] This invention proposes a computer storage medium that stores instructions, which are executed by a processor as described in Embodiment 1, a data comparison method during a traffic playback process.

[0139] The beneficial effects of the invention are as follows:

[0140] 1. This invention adds an operation log function to the backend program of the software, associates and stores the backend program interface with the time ID, and stores the input and output parameters of the interface; by comparing the input and output parameters of the backend program interface corresponding to the event ID in the traffic replay process, it verifies whether the backend program and traffic replay operation have been modified or attacked.

[0141] 2. This invention further improves the accuracy of judging whether the software backend program has been attacked by determining whether the time between the time when the event ID and the time when the backend program interface are written to the operation event log and the time when the feedback output parameter is obtained exceeds a preset time.

[0142] 3. This invention sets the storage locations of input and output parameters in the operation event log to a non-writable state, and after verification by the decryption password of the writing thread, the first blocking thread controls the change of the writable and non-writable states of the above storage locations, thereby ensuring that the storage locations of input and output parameters can only be written by the writing thread specified by the system, thus avoiding attacks from unknown sources.

[0143] 4. In the process of traffic playback, after obtaining the input and output parameters, the present invention writes the input and output parameters into a temporary storage array and changes the temporary storage array to a read-only state before starting the comparison of the input and output parameters. This avoids modification of the input and output parameters during the comparison process and improves the overall security of the system.

[0144] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A data comparison method during traffic playback, characterized in that, The method specifically includes the following steps: S1. Add an operation event log function to the software backend program; S2. When a user performs an operation on the software front-end interface, the software front-end program generates an operation event ID; S3. The software front-end program writes the operation event ID into the header of the interface request corresponding to the operation event; S4. The software backend program receives the interface request and writes the operation event ID, backend program interface name, interface input parameters, and interface output parameters corresponding to the interface request into the operation event log; S5. During the traffic replay process, the traffic replay script queries the event ID corresponding to the traffic replay, retrieves the record corresponding to the event ID from the operation event log, and compares the backend running program interface name, input parameters, and output parameters of the traffic replay event with a line of data in the operation event log that is the same as the event ID corresponding to the traffic replay, to obtain the comparison result; this line of data stores the backend running program interface name, input parameters, and output parameters; if the comparison results are the same, it is determined that the backend running program or traffic replay operation has not been modified or attacked; if they are different, it is determined that the backend running program or traffic replay operation has been modified or attacked; Step S4 includes the following steps: S41. The software backend program receives the interface request, obtains the operation event ID in the header of the interface request, and obtains the interface name of the backend program corresponding to the interface request. S42. The software backend program simultaneously starts the first write thread, the second write thread, and the third write thread; S43. The software backend program randomly selects a write thread from the first write thread, the second write thread, and the third write thread, and uses this write thread to store the operation event ID from step S41, the backend program interface name, and the current time. The corresponding information is written to the operation event log. Step S43 includes step S433: writing the backend running program interface name and the current time. Then, the backend program starts the first blocking thread and uses the first blocking thread to set the storage location of the input parameters and output parameters to a non-writable state; S44. The backend runtime interface receives the input parameters corresponding to the interface request, executes the interface request, and after completion, the backend runtime interface returns the output parameters and records the current time. ; S45. The writing thread randomly selected in step S43 continuously monitors the operation of the backend running program and writes the input parameters and output parameters in step S44 to the operation event log; Step S45 includes the following steps: S451. When the write thread detects the output parameter, determine... With preset time threshold Size relationship; when At that time, proceed to step S452; S452. Obtain the decryption password stored in the write thread, and have the write thread send the decryption password to the first blocking thread; S453. After receiving the decryption password, the first blocking thread compares and verifies the decryption password with the unblocking password stored internally in the first blocking thread. When the decryption password is present in the unblocking password, the first blocking thread sets the storage location of the second time, input parameters, and output parameters to a writable state.

2. The data comparison method in the process of traffic playback according to claim 1, characterized in that, Step S1 involves adding an operation event log function to the software backend program, specifically including: The software is divided into a front-end program and a back-end program; The front-end program is used to display the operation interface to the user, receive user operation behavior, and generate operation events and operation event IDs based on user operation behavior. The backend program is used to receive interface requests corresponding to operation events sent by the frontend program. The backend program includes more than one interface, and each interface has an interface name; Each interface receives input parameters, which are then processed by the corresponding running program, and the interface then outputs the parameters for the interface request corresponding to the operation event. Add an operation event log function to the software backend program, including: the operation event log records the data corresponding to the operation event.

3. The data comparison method in the process of traffic playback according to claim 2, characterized in that, In step S2, when the user performs an operation on the software front-end interface, the software front-end program generates an operation event ID, specifically including: When a user interacts with the software's front-end interface, the software's front-end program starts the first generation thread. The first generation thread generates an operation event ID for the user's operation behavior; The operation event ID is an identifier that can uniquely identify the operation event.

4. The data comparison method in the process of traffic playback according to claim 3, characterized in that, Step S3, where the software front-end program writes the operation event ID into the header of the interface request corresponding to the operation event, specifically includes: Generate the interface request corresponding to the user's operation behavior based on the user's operation behavior; The interface is the interface in the backend running program; The first generation thread writes the operation event ID into the header of the interface request.

5. The data comparison method in the process of traffic playback according to claim 4, characterized in that... In step S43, the operation event ID from step S41, the backend running program interface name, and the current time are... The corresponding data is written to the operation event log, specifically including: S431. Create a new row of data in the operation event log. The new row of data includes the following data: first moment, operation event ID, backend running program interface name, input parameters, and output parameters. S432. Set the value of the first time point to the current time point. Set the operation event ID to the operation event ID described in step S43, and set the backend running program interface name to the backend running program interface name described in step S43. Set the input and output parameters to empty.

6. The data comparison method in the process of traffic playback according to claim 5, characterized in that, Step S45 further includes the following steps: S454. The writing thread writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431; S455. The first blocking thread continuously monitors the execution object of data writing at the storage location of the input parameters and output parameters. When the execution object is the writing thread in step S452, it continues to monitor the execution object of data writing. When the execution object is not the writing thread in step S452, it is determined that the backend running program is under attack, and the running of the backend running program is terminated. S456. After the writing thread successfully writes the input parameters and output parameters into the input parameter and output parameter fields of the new row of data in step S431, the first blocking thread sets the storage location of the input parameters and output parameters in the new row of data to an unwritable state.

7. The data comparison method in the process of traffic playback according to claim 5, characterized in that, Step S5 specifically includes the following steps: S51. Start the traffic replay operation and obtain the event ID corresponding to the traffic replay through the traffic replay script; S52. Check if there is an event ID corresponding to the traffic replay in the operation event log. If it exists, proceed to step S53; if it does not exist, determine that the traffic replay operation has been tampered with and terminate the traffic replay operation. S53. Obtain the interface name and input parameters of the backend running program corresponding to the traffic replay operation; S54. Store the event ID corresponding to the traffic replay obtained in step S51, the backend running program interface name and input parameters obtained in step S53 into a temporary storage array; Record the current moment ; S55. The front-end and back-end programs of the software perform traffic replay operations to obtain the output parameters fed back by the interface of the back-end program. S56. Store the output parameters fed back by the backend running program into the temporary storage array, and record the current time. ; S57. The temporary storage array is locked by the second locking thread, so that the temporary storage array is changed to a read-only state; S58. When When it is determined that the backend program is under attack, the execution of the backend program is terminated; when At that time, proceed to step S59; in The preset time threshold; S59. The backend program retrieves a row of data from the operation event log that has the same event ID as the traffic playback in the temporary storage array, and retrieves the backend program interface name, input parameters, and output parameters stored in the row of data; The backend program compares whether the backend program interface name, input parameters, and output parameters stored in the row of data are exactly the same as those in the temporary storage array. If the results are the same, it indicates that the backend running program or traffic replay operation has not been modified or attacked. If the results are different, it indicates that the backend running program or traffic replay operation has been modified or attacked.

8. A data comparison system for a traffic playback process, used to implement the method of claim 1, characterized in that, The system performs the following steps: S1. Add an operation event log function to the software backend program; S2. When a user performs an operation on the software front-end interface, the software front-end program generates an operation event ID; S3. The software front-end program writes the operation event ID into the header of the interface request corresponding to the operation event; S4. The software backend program receives the interface request and writes the ID corresponding to the interface request, the backend program interface name, the interface input parameters, and the interface output parameters to the operation event log. S5. During the traffic replay process, the traffic replay script queries the ID corresponding to the event for traffic replay, retrieves the record corresponding to the ID of the event for traffic replay from the operation event log, and compares the backend running program interface name, input parameters, and output parameters of the event for traffic replay with a line of data in the operation event log that is the same as the event ID corresponding to traffic replay, to obtain the comparison result; this line of data stores the backend running program interface name, input parameters, and output parameters; if the comparison results are the same, it is determined that the backend running program or traffic replay operation has not been modified or attacked; if they are different, it is determined that the backend running program or traffic replay operation has been modified or attacked.

9. A computer storage medium storing instructions, the instructions being executed by a processor according to any one of claims 1-7.

Images