Distributed cloud platform system and auditing method thereof

Abstract

The invention relates to a distributed cloud platform system and an auditing method thereof, the distributed cloud platform system comprises a system component, an auditing software development kit SDK and an SDK interceptor; the system component is used for receiving a request sent by a user to the distributed system and forwarding the request to the SDK interceptor; the SDK interceptor is used for acquiring attribute content corresponding to the request; and the auditing SDK is used for auditing the attribute content and storing an auditing result in a log. By intercepting and auditing the SDK through the SDK in the embodiment of the invention, all the system components in the distributed cloud platform system can be audited, and an auditing module does not need to be independently developed for each system component, so that the auditing efficiency of the distributed cloud platform system is higher, and the auditing can be uniformly managed.

Description

Technical Field

[0001] This application relates to the field of computer science, and more particularly to a distributed cloud platform system and its auditing method. Background Technology

[0002] For enterprise applications, which are typically distributed cloud platform systems composed of numerous components, auditing functionality is essential. Therefore, developing a separate auditing module for each component leads to non-standard development practices, hindering unified management, inconsistent audit definitions, and increasing development and maintenance costs. Furthermore, a system without comprehensive auditing capabilities cannot track and record user actions, making it impossible to review these actions if problems arise. Summary of the Invention

[0003] This application provides a distributed cloud platform system and its auditing method to address the problem in the prior art where each system component in a distributed cloud platform requires a separate auditing module.

[0004] In a first aspect, this application provides a distributed cloud platform system, which includes system components, an audit software development kit (SDK), and an SDK interceptor; wherein, the system components are used to receive requests sent by users to the distributed system and forward the requests to the SDK interceptor; the SDK interceptor is used to obtain attribute content corresponding to the request; and the audit SDK is used to audit the attribute content and save the audit results to a log.

[0005] Secondly, this application provides an auditing method based on the distributed cloud platform system in the first aspect. The method includes: the system component receiving a request sent by a user to the distributed system and forwarding the request to the SDK interceptor; the SDK interceptor obtaining attribute content corresponding to the request; and the auditing SDK auditing the attribute content and saving the audit results to a log.

[0006] Thirdly, this application provides an electronic device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus, wherein the processor is configured to execute the auditing method described in the second aspect of this application.

[0007] Fourthly, this application also provides a computer storage medium storing computer-executable instructions for executing the auditing method described in the second aspect of this application.

[0008] Compared with the prior art, the technical solution provided in this application has the following advantages: When it is necessary to audit the distributed cloud platform system, the user-initiated request is intercepted by the SDK interceptor after being sent to the corresponding system component in the distributed cloud platform system. The SDK interceptor then obtains the attribute content corresponding to the request, audits the attribute content, and saves the audit results. Thus, in this application embodiment, the SDK interception and audit SDK can be used to audit all system components in the distributed cloud platform system without developing a separate audit module for each system component. This makes the audit efficiency of the distributed cloud platform system higher and allows for unified management of the audit. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0010] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0012] Figure 1 This is a schematic diagram of a distributed cloud platform system provided in an embodiment of this application;

[0013] Figure 2 A flowchart of an auditing method based on a distributed cloud platform system is provided for embodiments of this application;

[0014] Figure 3 One of the optional flowcharts for an auditing method based on a distributed cloud platform system provided in this application embodiment;

[0015] Figure 4 A second optional flowchart of an auditing method based on a distributed cloud platform system provided in this application embodiment;

[0016] Figure 5 A third optional flowchart of an auditing method based on a distributed cloud platform system provided in this application embodiment;

[0017] Figure 6A flowchart illustrating a dynamic operation auditing method based on a distributed platform, as provided in this application embodiment;

[0018] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] The following disclosure provides numerous different embodiments or examples for implementing various structures of the invention. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of the invention. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0021] This application provides a distributed cloud platform system, such as... Figure 1 The distributed cloud platform system includes system components, an audit software development kit (SDK), and an SDK interceptor.

[0022] The system component is used to receive requests sent by users to the distributed system and forward the requests to the SDK interceptor.

[0023] In specific examples, the system components in this application embodiment can be functional modules of the distributed cloud platform system, such as user modules, permission modules, and storage modules. Furthermore, in this application embodiment, different requests correspond to different system components. For example, if the current request is used to query and delete stored information in the storage module, then the system component corresponding to this request is the storage module. Similarly, if the current request is used to add user information to the user module, then the system component corresponding to this request is the user module. The above system components and their corresponding requests are merely illustrative examples; in specific application scenarios, there are many more system components, and each system component has a corresponding request.

[0024] SDK interceptors are used to retrieve the attribute content corresponding to the request;

[0025] As can be seen, when auditing is required in a distributed cloud platform system, all user requests are first intercepted by the SDK interceptor. The SDK interceptor then obtains the attribute content corresponding to the request and forwards it to the audit SDK for auditing. In a specific example, if the current request is to add user information in the user module, after the request is sent to the user module, it is first intercepted by the SDK interceptor, which obtains the request's attribute content, such as the user information sending the request, the operation to be performed, and the content already performed, and then forwards this attribute content to the audit SDK for auditing.

[0026] The audit SDK is used to audit attribute content and save the audit results to the log.

[0027] In a specific example, auditing attribute content can refer to monitoring and recording attribute content, downloading or saving the monitored and recorded behavioral events to a log service, and then performing operations such as behavioral analysis, security analysis, resource change behavior tracking, and behavioral compliance.

[0028] As can be seen, in this embodiment of the application, when it is necessary to audit the distributed cloud platform system, the user-initiated request is sent to the corresponding system component in the distributed cloud platform system. The SDK interceptor intercepts the request, obtains the attribute content corresponding to the request, audits the attribute content, and saves the audit results. Thus, in this embodiment of the application, the SDK interception and auditing SDK can be used to audit all system components in the distributed cloud platform system without developing a separate audit module for each system component. This makes the auditing efficiency of the distributed cloud platform system higher and allows for unified management of the audit.

[0029] In an optional embodiment of this application, the SDK interceptor in this application embodiment is further used to obtain at least one of the following attribute contents corresponding to the request: request type, operator information, and operation content.

[0030] In a specific example, the request type could be query, delete, or add; the operator information refers to the attribute information of the user sending the request, such as user account information or the user's department information within the company; the operation content could be the specific content queried or deleted. If the request is for querying one's own salary information over a certain period, the corresponding system component could be the finance module. After the request is sent to the system component (finance module), the SDK interceptor will obtain the attribute content corresponding to the request. For example, user A sending the request wants to query their salary information from January to March, including the specific amounts of basic salary, performance-based salary, bonuses, and social insurance and housing fund contributions.

[0031] In an optional embodiment of this application, the audit SDK in this application embodiment is also used to monitor and record attribute content, and save the behavior events of performing monitoring and recording operations to the log based on the service identifier corresponding to the request.

[0032] It's important to note that when auditing is required in a distributed cloud platform system, the audit SDK configures a service identifier. This service identifier allows the system to identify the service corresponding to the saved audit results. In a specific example, this service identifier can be categorized, such as into several main categories with corresponding subcategories. This means that after obtaining the service identifier, it's clear which service the saved content belongs to, facilitating the switching of log data sources during subsequent log viewing. For instance, if a request is for querying salary information over a specific period, the SDK intercepts the request and obtains the corresponding attribute content: the sender (user A) requests salary information for January to March, including basic salary, performance-based salary, bonuses, and the specific amounts of social insurance and housing provident fund contributions. The audit SDK monitors and records the attribute content corresponding to this request—what information the user queried, the query results—and saves the queried content and results to the log, along with the corresponding service identifier, so that the log data source can be switched freely later.

[0033] In an optional embodiment of this application, the audit SDK in this application embodiment is further used to report abnormal events when there are abnormal events in the behavioral events.

[0034] As can be seen, the audit process can monitor and record the access and operation of system components corresponding to user requests. This record can include any operation requested by the user, such as a normal request to check one's own salary, or an abnormal request to check someone else's salary. For example, if user A sends a request to check user B's salary, checking someone else's salary is not allowed. Therefore, when a user checks their salary, the audit function can obtain the operator information (user A), request type (query), and operation content (checking user B's salary) corresponding to the request sent by user A through the SDK interceptor. By comparison, it can be determined that the operator information is different from the user information in the operation content. Therefore, the audit SDK obtains the abnormal event after auditing the attribute content of the request and reports the abnormal event.

[0035] In an optional embodiment of this application, the system component in this application is further configured to, in the event of audit failure, print the audit failure record to the log and execute the Uniform Resource Identifier (URI) corresponding to the request; or, in the event of successful audit, directly execute the Uniform Resource Identifier (URI) corresponding to the request.

[0036] It should be noted that, in this embodiment, audit failure refers to the audit SDK failing to perform the audit normally for some reason, meaning the audit process cannot be completed. Therefore, when an audit fails, the failure record can be printed to the log for subsequent analysis of the failed audit process, ensuring that the audit process can be completed successfully on subsequent attempts. Furthermore, regardless of whether the audit succeeds or fails, the URI corresponding to the request will still be executed; that is, the audit function of the distributed cloud platform system does not affect the actual request service of the system.

[0037] As can be seen, in this embodiment of the application, when a system component in the distributed cloud platform system needs to use operation audit content, it first applies to the audit service for a service identifier as a credential for component use. The audit service in the distributed cloud platform system provides an audit SDK. By introducing the SDK and configuring the relevant applications, each component in the system can easily pass user request information to the operation audit service. The audit SDK will organize and store all requests, thereby achieving unification, loose coupling, easy expansion, and flexible configuration.

[0038] The following will explain the auditing methods based on the aforementioned distributed cloud platform system, such as... Figure 2 As shown, the method includes:

[0039] Step 201: The system component receives the request sent by the user to the distributed system and forwards the request to the SDK interceptor;

[0040] In specific examples, the system components in this application embodiment can be functional modules of the distributed cloud platform system, such as user modules, permission modules, and storage modules. Furthermore, in this application embodiment, different requests correspond to different system components. For example, if the current request is used to query and delete stored information in the storage module, then the system component corresponding to this request is the storage module. Similarly, if the current request is used to add user information to the user module, then the system component corresponding to this request is the user module. The above system components and their corresponding requests are merely illustrative examples; in specific application scenarios, there are many more system components, and each system component has a corresponding request.

[0041] Step 202: The SDK interceptor obtains the attribute content corresponding to the request;

[0042] As can be seen, when auditing is required in a distributed cloud platform system, all user requests are first intercepted by the SDK interceptor. The SDK interceptor then obtains the attribute content corresponding to the request and forwards it to the audit SDK for auditing. In a specific example, if the current request is to add user information in the user module, after the request is sent to the user module, it is first intercepted by the SDK interceptor, which obtains the request's attribute content, such as the user information sending the request, the operation to be performed, and the content already performed, and then forwards this attribute content to the audit SDK for auditing.

[0043] Step 203: The audit SDK audits the attribute content and saves the audit results to the log.

[0044] Through steps 201 to 203 above, when auditing the distributed cloud platform system is required, the user-initiated request is sent to the corresponding system component in the distributed cloud platform system. The SDK interceptor intercepts the request, obtains the attribute content corresponding to the request, audits the attribute content, and saves the audit results. Thus, in this embodiment of the application, the SDK interception and auditing SDK can be used to audit all system components in the distributed cloud platform system without developing a separate audit module for each system component. This makes the auditing efficiency of the distributed cloud platform system higher and allows for unified management of the audit.

[0045] In optional embodiments of this application, the method by which the audit SDK audits attribute content in step 203 above is as follows: Figure 3 As shown, it may further include:

[0046] Step 301: The audit SDK monitors and records the attribute content;

[0047] Step 302: The audit SDK saves the behavior events of the monitoring and recording operations to the log based on the service identifier corresponding to the request.

[0048] It's important to note that when auditing is required in a distributed cloud platform system, the audit SDK configures a service identifier. This service identifier allows the system to identify the service corresponding to the saved audit results. In a specific example, this service identifier can be categorized, such as into several main categories with corresponding subcategories. This means that after obtaining the service identifier, it's clear which service the saved content belongs to, facilitating the switching of log data sources during subsequent log viewing. For instance, if a request is for querying salary information over a specific period, the SDK intercepts the request and obtains the corresponding attribute content: the sender (user A) requests salary information for January to March, including basic salary, performance-based salary, bonuses, and the specific amounts of social insurance and housing provident fund contributions. The audit SDK monitors and records the attribute content corresponding to this request—what information the user queried, the query results—and saves the queried content and results to the log, along with the corresponding service identifier, so that the log data source can be switched freely later.

[0049] In optional embodiments of this application, such as Figure 4 As shown, the method in this application embodiment may further include:

[0050] Step 401: If the audit SDK detects an abnormal event in the behavior event, it shall report the abnormal event.

[0051] As can be seen, the audit process can monitor and record the access and operation of system components corresponding to user requests. This record can include any operation requested by the user, such as a normal request to check one's own salary, or an abnormal request to check someone else's salary. For example, if user A sends a request to check user B's salary, checking someone else's salary is not allowed. Therefore, when a user checks their salary, the audit function can obtain the operator information (user A), request type (query), and operation content (checking user B's salary) corresponding to the request sent by user A through the SDK interceptor. By comparison, it can be determined that the operator information is different from the user information in the operation content. Therefore, the audit SDK obtains the abnormal event after auditing the attribute content of the request and reports the abnormal event.

[0052] In an optional embodiment of this application, the method by which the SDK interceptor obtains the attribute content corresponding to the request in step 202 above can be further described as follows: the SDK interceptor is used to obtain at least one of the following attribute contents corresponding to the request: request type, operator information, and operation content.

[0053] In a specific example, the request type could be query, delete, or add; the operator information refers to the attribute information of the user sending the request, such as user account information or the user's department information within the company; the operation content could be the specific content queried or deleted. If the request is for querying one's own salary information over a certain period, the corresponding system component could be the finance module. After the request is sent to the system component (finance module), the SDK interceptor will obtain the attribute content corresponding to the request. For example, user A sending the request wants to query their salary information from January to March, including the specific amounts of basic salary, performance-based salary, bonuses, and social insurance and housing fund contributions.

[0054] In optional embodiments of this application, such as Figure 5 As shown, the method in this application embodiment further includes:

[0055] Step 501: If the audit fails, the system component prints the audit failure record to the log and executes the Uniform Resource Identifier (URI) corresponding to the request; or if the audit succeeds, it directly executes the Uniform Resource Identifier (URI) corresponding to the request.

[0056] It should be noted that, in this embodiment, audit failure refers to the audit SDK failing to perform the audit normally for some reason, meaning the audit process cannot be completed. Therefore, when an audit fails, the failure record can be printed to the log for subsequent analysis of the failed audit process, ensuring that the audit process can be completed successfully on subsequent attempts. Furthermore, regardless of whether the audit succeeds or fails, the URI corresponding to the request will still be executed; that is, the audit function of the distributed cloud platform system does not affect the actual request service of the system.

[0057] The audit process in this application will be illustrated below with specific examples of its implementation. Figure 6 As shown, the steps of implementing a dynamic operation auditing method based on a distributed platform provided in this specific embodiment include:

[0058] Step 601: The distributed cloud platform system receives the user's request and forwards it to the corresponding component system through the request path.

[0059] It should be noted that the request path is the corresponding URL to be accessed. Each system has its own context path to distinguish them, for example: / dep / user / list.

[0060] Step 602: After receiving the request, the system component will intercept it through the SDK interceptor.

[0061] Step 603: The SDK interceptor forwards all requests to the audit service.

[0062] As can be seen, the SDK interceptor in this application embodiment is equivalent to the customer service provided by the system.

[0063] Step 604: After receiving the request, the audit service will process the relevant logic, such as the request type, operator information, operation content and other important information, and persist the data according to the storage source information configured in the component.

[0064] Step 605: After storing the operation information, the audit service will return it to the system components for reference.

[0065] Step 606: If the system component receives a failure result from the audit service, it logs the error and executes the relevant user-requested URI. If the audit service returns a success result, it also executes the user-requested URI accordingly. This concludes the operation audit process.

[0066] As can be seen, the audit service is used to collect user requests and analyze whether the behavior is appropriate, without affecting the actual business of the system. Therefore, the URI corresponding to the request will still be executed regardless of whether the audit service returns success or failure.

[0067] Through steps 601 to 606 above, in this embodiment of the application, the audit SDK can record all user operations, reducing the development and maintenance of audit logs for developers, and allowing for free switching of log data sources. Furthermore, all operations performed in the application system can be uniformly displayed under the operation audit menu, and the system can analyze the current user's access to and operation records of its own components, thereby achieving secure recording of important data and improving the auditing function of enterprise-level applications.

[0068] like Figure 7 As shown in the figure, this application provides an electronic device, including a processor 711, a communication interface 712, a memory 713, and a communication bus 714, wherein the processor 711, the communication interface 712, and the memory 713 communicate with each other through the communication bus 714.

[0069] Memory 713 is used to store computer programs;

[0070] In one embodiment of this application, when the processor 711 executes the program stored in the memory 713, it implements the auditing method provided in any of the foregoing method embodiments, and its function is similar, so it will not be described again here.

[0071] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the auditing method provided in any of the foregoing method embodiments.

[0072] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0073] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0074] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0075] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A distributed cloud platform system, characterized in that, The distributed cloud platform system includes system components, an audit software development kit (SDK), and an SDK interceptor. The system component is used to receive requests sent by users to the distributed system and forward the requests to the SDK interceptor; The SDK interceptor is used to obtain the attribute content corresponding to the request; The audit SDK is used to audit the attribute content and save the audit results to the log.

2. The system according to claim 1, characterized in that, The audit SDK is used to monitor and record the attribute content, and save the behavior events of performing monitoring and recording operations to the log based on the service identifier corresponding to the request.

3. The system according to claim 2, characterized in that, The audit SDK is also used to report the abnormal event if an abnormal event exists in the behavioral event.

4. The system according to claim 1, characterized in that, The SDK interceptor is used to obtain at least one of the following attribute contents corresponding to the request: request type, operator information, and operation content.

5. The system according to claim 1, characterized in that, The system component is configured to, in the event of an audit failure, print the audit failure record to the log and execute the Uniform Resource Identifier (URI) corresponding to the request; or, in the event of a successful audit, directly execute the Uniform Resource Identifier (URI) corresponding to the request.

6. An auditing method for a distributed cloud platform system based on any one of claims 1 to 5, characterized in that, The method includes: The system component receives a request sent by the user to the distributed system and forwards the request to the SDK interceptor; The SDK interceptor obtains the attribute content corresponding to the request; The audit SDK audits the attribute content and saves the audit results to the log.

7. The method according to claim 6, characterized in that, The audit SDK audits the attribute content, including: The audit SDK monitors and records the attribute content, and saves the behavior events of performing monitoring and recording operations to the log based on the service identifier corresponding to the request.

8. The method according to claim 7, characterized in that, The method further includes: If an abnormal event exists in the behavior event, the audit SDK shall report the abnormal event.

9. An electronic device, comprising: At least one communication interface; At least one bus connected to the at least one communication interface; At least one processor connected to the at least one bus; At least one memory connected to the at least one bus, wherein the processor is configured to execute the auditing method according to any one of claims 6 to 8.

10. A computer storage medium storing computer-executable instructions for performing the auditing method according to any one of claims 6 to 8.

Images