Log information processing method, device, equipment, storage medium and program product

Abstract

According to an embodiment of the present disclosure, a method, apparatus, device, storage medium and program product for log information processing are provided. The method includes: determining the source of a target log in response to a log query request, wherein the log query request is used to indicate that the target user requests to query the target log; determining a log desensitization policy corresponding to the source of the target log, the log desensitization policy is determined based on the log registration information associated with the source, and the log registration information is used to indicate the physical meaning of the variable items in the target log; and desensitizing the variable items related to the target user in the target log according to the business attribute information, log desensitization policy and business authority information of the target user, so as to provide the target user with a desensitized target log. According to the facts disclosed in the present disclosure, it is possible to systematically and efficiently be compatible with various different log business party requirements, and control log information query access to avoid sensitive data leakage.

Description

Technical Field

[0001] Various implementations of the present disclosure relate to the computer field, and more specifically, to a method, apparatus, device, and computer storage medium for determining log information processing. Background Art

[0002] For various computing applications, log information is important data for system development and maintenance. Usually, log information is mostly unstructured data, and various types of information may be integrated into one log entry.

[0003] Since different log demanders are accustomed to importing various types of data into logs, it is very likely that some business-sensitive data will be included in the logs. The transmission of log information will lead to the leakage of these sensitive data. Therefore, in actual business, it is necessary to consider the log demander's demand for the log data itself, and also consider the problem that the log information may carry sensitive data. Especially when the demand for logs is relatively large, how to systematically and efficiently be compatible with the needs of various different log business parties, and control log information query access to avoid sensitive data leakage, is a technical problem that urgently needs to be solved. Summary of the invention

[0004] In the first aspect of the present disclosure, a method for log information processing is provided. The method includes: receiving a log query request, the log query request is used to indicate that a target user requests to query a target log; in response to the log query request, determining the source of the target log, the target log is a log with a preset structured format generated via a preset log software development kit, the preset structured format identifies variable items in the log through a preset structure identifier; determining a log desensitization policy corresponding to the source of the target log, the log desensitization policy is determined based on log registration information associated with the source, and the log registration information is used to indicate the physical meaning of the variable items in the target log; and desensitizing the variable items related to the target user in the target log according to the business attribute information of the target user, the log desensitization policy, and the pre-configured business authority information, so as to provide the target user with a desensitized target log.

[0005] In the second aspect of the present disclosure, a device for log information processing is provided. The device includes: a receiving module configured to receive a log query request, the log query request is used to indicate that a target user requests to query a target log; a first determination module configured to determine the source of the target log in response to the log query request, the target log is a log with a preset structured format generated via a preset log software development kit, and the preset structured format identifies variable items in the log through a preset structure identifier; a second determination module configured to determine a log desensitization strategy corresponding to the source of the target log, the log desensitization strategy is determined based on log registration information associated with the source, and the log registration information is used to indicate the physical meaning of the variable items in the target log; and a processing module configured to perform desensitization processing on the variable items related to the target user in the target log according to the business attribute information of the target user, the log desensitization strategy, and the pre-configured business authority information, so as to provide the target user with a desensitized target log.

[0006] In a third aspect of the present disclosure, an electronic device is provided, comprising: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to the first aspect of the present disclosure.

[0007] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, on which one or more computer instructions are stored, wherein the one or more computer instructions are executed by a processor to implement the method according to the first aspect of the present disclosure.

[0008] In a fifth aspect of the present disclosure, a computer program product is provided, which includes one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the method according to the first aspect of the present disclosure.

[0009] According to various embodiments of the present disclosure, it is possible to systematically and efficiently meet the requirements of various different log service providers, and control log information query access to avoid sensitive data leakage. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram illustrating an example environment in which various embodiments of the present disclosure can be implemented;

[0012] Figure 2 A flowchart showing an example process of log information processing according to some embodiments of the present disclosure;

[0013] Figure 3 A schematic structural block diagram showing an apparatus for processing log information according to some embodiments of the present disclosure; and

[0014] Figure 4 A block diagram of a computing device capable of implementing various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0015] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0016] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0017] As discussed above, in actual business, it is necessary to consider the needs of log demanders for log data itself, and also to consider the problem that log information may carry sensitive data. Especially when the demand for logs is relatively large, how to systematically and efficiently be compatible with the needs of various different log business parties and control log information query access to avoid sensitive data leakage is a technical problem that urgently needs to be solved.

[0018] In order to at least partially solve one or more of the above problems and other potential problems, the example embodiments of the present disclosure propose a scheme for log information processing. In general, according to the embodiments described herein, first, a log query request is received, and the log query request is used to indicate that the target user requests to query the target log. In response to the log query request, the source of the target log can be determined, wherein the target log is a log with a preset structured format generated via a preset log software development kit (Software Development Kit, SDK), and the preset structured format identifies the variable items in the log by a preset structure identifier. Accordingly, a log desensitization policy corresponding to the source of the target log can be determined, and the log desensitization policy is determined based on the log registration information associated with the source, and the log registration information is used to indicate the physical meaning of the variable items in the target log. Further, according to the business attribute information of the target user, the log desensitization policy and the pre-configured business authority information, the variable items related to the target user in the target log are desensitized, so as to provide the target user with a desensitized target log.

[0019] According to various embodiments of the present disclosure, by utilizing the log SDK to manage the generation of structured logs, utilizing the log registration information to determine the log desensitization strategy, and performing log desensitization operations based on user business attribute information, log desensitization strategy, and sensitive data protection files, the embodiments of the present disclosure can systematically and efficiently be compatible with various different log business requirements, and control log information query access to avoid sensitive data leakage.

[0020] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0021] Figure 1 A schematic diagram of an example environment 100 in which various embodiments of the present disclosure can be implemented is shown. In the example environment 100 , a log processing device 120 receives a log query request 115 , which may indicate that a target user 110 requests to view a target log 140 .

[0022] In some embodiments, the target user 110 may be, for example, a developer or maintainer of an application, who may initiate a request to view various types of logs generated during the running or debugging process of the program code.

[0023] like Figure 1 As shown, the target log 140 may be generated by the running device 130 during the running of the program code. In some embodiments, in order to ensure the security of the log information, the target log 140 directly generated by the running device 130 may not be directly accessible to the target user 110.

[0024] In some embodiments, the target log 140 may be, for example, a log having a preset structured format generated via a preset log software development kit, wherein the preset structured format identifies variable items in the log by using a preset structure identifier.

[0025] Exemplarily, the operating device 130 may be deployed in an environment of a trusted technology partner, so that the target user 110 cannot directly access the target log generated by the operating device 130 .

[0026] In some embodiments, the trusted technology partner may also provide the target user 110 with a log processing device 120 that can be accessed through a network. The log processing device 120 may be a gateway device managed by the trusted technology partner.

[0027] As will be described in detail below, the log processing device 120 can determine the source of the target log 140 and obtain the log desensitization strategy 150 corresponding to the source. In some embodiments, the log desensitization strategy 150 can be determined based on the log registration information associated with the source, where the log registration information can be used to indicate the physical meaning of the variable items in the target log 140.

[0028] Furthermore, the log processing device 120 may perform desensitization processing on the target log 140 based on the log desensitization strategy 150. Exemplarily, the log processing device 120 may provide the target user 110 with the desensitized target log 160.

[0029] The following will be combined Figure 2 The process of log management by the log processing device 120 is described in detail. Figure 2 A flowchart of an example process 200 of log information processing according to some embodiments of the present disclosure is shown. The process 200 may be performed, for example, in Figure 1 The log processing device 120 is implemented.

[0030] like Figure 2 As shown, in box 210 , the log processing device 120 receives a log query request 115 , wherein the log query request is used to indicate that the target user 110 requests to query the target log 140 .

[0031] In some embodiments, the log processing device 120 may receive the log query request 115 from the target user 110, for example, via a dedicated gateway device. In some embodiments, the log query request 115 may protect the user identity of the target user 110, for example.

[0032] In block 220, the log processing device 120 determines the source of the target log 140 in response to the log query request 115, wherein the target log 140 is a log having a preset structured format generated via a preset log software development kit SDK, and the preset structured format identifies variable items in the log 140 through a preset structure identifier. The preset structure identifier may include a specific symbol or character for indicating that the corresponding log content is a variable item.

[0033] In some embodiments, the source of the target log 140 is used to indicate the ownership of the code file that generates the target log 140. For example, some code files that generate logs may be derived from a third-party underlying framework, and accordingly, the source of such logs may be determined as a specific underlying framework, such as the Kite development framework.

[0034] As another example, some code files that generate logs may be developed by a business party. Accordingly, the source of such logs may be determined to be a specific business party.

[0035] In some embodiments, the log processing device 120 can determine the type of the target log 140 based on the compilation path associated with the target log 140, where the type indicates that the target log belongs to a framework log or a business log. The framework log is a log generated by the execution of the underlying framework code, and the business log is a log generated by the execution of the business logic code.

[0036] In some embodiments, considering the compilation characteristics of framework code files and business code files, the compilation path of the code file that generates the target log can indicate whether such code file belongs to a framework code file or a business code file.

[0037] Specifically, the log processing device 120 may extract a corresponding compilation path from the content of the target log 140 , and further determine whether the target log belongs to a framework log or a business log.

[0038] Further, the log processing device 120 may determine the source of the target log from the target log 140 based on the determined type, wherein the source indicates an underlying framework or a business party that generates the target log 140 .

[0039] Specifically, in response to determining that the target log 140 is a framework log, the log processing device 120 can determine the framework identifier from the compilation path of the target log 140 as the source of the target log 140. In addition, in response to determining that the target log 140 is a business log, the log processing device 120 can determine the service name from the target log 140 as the source of the target log 140.

[0040] In some embodiments, in order to improve the reliability of log information processing, the log processing device 120 may also perform various types of verifications before determining the source of the target log 140 .

[0041] In some embodiments, the log processing device 120 may determine the format of the target log. Only when it is determined that the format meets the predetermined specification, the log processing device 120 determines the source of the target log 140 from the target log 140. On the contrary, if it is determined that the format of the target log 140 does not meet the predetermined specification, the log processing device 120 may consider that the target log 140 should not be disclosed, and refuse to provide the target log 140.

[0042] In some embodiments, the log processing device 120 may determine the content format of the target log 140 in response to the log query request 115. Further, in response to determining that the content format of the target log 140 complies with a predetermined format specification, the log processing device 120 may determine the service source of the target log. In some embodiments, the predetermined format specification may indicate that the log content includes a service name, a compilation path, a code version number, and a preset structure identifier.

[0043] In some embodiments, the log processing device 120 may also determine version information of the target log 140. For example, the log processing device 120 may determine a code version number from the target log 140. If it is determined that the version information indicates that the target log 140 is generated using a predetermined log software development kit, the log processing device 120 may further determine the source of the target log 140.

[0044] On the contrary, if it is determined that the version information indicates that the target log 140 is not generated using a predetermined log SDK, the log processing device 120 may consider that the target log 140 should not be disclosed, and refuse to provide the target log 140 .

[0045] In box 230 , the log processing device 120 determines a log desensitization policy 150 corresponding to the source of the target log 140 , wherein the log desensitization policy 150 is determined based on log registration information associated with the source, and the log registration information is used to indicate the physical meaning of the variable items in the target log 140 .

[0046] Exemplarily, a developer or operator may submit log registration information to a log registration platform provided by a trusted technical partner to register the contents that can be revealed in logs generated by different sources, such as variables or predetermined strings. Further, the trusted technical partner may review the log registration information to determine the contents that can be revealed in the log, thereby forming a log desensitization strategy 150 corresponding to the source.

[0047] In some embodiments, the variable items allowed to be registered may be different for framework logs and business logs. Exemplarily, in response to determining that the type indicates that the target log 140 is a framework log, the log processing device 120 can determine the log desensitization strategy corresponding to the underlying framework based on the framework class indicated by the source, wherein the log desensitization strategy at least indicates the first group of variable items allowed to be exposed in the target log and the first description information about the first group of variable items.

[0048] In some embodiments, the first description information may indicate a first variable item type of the first group of variable items, and the first variable item type includes one of the following: a character variable, a Boolean variable, a floating point variable, or an integer variable.

[0049] In some embodiments, the log registration information may be generated based on a registration request for adding a candidate log registration information entry, wherein the registration request at least indicates identification information and description information corresponding to the candidate log registration information entry. Such description information may include, for example, the type of the variable item and the physical meaning description information of the variable item.

[0050] For example, a developer may submit a request to add a candidate log registration information entry to the Kite development framework through the log registration platform. For example, a developer may submit a variable item name, variable item type, and physical meaning description information about the variable item through the log registration platform.

[0051] Considering that framework logs usually do not include sensitive information, when developers register variable items that are allowed to be exposed in framework logs, the variable item types that can be specified can include not only floating-point variables and integer variables, but also character variables. Therefore, the embodiments of the present disclosure can provide developers with richer information while ensuring the compliance of log content.

[0052] In some embodiments, considering that the business party logs will have a greater probability of being exposed to sensitive data, the log registration platform may, for example, limit the types of variable items that are allowed to be exposed in the business party logs.

[0053] Exemplarily, if it is determined that the type indicates that the target log 140 is a business-type log, the log processing device 120 may determine the log desensitization policy 150 corresponding to the business party based on the business party indicated by the source.

[0054] In some embodiments, similar to framework logs, the log desensitization policy 150 indicates, for example, a second group of variable items that are allowed to be viewed in the target log and second description information about the second group of variable items.

[0055] In some embodiments, the types of variable items allowed to be exposed in the framework log may be limited, for example, to ensure the compliance of the log content. Specifically, the second description information indicates, for example, the second variable item type of the second group of variable items, and the second variable item type includes one of the following: a Boolean variable, a floating-point variable, or an integer variable, but does not include a character variable.

[0056] In some embodiments, the log desensitization policy 150 of the framework log may also indicate, for example, a string pattern that is allowed to be exposed in the target log 140 , wherein the string pattern represents at least one group of strings that are allowed to be exposed.

[0057] Considering that developers often want to obtain richer semantic information to facilitate the interpretation of log content when the program automatically generates log content, the log registration platform can also allow, for example, to submit a registration request for a string style through log registration information.

[0058] For example, a developer can create a string pattern such as "AAA{{Code=d%}}BBB" for a business log generated by a specific business party on the log registration platform, so that the log content that conforms to the pattern (for example, "AAA{{Code=1}}BBB") can be exposed.

[0059] In some embodiments, the log registration information submitted by the log registration platform can be provided to the auditor for review, and after the review is passed, the log desensitization policy 150 corresponding to the source is updated accordingly. The log desensitization policy 150 can thus manage what content in the log generated by what source can be revealed in what manner.

[0060] In some embodiments, before determining the log desensitization strategy 150, the log processing device 120 may also determine whether the source is on the whitelist that allows the log to be transmitted. When it is determined that the source belongs to the whitelist that allows the log to be transmitted, the log processing device 120 may further determine the log desensitization strategy 150 corresponding to the source. On the contrary, the log processing device 120 may believe that the target log 140 should not be transmitted and refuse to provide the target log 140.

[0061] In box 240 , the log processing device 120 desensitizes the variable items related to the target user in the target log 140 according to the business attribute information of the target user 110 , the log desensitization policy 150 , and the pre-configured business authority information, so as to provide the target user 110 with a desensitized target log 160 .

[0062] In some embodiments, as discussed above, the log processing device 120 may require that the target log 140 is generated using a predetermined log SDK.

[0063] In some embodiments, the target log 140 generated based on the log SDK may include, for example, two parts, namely, a first part generated by the log SDK itself, and a second part generated by a programming framework or a business party using the log SDK.

[0064] Specifically, when the target log 140 is a framework log, the target log 140 includes a first part generated by the log software development kit SDK itself and a second part generated by the underlying framework code through the log SDK. When the target log 140 is a business log, the target log includes a first part generated by the log SDK itself and a second part generated by the business logic code through the log SDK.

[0065] From the log content, the first part is generated by the log SDK code itself, so it will not be able to access the real application data. In some embodiments, the log processing device 120 can, for example, always provide the first part without considering the log registration information 150 corresponding to the target log 140.

[0066] In some embodiments, the log processing device 120 may further distinguish the second part into text type log content and statistical type log content (also called KVS, Key-Values) based on the data type included in the second part. The statistical type log content may include multiple key-value pairs.

[0067] In some embodiments, when generating statistical log content, the log SDK always requires that the log content be organized in a predetermined format. For example, such content can be represented as "{{key=value}}", that is, two brackets are used to indicate that the key-value pair information is included therein.

[0068] Accordingly, the log processing device 120 can identify whether the second part is statistical log content by the corresponding format of the statistical log. If yes, the log processing device 120 can determine the target business sensitive data matching the target user 110 according to the business attribute information of the target user 110 and the pre-configured business authority information.

[0069] In some embodiments, the business permission information may indicate the range of logs that can be accessed by users of different business attributes. Exemplarily, the business permission information may specify the log types that users of specific business attributes are allowed to view and / or the specific variable items that are allowed to be viewed in the logs. Thus, the log processing device 120 may determine the logs that the target user 110 is allowed to view and / or the variables that are allowed to be viewed in the logs based on the business permission information and the business attributes of the target user 110.

[0070] Further, the log processing device 120 can perform desensitization processing on the variable items of the target business sensitive data in the target log 140 based on the log desensitization strategy 150. Specifically, the log processing device 120 can, for example, determine a set of target variable items that match the log desensitization strategy 150 from the target log 140, and provide the desensitized target log 160 accordingly.

[0071] For example, if the log desensitization policy 150 indicates that the variable item "key1" has been approved, the log processing device 120 can search for the variable item "key1" from the second part, and further determine whether its corresponding value meets the variable item type constraint indicated by the log desensitization policy 150. If it meets, the log processing device 120 can consider that the variable item "key1" matches the log desensitization policy 150, and make its corresponding log content, such as "{{key1=value1}}" as desensitized log content and provide it to the target user 110.

[0072] In addition, if the log processing device 120 determines that the second part is a text type log, the log processing device 120 may first remove the corresponding content from the second part based on the format characteristics of the content of the variable items recorded in the log.

[0073] For example, if the content of the second part of the target log is "AAA{{Code=2}}BBB", the log processing device 120 can determine that its corresponding string pattern is "AAA{{}}BBB" by removing "{{Code=2}}", and further determine that the string pattern has been registered and passed the review. Accordingly, the log processing device 120 can allow the log content corresponding to the string pattern to be provided to the target user 110 as the desensitized log content.

[0074] Further, for each variable item included in the text type log, the log processing device 120 can analyze each variable item based on a similar process discussed above to determine whether it matches the log desensitization strategy 150, thereby controlling the desensitization processing of each variable item.

[0075] It should be understood that the desensitized target log 160 may be provided in any appropriate manner, examples of which may include but are not limited to a graphical user interface or email to provide the desensitized target log 160. The present disclosure is not intended to limit the specific provision method.

[0076] Based on the process discussed above, by utilizing the log SDK to manage the generation of structured logs, utilizing the log registration information to determine the log desensitization strategy, and performing log desensitization operations based on user business attribute information, log desensitization strategy, and sensitive data protection files, the embodiments of the present disclosure can systematically and efficiently be compatible with various different log business requirements, and control log information query access to avoid sensitive data leakage.

[0077] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 3 A schematic structural block diagram of a log information processing device 300 according to some embodiments of the present disclosure is shown.

[0078] like Figure 3 As shown, the device 300 may include: a receiving module 310, configured to receive a log query request, the log query request is used to indicate that the target user requests to query the target log; a first determination module 320, configured to determine the source of the target log in response to the log query request, the target log is a log with a preset structured format generated via a preset log software development kit, the preset structured format identifies variable items in the log through a preset structure identifier; a second determination module 330, configured to determine a log desensitization policy corresponding to the source of the target log, the log desensitization policy is determined based on log registration information associated with the source, the log registration information is used to indicate the physical meaning of the variable items in the target log; and a processing module 340, configured to perform desensitization processing on the variable items related to the target user in the target log according to the business attribute information of the target user, the log desensitization policy and pre-configured business authority information, so as to provide the desensitized target log to the target user.

[0079] In some embodiments, the first determination module 320 is also configured to determine the type of the target log based on the compilation path associated with the target log, the type indicating that the target log belongs to a framework log or a business log, the framework log is a log generated by the execution of the underlying framework code, and the business log is a log generated by the execution of the business logic code; in response to determining that the target log is a framework log, determining a framework identifier from the compilation path of the target log as the source of the target log; in response to determining that the target log is a business log, determining a service name from the target log as the source of the target log.

[0080] In some embodiments, when the target log is a framework type log, the target log includes a first part generated by the log software development kit SDK itself and a second part generated by the underlying framework code through the log SDK; or when the target log is a business type log, the target log includes a first part generated by the log SDK itself and a second part generated by the business logic code through the log SDK.

[0081] In some embodiments, the log registration information includes the type of variable items in the target log and the physical meaning description information of the variable items; the variable items include the following types: character variables, Boolean variables, floating point variables or integer variables.

[0082] In some embodiments, the processing module 340 is further configured to: determine the business attribute information of the target user based on the user identifier of the target user; determine the target business sensitive data matching the target user based on the business attribute information of the target user and pre-configured business authority information; and perform desensitization processing on the variable items of the target business sensitive data in the target log based on the log desensitization strategy.

[0083] In some embodiments, the first determination module is further configured to: determine the content format of the target log in response to a log query request; and determine the source of the target log in response to determining that the content format of the target log conforms to a predetermined format specification, wherein the predetermined format specification indicates that the log content includes a service name, a compilation path, a code version number, and a preset structure identifier.

[0084] In some embodiments, when the target log is a business log, the log registration information further includes a set of character strings included in the target log and a set of description information of the physical meaning of the character strings.

[0085] Figure 4 A schematic block diagram of an example device 400 that can be used to implement an embodiment of the present disclosure is shown. For example, the log processing device 120 and / or the operation device 130 according to the embodiment of the present disclosure can be implemented by the device 400. As shown in the figure, the device 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 402 or computer program instructions loaded from a storage unit 408 to a random access memory (RAM) 403. In RAM 403, various programs and data required for the operation of the device 400 can also be stored. CPU 401, ROM 402 and RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0086] A number of components in the device 400 are connected to the I / O interface 405, including: an input unit 406, such as a keyboard, a mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a disk, an optical disk, etc.; and a communication unit 409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 409 allows the device 400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0087] The various processes and processing described above, such as process 200, may be performed by processing unit 401. For example, in some embodiments, process 200 may be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed on device 400 via ROM 402 and / or communication unit 409. When the computer program is loaded into RAM 403 and executed by CPU 401, one or more actions of process 200 described above may be performed.

[0088] The present disclosure may be a method, an apparatus, a system and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for executing various aspects of the present disclosure.

[0089] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.

[0090] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0091] The computer program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0092] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0093] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0094] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0095] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.

[0096] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A log information processing method, characterized in that: The method comprises: A log query request is received by a log processing device, the log query request being used to indicate that a target user requests to query a target log generated by an operating device in an environment of a trusted technology partner during a program code running process or a debugging process, wherein the target user is blocked from directly accessing the target log generated by the operating device, and wherein the trusted technology partner provides the log processing device to the target user; In response to the log query request, the log processing device determines the source of the target log, where the target log is a log with a preset structured format generated by a preset log software development kit, and the preset structured format identifies variable items in the log by a preset structure identifier; Determining, by the log processing device, a log desensitization policy corresponding to the source of the target log, the log desensitization policy being determined based on log registration information associated with the source, the log registration information being used to indicate a physical meaning of a variable item in the target log, and being submitted through a log registration platform provided by the trusted technology partner to register content that can be revealed in logs generated by different sources; and According to the business attribute information of the target user, the log desensitization policy and pre-configured business authority information, the variable items related to the target user in the target log are desensitized to provide the desensitized target log to the target user.

2. The method according to claim 1, characterized in that The step of determining the source of the target log in response to the log query request includes: Based on the compilation path associated with the target log, determine the type of the target log, the type indicating that the target log belongs to a framework log or a business log, the framework log is a log generated by the running of the underlying framework code, and the business log is a log generated by the running of the business logic code; In response to determining that the target log is a framework log, determining a framework identifier from the compilation path of the target log as a source of the target log; In response to determining that the target log is a business log, a service name is determined from the target log as a source of the target log.

3. The method according to claim 1, characterized in that When the target log is a framework log, the target log includes a first part generated by the log software development kit SDK itself and a second part generated by the underlying framework code through the log SDK; or When the target log is a business log, the target log includes a first part generated by the log SDK itself and a second part generated by the business logic code through the log SDK.

4. The method according to claim 1, characterized in that: The log registration information includes the type of the variable item in the target log and the physical meaning description information of the variable item; The variable items include the following types: character variables, Boolean variables, floating-point variables or integer variables.

5. The method according to claim 1, characterized in that The desensitizing the variable items related to the target user in the target log according to the business attribute information of the target user, the log desensitization policy and the pre-configured business authority information includes: Determining the service attribute information of the target user according to the user identifier of the target user; Determining target business sensitive data matching the target user according to the business attribute information of the target user and the pre-configured business authority information; and Based on the log desensitization strategy, desensitization processing is performed on the variable items of the target business sensitive data in the target log.

6. The method according to claim 1, characterized in that The step of determining the source of the target log in response to the log query request includes: In response to the log query request, determining a content format of the target log; and In response to determining that the content format of the target log complies with a predetermined format specification, the source of the target log is determined, wherein the predetermined format specification indicates that the log content includes a service name, a compilation path, a code version number, and the preset structure identifier.

7. The method according to claim 1, characterized in that When the target log is a business log, the log registration information further includes a group of character strings included in the target log and physical meaning description information of the group of character strings.

8. A device for log information processing, characterized in that: include: a receiving module configured to receive a log query request, wherein the log query request is used to indicate that a target user requests to query a target log generated by a running device in an environment of a trusted technology partner during a running process or a debugging process of a program code, wherein the target user is blocked from directly accessing the target log generated by the running device, and wherein the trusted technology partner provides the target user with a device for processing the log information; A first determination module is configured to determine, in response to the log query request, a source of the target log, wherein the target log is a log having a preset structured format generated by a preset log software development kit, and the preset structured format identifies variable items in the log by a preset structure identifier; a second determination module, configured to determine a log desensitization policy corresponding to the source of the target log, the log desensitization policy being determined based on log registration information associated with the source, the log registration information being used to indicate a physical meaning of a variable item in the target log, and being submitted through a log registration platform provided by the trusted technology partner to register content that can be revealed in logs generated by different sources; as well as The processing module is configured to desensitize the variable items related to the target user in the target log according to the business attribute information of the target user, the log desensitization policy and pre-configured business authority information, so as to provide the desensitized target log to the target user.

9. An electronic device, characterized in that: include: Memory and processor; The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: One or more computer instructions are stored thereon, wherein the one or more computer instructions are executed by a processor to implement the method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The method comprises one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the method according to any one of claims 1 to 7.

Images