CN115632879A - Log management method, system, electronic device and storage medium - Google Patents
Log management method, system, electronic device and storage medium Download PDFInfo
- Publication number
- CN115632879A CN115632879A CN202211560352.3A CN202211560352A CN115632879A CN 115632879 A CN115632879 A CN 115632879A CN 202211560352 A CN202211560352 A CN 202211560352A CN 115632879 A CN115632879 A CN 115632879A
- Authority
- CN
- China
- Prior art keywords
- request
- log
- plaintext
- encryption
- encrypted
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a log management method, a system, electronic equipment and a storage medium, wherein the log management method comprises the steps of sending a first request to a server node to trigger the server node to generate a second request, wherein the second request comprises a first encrypted log; receiving a second request and acquiring a first encryption log from the second request; capturing a third request, wherein the third request comprises a second plaintext log; judging whether the third request corresponds to the second request, if so, encrypting the second plaintext log by using a public key corresponding to the algorithm to obtain a second encrypted log; and judging whether the first encryption log is the same as the second encryption log, and if so, determining that the algorithm is safe. The method and the device complete the monitoring of algorithm safety through the management of the log, determine that the encrypted data is not tampered, do not need to invade the federal learning products of manufacturers and carry out a large amount of personalized operations aiming at the federal learning products of different manufacturers, simplify the operation and save the time cost and the labor cost.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a log management method, a log management system, electronic equipment and a storage medium.
Background
Various logs can exist among all server nodes of the federal learning product, including an operation log, an API (Application Programming Interface) call log, a task log, an algorithm log and the like, some clients can use the federal learning products of different manufacturers, the interfaces of the federal learning products of different manufacturers are mutually called, and encrypted data are easily tampered after being captured. In the prior art, when a user manages different federal learning products, the difficulty of unifying interfaces and request modes is high, so that the algorithm safety of the different federal learning products needs to be personalized and customized for verification. Logs are easily managed and analyzed in federal learning products of different vendors. How to use the log is to monitor the algorithm safety of the federal learning products of different manufacturers and determine that the encrypted data is not tampered on the premise of not invading the federal learning products of the manufacturers and not carrying out a large amount of personalized operations aiming at the federal learning products of different manufacturers, so that the problem which needs to be solved urgently is solved.
Disclosure of Invention
The invention aims to overcome the defect that algorithm safety monitoring of the Federation learning product is difficult in the prior art, and provides a log management method, a log management system, electronic equipment and a storage medium.
The invention solves the technical problems through the following technical scheme:
the invention provides a log management method, which comprises the following steps:
sending a first request to a target server node, wherein the first request is used for triggering the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate a second request, and the second request comprises the first encrypted log;
receiving the second request sent by the target server node through a target algorithm interface through a log interface, and acquiring the first encrypted log from the second request;
capturing a third request from the target algorithm interface, wherein the third request comprises a second plaintext log;
judging whether the third request corresponds to the second request, if so, encrypting the second plaintext log by using a public key corresponding to the target algorithm to obtain a second encrypted log;
and judging whether the first encryption log and the second encryption log are the same or not, and if so, determining that the target algorithm is safe.
Preferably, the step of sending the first request to the target server node is preceded by:
generating a pair of public key and private key;
the first request comprises the public key;
the second request comprises the first encryption log, an encryption request header and a first plaintext parameter, wherein the encryption request header is obtained by encrypting the first plaintext request header by the target server node by using the public key.
Preferably, the step of obtaining the first encryption log from the second request comprises:
judging whether the private key is matched with the encryption request head, if so, decrypting the encryption request head by using the private key to obtain the first plaintext request head, and executing the step of obtaining the first encryption log from the second request;
the step of obtaining the first encrypted log from the second request may be followed by:
and acquiring the first plaintext parameters from the second request.
Preferably, the third request further includes a second plaintext request header and a second plaintext parameter;
the step of determining whether the third request corresponds to the second request comprises:
judging whether the second plaintext parameters are the same as the first plaintext parameters, if so, judging whether the second plaintext request header is the same as the first plaintext request header, and if so, determining that the third request corresponds to the second request; and/or the presence of a gas in the atmosphere,
the step of obtaining the first plaintext parameter from the second request is followed by:
classifying the first encrypted log according to the first plaintext parameter;
extracting label information from the first plain text parameter, and correspondingly storing the label information and the first encryption log.
The invention also provides a log management system, which comprises:
the system comprises a first request sending module, a first encryption module and a second request sending module, wherein the first request sending module is used for sending a first request to a target server node, the first request is used for triggering the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate the second request, and the second request comprises the first encrypted log;
a second request receiving module, configured to receive, through a log interface, the second request sent by the target server node through a target algorithm interface, and obtain the first encrypted log from the second request;
a third request capturing module, configured to capture a third request from the target algorithm interface, where the third request includes a second plaintext log;
the first judgment module is used for judging whether the third request corresponds to the second request or not, if so, an encryption module is called, and the encryption module is used for encrypting the second plaintext log by using a public key corresponding to the target algorithm to obtain a second encrypted log;
and the second judgment module is used for judging whether the first encryption log and the second encryption log are the same or not, and if so, determining that the target algorithm is safe.
Preferably, the first request sending module is further configured to generate a pair of a public key and a private key;
the first request comprises the public key;
the second request comprises the first encryption log, an encryption request header and first plaintext parameters, wherein the encryption request header is obtained by encrypting the first plaintext request header by the target server node by using the public key.
Preferably, the second request receiving module is further configured to:
judging whether the private key is matched with the encryption request head, if so, decrypting the encryption request head by using the private key to obtain the first plaintext request head, and acquiring the first encryption log from the second request;
and acquiring the first plaintext parameters from the second request.
Preferably, the third request further includes a second plaintext request header and a second plaintext parameter;
the first judging module comprises:
a first judging unit, configured to judge whether the second plaintext parameter is the same as the first plaintext parameter, if so, invoke a second judging unit, where the second judging unit is configured to judge whether the second plaintext request header is the same as the first plaintext request header, and if so, determine that the third request corresponds to the second request; and/or the presence of a gas in the gas,
the second request receiving module is further configured to:
classifying the first encrypted log according to the first plaintext parameter;
extracting label information from the first plain text parameter, and correspondingly storing the label information and the first encryption log.
The invention further provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory and used for running on the processor, wherein the processor realizes the log management method when executing the computer program.
The present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the aforementioned log management method.
The positive progress effects of the invention are as follows: the method and the device complete the monitoring of algorithm safety through the management of the logs, determine that the encrypted data is not tampered, do not need to invade the federal learning products of manufacturers and carry out a large amount of personalized operations aiming at the federal learning products of different manufacturers, simplify the operation, and save the time cost and the labor cost.
Drawings
Fig. 1 is a first flowchart of a log management method according to embodiment 1 of the present invention.
Fig. 2 is a second flowchart of the log management method provided in embodiment 1 of the present invention.
Fig. 3 is a flowchart of S107 provided in embodiment 1 of the present invention.
Fig. 4 is a schematic block diagram of a log management system according to embodiment 2 of the present invention.
Fig. 5 is a block diagram of the first determining module 24 according to embodiment 2 of the present invention.
Fig. 6 is a schematic structural diagram of an electronic device provided in embodiment 3 of the present invention.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the invention thereto.
Example 1
The present embodiment provides a log management method, as shown in fig. 1, the log management method includes the following steps:
s101, a first request is sent to a target server node, the first request is used for triggering the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate a second request, and the second request comprises the first encrypted log.
Specifically, in this embodiment, the target server node is a server node of a federal learning product that needs to monitor algorithm security, and may send the corresponding first requests to all server nodes of the federal learning product that needs to monitor algorithm security at one time, or may send the first requests respectively in sequence until all server nodes of the federal learning product that need to monitor algorithm security receive the first requests.
S102, receiving a second request sent by the target server node through the target algorithm interface through the log interface.
S103, acquiring the first encryption log from the second request.
S104, capturing a third request from the target algorithm interface, wherein the third request comprises a second plaintext log.
S105, judging whether the third request corresponds to the second request; if yes, go to step S106.
S106, encrypting the second plaintext log by using the public key corresponding to the target algorithm to obtain a second encrypted log.
S107, judging whether the first encryption log and the second encryption log are the same, if so, executing S108.
And S108, determining the safety of the target algorithm.
As shown in fig. 2, in this embodiment, before S101, the method further includes:
s1101, generating a pair of public key and private key.
The first request includes a public key.
Specifically, in the present embodiment, the parameters ClientId (client identification number) and ClientSecret (client key) are also included in the first request.
Specifically, in this embodiment, the second request includes a first encrypted log, an encrypted request header, and a first plaintext parameter, where the encrypted request header is obtained by encrypting, by the target server node, the first plaintext request header using a public key.
As shown in fig. 2, specifically, in the present embodiment, S103 includes the steps of:
s1103, judging whether the private key is matched with the encryption request header, if so, executing S2103.
Specifically, in this embodiment, the matching of the private key with the decryption request header means that the private key can decrypt the encryption request header.
S2103, the encrypted request head is decrypted by using a private key to obtain a first plaintext request head.
As shown in fig. 2, specifically, in the present embodiment, the step of S103 is followed by:
s3103, the first plaintext parameter is obtained from the second request.
S4103, classifying the first encryption log according to the first plaintext parameter.
And S5103, extracting the label information from the first plaintext parameter, and correspondingly storing the label information and the first encryption log.
Specifically, in this embodiment, the content of the plaintext parameters includes a server address, manufacturer information, product information, algorithm type information, log type, and the like. The types of the log include an operation log, a task log, an API (Application Programming Interface) log, a verification log, and the like. The plaintext parameters corresponding to the operation logs comprise a node ID, manufacturer information, product information and a label related to an algorithm type, the plaintext parameters corresponding to the task logs comprise a node ID, a log type, an operator account, manufacturer information, product information and a label related to the algorithm type, the plaintext parameters corresponding to the API logs comprise a node ID, a log type, manufacturer information, product information and a label related to the algorithm type, and the plaintext parameters corresponding to the evidence-storing logs comprise a node ID, manufacturer information, product information and a label related to the algorithm type.
Specifically, in this embodiment, the third request further includes a second plaintext request header and a second plaintext parameter.
As shown in fig. 3, in particular, in this embodiment, S107 specifically includes the steps of:
s1071, judging whether the second plaintext parameter is the same as the first plaintext parameter, if so, executing S1072.
S1072, judging whether the second plaintext request header is the same as the first plaintext request header, if so, executing S1073.
Specifically, in this embodiment, after receiving the first request, the target server node maintains the ClientId and the ClientSecret included in the first request, generates a Timestamp and a Nonce (Number one), and then combines the ClientId, the ClientSecret, the Timestamp, and the Nonce to obtain a plaintext request header. The Timestamp in the plaintext request header may indicate the time at which the target server node generated the plaintext request header.
Specifically, in this embodiment, the log management system is used to implement the log management method in this embodiment, after obtaining the plaintext request header, the log management system compares the Timestamp in the plaintext request header with its own Timestamp, and determines whether the time difference between the Timestamp and the plaintext request header is within a preset range, and if the time difference exceeds the preset range, it indicates that the received request is out of date, and the log management system discards the received request, and retransmits the first request to the target server node or captures a third request from the target server node. The Timestamp of the log management system may indicate the time at which the log management system received the request.
S1073, determining that the third request corresponds to the second request.
The embodiment provides a log management method, which completes the monitoring of algorithm safety through the management of logs, determines that encrypted data is not tampered, and does not need to invade federal learning products of manufacturers and perform a large amount of personalized operations aiming at federal learning products of different manufacturers, thereby simplifying the operation and saving the time cost and the labor cost; when the log interface is called, the encryption technology is used, so that the safety of interface calling is ensured; the log information of all the federal learning products is collected and classified and stored, and the integrity and the normalization of the log are guaranteed.
Example 2
The present embodiment provides a log management system, as shown in fig. 4, the log management system includes a first request sending module 21, a second request receiving module 22, a third request capturing module 23, a first judging module 24, an encrypting module 25, and a second judging module 26.
The first request sending module 21 is configured to send a first request to a target server node, where the first request is used to trigger the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate a second request, where the second request includes the first encrypted log.
Specifically, in this embodiment, the target server node is a server node of the federal learning product requiring monitoring algorithm security, and may send the corresponding first requests to all server nodes of the federal learning product requiring monitoring algorithm security at a time, or may send the corresponding first requests respectively in sequence until all server nodes of the federal learning product requiring monitoring algorithm security receive the first requests.
The second request receiving module 22 is configured to receive, through the log interface, a second request sent by the target server node through the target algorithm interface, and obtain the first encrypted log from the second request.
The third request capture module 23 is configured to capture a third request from the target algorithm interface, where the third request includes a second plaintext log.
The first determining module 24 is configured to determine whether the third request corresponds to the second request, and if so, invoke the encrypting module 25, where the encrypting module is configured to encrypt the second plaintext log by using a public key corresponding to the target algorithm, to obtain a second encrypted log.
The second judging module 26 is configured to judge whether the first encryption log and the second encryption log are the same, and if yes, determine that the target algorithm is safe.
Specifically, in this embodiment, the first request sending module 21 is further configured to generate a pair of a public key and a private key. The first request includes a public key.
Specifically, in this embodiment, the first request further includes parameters ClientId and ClientSecret.
The second request comprises a first encryption log, an encryption request header and a first plaintext parameter, wherein the encryption request header is obtained by encrypting the first plaintext request header by the target server node by using a public key.
Specifically, in this embodiment, the second request receiving module 22 is further configured to determine whether the private key is matched with the encrypted request header, and if so, decrypt the encrypted request header by using the private key to obtain a first plaintext request header, and obtain a first encrypted log from the second request.
Specifically, in this embodiment, the second request receiving module 22 is further configured to obtain the first plaintext parameter from the second request.
Specifically, in this embodiment, the third request further includes a second plaintext request header and a second plaintext parameter.
As shown in fig. 5, in particular, in the present embodiment, the first judging module 24 includes a first judging unit 241 and a second judging unit 242.
The first determining unit 241 is configured to determine whether the second plaintext parameter is the same as the first plaintext parameter, if so, invoke the second determining unit 242, and the second determining unit 242 is configured to determine whether the second plaintext request header is the same as the first plaintext request header, and if so, determine that the third request corresponds to the second request. Specifically, in this embodiment, after receiving the first request, the target server node maintains the ClientId and the ClientSecret included in the first request, generates the Timestamp and the Nonce, and then combines the ClientId, the ClientSecret, the Timestamp, and the Nonce to obtain the plaintext request header. The Timestamp in the plaintext request header may indicate the time at which the target server node generated the plaintext request header.
Specifically, in this embodiment, after obtaining the plaintext request header, the log management system compares the Timestamp in the plaintext request header with its own Timestamp, and determines whether the time difference between the two timestamps is within a preset range, and if the time difference exceeds the preset range, the received request is expired, and the log management system discards the received request, and retransmits the first request to the target server node or captures a third request from the target server node. The Timestamp of the log management system may indicate the time the log management system received the request.
Specifically, in this embodiment, the second request receiving module 22 is further configured to classify the first encrypted log according to the first plaintext parameter, extract the tag information from the first plaintext parameter, and store the tag information and the first encrypted log correspondingly. The contents of the plaintext parameters in this embodiment include server address, manufacturer information, product information, algorithm type information, log type, and the like. The types of logs include operation logs, task logs, API logs, evidence-storing logs, and the like. The plaintext parameters corresponding to the operation logs comprise node IDs, manufacturer information, product information and algorithm type related labels, the plaintext parameters corresponding to the task logs comprise the node IDs, log types, operator accounts, manufacturer information, product information and algorithm type related labels, the plaintext parameters corresponding to the API logs comprise the node IDs, the log types, the manufacturer information, the product information and algorithm type related labels, and the plaintext parameters corresponding to the evidence storage logs comprise the node IDs, the manufacturer information, the product information and the algorithm type related labels.
The embodiment provides a log management system, which completes the monitoring of algorithm safety through the management of logs, determines that encrypted data is not tampered, does not need to invade federal learning products of manufacturers and perform a large amount of personalized operations aiming at federal learning products of different manufacturers, simplifies the operation, and saves time cost and labor cost; when the log interface is called, an encryption technology is used, so that the safety of interface calling is ensured; the log information of all the federal learning products is collected and classified and stored, and the completeness and the normalization of the log are guaranteed.
Example 3
Fig. 6 is a schematic structural diagram of an electronic device according to embodiment 3 of the present invention. Comprising a memory, a processor and a computer program stored in the memory and adapted to run on the processor, the processor implementing the log management method of the aforementioned embodiment 1 when executing the computer program. The electronic device 30 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
The electronic device 30 may be embodied in the form of a general purpose computing device, which may be, for example, a server device. The components of the electronic device 30 may include, but are not limited to: the at least one processor 31, the at least one memory 32, and a bus 33 connecting the various system components (including the memory 32 and the processor 31).
The bus 33 includes a data bus, an address bus, and a control bus.
The memory 32 may include volatile memory, such as Random Access Memory (RAM) 321 and/or cache memory 322, and may further include Read Only Memory (ROM) 323.
The processor 31 executes various functional applications and data processing, such as the log management method of embodiment 1 of the present invention, by running the computer program stored in the memory 32.
The electronic device 30 may also communicate with one or more external devices 34 (e.g., a keyboard, a pointing device, etc.). Such communication may be through input/output (I/O) interfaces 35. Also, model-generating device 30 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via network adapter 36. As shown, network adapter 36 communicates with the other modules of model-generating device 30 via bus 33. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the model-generating device 30, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, to name a few.
It should be noted that although in the above detailed description several units/modules or sub-units/modules of the electronic device are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module according to embodiments of the invention. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Example 4
The present invention also provides a computer-readable medium on which a computer program is stored, the computer program, when executed by a processor, implementing the log management method of the foregoing embodiment 1.
More specific examples, among others, that the readable storage medium may employ may include, but are not limited to: a portable disk, hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible implementation, the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the log management method implementing embodiment 1 when the program product is run on the terminal device.
Where program code for carrying out the invention is written in any combination of one or more programming languages, the program code may be executed entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device and partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and that the scope of the invention is defined by the appended claims. Various changes or modifications to these embodiments may be made by those skilled in the art without departing from the principle and spirit of this invention, and these changes and modifications are within the scope of this invention.
Claims (10)
1. A log management method, characterized in that the log management method comprises:
sending a first request to a target server node, wherein the first request is used for triggering the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate a second request, and the second request comprises the first encrypted log;
receiving the second request sent by the target server node through a target algorithm interface through a log interface, and acquiring the first encrypted log from the second request;
capturing a third request from the target algorithm interface, wherein the third request comprises a second plaintext log;
judging whether the third request corresponds to the second request, if so, encrypting the second plaintext log by using a public key corresponding to the target algorithm to obtain a second encrypted log;
and judging whether the first encryption log and the second encryption log are the same or not, and if so, determining that the target algorithm is safe.
2. The log management method of claim 1,
the step of sending the first request to the target server node may be preceded by:
generating a pair of public key and private key;
the first request includes the public key;
the second request comprises the first encryption log, an encryption request header and a first plaintext parameter, wherein the encryption request header is obtained by encrypting the first plaintext request header by the target server node by using the public key.
3. The log management method of claim 2,
the step of obtaining the first encrypted log from the second request may be preceded by:
judging whether the private key is matched with the encryption request head, if so, decrypting the encryption request head by using the private key to obtain the first plaintext request head, and executing the step of acquiring the first encryption log from the second request;
the step of obtaining the first encrypted log from the second request may be followed by:
and acquiring the first plaintext parameters from the second request.
4. The log management method of claim 3,
the third request also comprises a second plaintext request header and a second plaintext parameter;
the step of determining whether the third request corresponds to the second request comprises:
judging whether the second plaintext parameters are the same as the first plaintext parameters, if so, judging whether the second plaintext request header is the same as the first plaintext request header, and if so, determining that the third request corresponds to the second request; and/or the presence of a gas in the atmosphere,
the step of obtaining the first plaintext parameter from the second request is followed by:
classifying the first encrypted log according to the first plaintext parameter;
extracting label information from the first plain text parameter, and correspondingly storing the label information and the first encryption log.
5. A log management system, characterized in that the log management system comprises:
the system comprises a first request sending module, a first encryption module and a second request sending module, wherein the first request sending module is used for sending a first request to a target server node, the first request is used for triggering the target server node to encrypt a first plaintext log by using a target algorithm to obtain a first encrypted log and generate the second request, and the second request comprises the first encrypted log;
a second request receiving module, configured to receive, through a log interface, the second request sent by the target server node through a target algorithm interface, and obtain the first encrypted log from the second request;
a third request capture module, configured to capture a third request from the target algorithm interface, where the third request includes a second plaintext log;
the first judgment module is used for judging whether the third request corresponds to the second request or not, if so, an encryption module is called, and the encryption module is used for encrypting the second plaintext log by using a public key corresponding to the target algorithm to obtain a second encrypted log;
and the second judgment module is used for judging whether the first encryption log and the second encryption log are the same or not, and if so, determining that the target algorithm is safe.
6. The log management system of claim 5,
the first request sending module is also used for generating a pair of public key and private key;
the first request comprises the public key;
the second request comprises the first encryption log, an encryption request header and first plaintext parameters, wherein the encryption request header is obtained by encrypting the first plaintext request header by the target server node by using the public key.
7. The log management system of claim 6,
the second request receiving module is further configured to:
judging whether the private key is matched with the encryption request head, if so, decrypting the encryption request head by using the private key to obtain the first plaintext request head, and acquiring the first encryption log from the second request;
and acquiring the first plaintext parameters from the second request.
8. The log management system of claim 7,
the third request also comprises a second plaintext request header and a second plaintext parameter;
the first judging module comprises:
a first judging unit, configured to judge whether the second plaintext parameter is the same as the first plaintext parameter, if so, invoke a second judging unit, where the second judging unit is configured to judge whether the second plaintext request header is the same as the first plaintext request header, and if so, determine that the third request corresponds to the second request; and/or the presence of a gas in the atmosphere,
the second request receiving module is further configured to:
classifying the first encrypted log according to the first plaintext parameter;
extracting label information from the first plain text parameter, and correspondingly storing the label information and the first encryption log.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and adapted to run on the processor, wherein the processor implements the log management method of any of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the log management method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211560352.3A CN115632879B (en) | 2022-12-07 | 2022-12-07 | Log management method, system, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211560352.3A CN115632879B (en) | 2022-12-07 | 2022-12-07 | Log management method, system, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115632879A true CN115632879A (en) | 2023-01-20 |
| CN115632879B CN115632879B (en) | 2023-04-11 |
Family
ID=84910980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211560352.3A Active CN115632879B (en) | 2022-12-07 | 2022-12-07 | Log management method, system, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115632879B (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106506552A (en) * | 2016-12-28 | 2017-03-15 | 北京奇艺世纪科技有限公司 | A kind of HTTP request transmission method and device |
| CN108833091A (en) * | 2018-05-28 | 2018-11-16 | 武汉斗鱼网络科技有限公司 | A kind of encryption method of journal file, decryption method and device |
| CN109639676A (en) * | 2018-12-12 | 2019-04-16 | 杭州安恒信息技术股份有限公司 | The method, apparatus, equipment and system of tampering detection when log transmission |
| CN110661748A (en) * | 2018-06-28 | 2020-01-07 | 武汉斗鱼网络科技有限公司 | Log encryption method, log decryption method and log encryption device |
| CN110855439A (en) * | 2019-12-17 | 2020-02-28 | 深圳前海环融联易信息科技服务有限公司 | HTTP encryption method, device, computer equipment and storage medium |
| US20200313878A1 (en) * | 2019-03-29 | 2020-10-01 | Microsoft Technology Licensing, Llc | Secure and verifiable data access logging system |
| CN112132198A (en) * | 2020-09-16 | 2020-12-25 | 建信金融科技有限责任公司 | Data processing method, device and system and server |
| CN112235243A (en) * | 2020-09-10 | 2021-01-15 | 李文华 | Log audit security platform based on Web application security |
| US20210097195A1 (en) * | 2017-10-30 | 2021-04-01 | Abb Schweiz Ag | Privacy-Preserving Log Analysis |
| CN113344222A (en) * | 2021-06-29 | 2021-09-03 | 福建师范大学 | Safe and credible federal learning mechanism based on block chain |
| CN113723623A (en) * | 2021-08-10 | 2021-11-30 | 深圳致星科技有限公司 | Federal learning auditing device, system and method |
| CN114448601A (en) * | 2022-03-01 | 2022-05-06 | 南京航空航天大学 | Distributed federal learning security defense method based on end edge cloud architecture and application |
| CN115085902A (en) * | 2022-06-09 | 2022-09-20 | 深圳供电局有限公司 | Power grid dispatching log management method and system |
| CN115225265A (en) * | 2022-06-20 | 2022-10-21 | 中国电信股份有限公司 | Log management method and device, electronic equipment and storage medium |
-
2022
- 2022-12-07 CN CN202211560352.3A patent/CN115632879B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106506552A (en) * | 2016-12-28 | 2017-03-15 | 北京奇艺世纪科技有限公司 | A kind of HTTP request transmission method and device |
| US20210097195A1 (en) * | 2017-10-30 | 2021-04-01 | Abb Schweiz Ag | Privacy-Preserving Log Analysis |
| CN108833091A (en) * | 2018-05-28 | 2018-11-16 | 武汉斗鱼网络科技有限公司 | A kind of encryption method of journal file, decryption method and device |
| CN110661748A (en) * | 2018-06-28 | 2020-01-07 | 武汉斗鱼网络科技有限公司 | Log encryption method, log decryption method and log encryption device |
| CN109639676A (en) * | 2018-12-12 | 2019-04-16 | 杭州安恒信息技术股份有限公司 | The method, apparatus, equipment and system of tampering detection when log transmission |
| US20200313878A1 (en) * | 2019-03-29 | 2020-10-01 | Microsoft Technology Licensing, Llc | Secure and verifiable data access logging system |
| CN110855439A (en) * | 2019-12-17 | 2020-02-28 | 深圳前海环融联易信息科技服务有限公司 | HTTP encryption method, device, computer equipment and storage medium |
| CN112235243A (en) * | 2020-09-10 | 2021-01-15 | 李文华 | Log audit security platform based on Web application security |
| CN112132198A (en) * | 2020-09-16 | 2020-12-25 | 建信金融科技有限责任公司 | Data processing method, device and system and server |
| CN113344222A (en) * | 2021-06-29 | 2021-09-03 | 福建师范大学 | Safe and credible federal learning mechanism based on block chain |
| CN113723623A (en) * | 2021-08-10 | 2021-11-30 | 深圳致星科技有限公司 | Federal learning auditing device, system and method |
| CN114448601A (en) * | 2022-03-01 | 2022-05-06 | 南京航空航天大学 | Distributed federal learning security defense method based on end edge cloud architecture and application |
| CN115085902A (en) * | 2022-06-09 | 2022-09-20 | 深圳供电局有限公司 | Power grid dispatching log management method and system |
| CN115225265A (en) * | 2022-06-20 | 2022-10-21 | 中国电信股份有限公司 | Log management method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115632879B (en) | 2023-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108780485B (en) | Pattern matching based data set extraction | |
| CN108304704B (en) | Authority control method and device, computer equipment and storage medium | |
| US8966249B2 (en) | Data security and integrity by remote attestation | |
| CN112217835B (en) | Message data processing method and device, server and terminal equipment | |
| CN107483472B (en) | Network security monitoring method and device, storage medium and server | |
| US8544100B2 (en) | Detecting secure or encrypted tunneling in a computer network | |
| CN108347361B (en) | Application program testing method and device, computer equipment and storage medium | |
| CN109450777B (en) | Session information extraction method, device, equipment and medium | |
| US20130145483A1 (en) | System And Method For Processing Protected Electronic Communications | |
| CN110855699B (en) | Flow auditing method and device, server and auditing equipment | |
| US20140195793A1 (en) | Remotely Establishing Device Platform Integrity | |
| CN103631678A (en) | Backup method, restoring method and device for client software | |
| CN110737639A (en) | Audit log method, device, computer equipment and storage medium | |
| US20200052902A1 (en) | Digital data locker system providing enhanced security and protection for data storage and retrieval | |
| CN110888778A (en) | Cloud desktop-based log file monitoring system and method | |
| CN112507264A (en) | System and method for automatically realizing network electronic evidence obtaining through traceability | |
| US8745010B2 (en) | Data storage and archiving spanning multiple data storage systems | |
| CN114866258A (en) | Method and device for establishing access relationship, electronic equipment and storage medium | |
| CN111371889A (en) | Message processing method and device, Internet of things system and storage medium | |
| CN107133517B (en) | Data recovery method based on data encryption and calculation in memory | |
| CN115632879B (en) | Log management method, system, electronic device and storage medium | |
| KR101641306B1 (en) | Apparatus and method of monitoring server | |
| CN114189515B (en) | SGX-based server cluster log acquisition method and device | |
| CN115250467A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN111885069B (en) | Computer network safety system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |