A risk identification method, apparatus, electronic device, and storage medium
By constructing a cross-application graph database to store the behavioral data relationships of multiple applications, the accuracy and speed issues of cross-application and cross-service business risk analysis in microservice architecture are solved, and high-precision risk identification is achieved.
Patent Information
- Application Number
- CN202310340554.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-31
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-03-31
AI Technical Summary
Existing technologies struggle to accurately perform cross-application and cross-service business risk analysis in microservice architectures, resulting in slow and inaccurate analysis.
By acquiring behavioral data of various target types from multiple applications, a cross-application graph database is constructed to store the relationships between these data, and this database is used for risk identification.
It enables high-precision business risk analysis across applications and services, avoiding the problem of slow analysis speed caused by excessive data, and improving the accuracy and efficiency of analysis.
Smart Images

Figure CN116455619B_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of communications, and more specifically, to a risk identification method, apparatus, electronic device, and storage medium in the field of communications. Background Technology
[0002] The security R&D lifecycle is a process that integrates security elements into all stages of R&D to achieve early detection of security risks and reduce the cost of risk resolution. Development Security Operations (DevSecOps) is a practice within the security R&D lifecycle that integrates security tools such as static code scanners, interactive instrumentation scanners, and request / response scanners with other R&D tools into the R&D pipeline, ensuring smooth operation. In popular microservice architectures, a single call chain often involves multiple application units and service interfaces, making it difficult for existing tools to accurately perform cross-application and cross-service business risk analysis. Therefore, there is an urgent need for a solution that can easily and accurately perform cross-application and cross-service business risk analysis.
[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this specification, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0004] This specification provides a risk identification method, apparatus, electronic device, and storage medium that can relatively accurately perform business risk analysis across applications and services.
[0005] Other features and advantages of this specification will become apparent from the following detailed description, or may be learned in part by practice of this specification.
[0006] According to one aspect of this specification, a risk identification method is provided, comprising: acquiring behavioral data of multiple target types from multiple applications; constructing a cross-application graph database based on the behavioral data of multiple target types from the multiple applications; wherein the cross-application graph database stores the relationships between the behavioral data of multiple target types from the multiple applications; and performing risk identification on a business to be identified based on the cross-application graph database; wherein the business to be identified includes at least one of the multiple applications.
[0007] According to another aspect of this specification, a risk identification device is provided, comprising: an acquisition module for acquiring behavioral data of multiple target types from multiple applications; a construction module for constructing a cross-application graph database based on the behavioral data of multiple target types from the multiple applications; wherein the cross-application graph database stores the relationships between the behavioral data of multiple target types from the multiple applications; and an identification module for performing risk identification on a business to be identified based on the cross-application graph database; wherein the business to be identified includes at least one of the multiple applications.
[0008] According to another aspect of this specification, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the risk identification method as described in the above embodiments.
[0009] According to one aspect of this specification, a computer-readable storage medium is provided that stores instructions which, when executed on a computer or processor, cause the computer or processor to perform the risk identification method as described in the above embodiments.
[0010] According to another aspect of this specification, a computer program product containing instructions is provided that, when the computer program product is run on a computer or processor, causes the computer or processor to perform the risk identification method as described in the above embodiments.
[0011] The risk identification method, risk identification device, computer-readable storage medium, electronic device, and computer program product provided in the embodiments of this specification have the following technical effects:
[0012] The exemplary embodiments of this specification provide a solution that constructs a cross-application graph database by acquiring behavioral data of various target types from multiple applications. Since this cross-application graph database stores the relationships between behavioral data of various target types from multiple applications, and the business to be identified includes at least one of multiple applications, risk identification of the business to be identified can be performed based on this cross-application graph database. By constructing a cross-application graph database, the solution provided by the exemplary embodiments of this specification possesses high-precision cross-application and cross-service analysis capabilities, thereby facilitating relatively accurate cross-application and cross-service business risk analysis. Furthermore, since the cross-application graph database stores the relationships between behavioral data of various target types from multiple applications without needing to store other data, accurate analysis can be achieved while avoiding the problem of slow analysis speed caused by excessive data storage.
[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description
[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of this specification. It is obvious that the drawings described below are merely some embodiments of this specification, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0015] Figure 1 This is a schematic flowchart illustrating a risk identification method provided in one embodiment of this specification.
[0016] Figure 2 This is a schematic flowchart illustrating one implementation of step 101 provided in an embodiment of this specification.
[0017] Figure 3 This is a schematic flowchart illustrating one implementation of step 1011 provided in an embodiment of this specification.
[0018] Figure 4 This is a schematic diagram illustrating the static program analysis capability provided in one embodiment of this specification.
[0019] Figure 5 This is a schematic diagram illustrating the dynamic program analysis capability provided in one embodiment of this specification.
[0020] Figure 6 This is a schematic flowchart illustrating one implementation of step 1013 provided in an embodiment of this specification.
[0021] Figure 7 This is a schematic flowchart illustrating one implementation of step 102 provided in an embodiment of this specification.
[0022] Figure 8 This is a schematic diagram of an in->out link and an in->sink link provided in an embodiment of this specification.
[0023] Figure 9 This is a schematic diagram illustrating the association between app1 and app3 as provided in one embodiment of this specification.
[0024] Figure 10 This is a schematic flowchart illustrating one implementation of step 103 provided in an embodiment of this specification.
[0025] Figure 11 This is a schematic diagram of a transaction payment scenario provided in one embodiment of this specification.
[0026] Figure 12 This is a diagram illustrating the overall technical architecture of a risk identification method provided in one embodiment of this specification.
[0027] Figure 13 This is a schematic diagram of a purely manual evaluation mode provided in one embodiment of this specification.
[0028] Figure 14 This is a schematic diagram of a purely automated evaluation mode provided in one embodiment of this specification.
[0029] Figure 15 This is a schematic diagram of an automated risk assessment mode provided in one embodiment of this specification.
[0030] Figure 16 This is a schematic diagram of an automated scenario verification mode provided in one embodiment of this specification.
[0031] Figure 17 This is a schematic diagram of the structure of a risk identification device provided in one embodiment of this specification.
[0032] Figure 18 The schematic diagram illustrates the structure of an electronic device according to an exemplary embodiment of this specification. Detailed Implementation
[0033] To make the objectives, technical solutions, and advantages of this specification clearer, the embodiments of this specification will be described in further detail below with reference to the accompanying drawings.
[0034] In the following description, when referring to the accompanying drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.
[0035] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this specification more comprehensive and complete, and to fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of the embodiments described herein. However, those skilled in the art will recognize that the technical solutions described herein may be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., may be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this specification.
[0036] Furthermore, the accompanying drawings are merely illustrative diagrams of this specification and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0037] The essence of risk assessment is the process of disclosing risks using security knowledge, based on a thorough understanding of the business. After reviewing and analyzing numerous risk assessment cases, it was found that the key factor affecting efficiency is either insufficient understanding of the "business" by security engineers or inadequate security knowledge by development engineers. "Business" refers to a broad concept, encompassing not only commonly understood business aspects (such as login and payment processes) but also the system architecture supporting the business, as well as the running application processes and source code; and not only commonly understood business aspects (such as login processes) but also security aspects (whether security defense components are integrated). Security engineers need a comprehensive understanding of the "business" to identify security risks based on their existing security knowledge. Conversely, development engineers often have a strong understanding of the business but lack sufficient security knowledge to identify existing risks. Beyond risk assessment, many other scenarios require security engineers to have the ability to quickly and clearly understand the "business." For example, in risk emergency response and risk governance scenarios, security engineers need to quickly identify the business processes, systems, and code requiring modification based on emergency / governance standards, with high requirements for accuracy, implementation efficiency, and cost.
[0038] The Security Development Lifecycle (SDL) is a software development process that helps developers reduce costs while building secure software. First proposed and successfully implemented by Microsoft, it is now widely adopted and popular in the industry. A concept that runs parallel to SDL is DevSecOps. DevSecOps originated from DevOps, just as SDL originated from the Development Lifecycle (DL). The core principles of DevSecOps are no different from SDL, but it places greater emphasis on the tooling and pipelined nature of the security process.
[0039] Due to the high cost of fully implementing SDL processes, most enterprises tend to prioritize building lighter-weight DevSecOps processes. Implementing DevSecOps processes can significantly improve security levels, but it also has some bottlenecks. DevSecOps is a set of security development lifecycle practices that integrate security tools such as static code scanners, interactive instrumentation scanners, and request / response scanners with other development tools into the development pipeline, ensuring smooth operation. However, when facing the currently popular microservice architecture, some DevSecOps tools struggle to accurately perform cross-application and cross-service business risk analysis, as a single call chain often involves multiple application units and service interfaces.
[0040] Based on this, to address the aforementioned technical problem of accurately performing cross-application and cross-service business risk analysis, embodiments of this specification provide a risk identification method, apparatus, electronic device, and storage medium. The risk identification method in the embodiments of this specification will be described in detail below:
[0041] The risk identification method described in this specification can be applied to electronic devices with risk identification functions, which can be servers. In specific implementations, the risk identification function can be implemented by one server or by multiple servers working together.
[0042] In an exemplary embodiment, a schematic flowchart of the risk identification method can be found. Figure 1 ,include:
[0043] Step 101: Obtain behavioral data for various target types from multiple applications.
[0044] Step 102: Construct a cross-application graph database based on the behavioral data of various target types of the above-mentioned applications; wherein, the cross-application graph database stores the association relationships between the behavioral data of various target types of the above-mentioned applications.
[0045] Step 103: Based on the cross-application graph database mentioned above, perform risk identification on the business to be identified; wherein the business to be identified includes at least one of the above multiple applications.
[0046] exist Figure 1In the illustrated embodiment, a cross-application graph database is constructed by acquiring behavioral data of various target types from multiple applications. Since this cross-application graph database stores the relationships between behavioral data of various target types from multiple applications, and the business to be identified includes at least one of multiple applications, risk identification of the business to be identified can be performed based on this cross-application graph database. By constructing a cross-application graph database, the solution provided by the exemplary embodiments of this specification possesses high-precision cross-application and cross-service analysis capabilities, thereby facilitating relatively accurate cross-application and cross-service business risk analysis. Furthermore, since the cross-application graph database stores the relationships between behavioral data of various target types from multiple applications without storing other data, accurate analysis can be achieved while avoiding the problem of slow analysis speed caused by excessive data storage.
[0047] The following is about Figure 1 The specific implementation methods of each step in the illustrated embodiments will be explained below:
[0048] In step 101, the electronic device can collect behavioral data of various target types from multiple applications. These target types can be risk identification-related, and these risk identification-related types can be pre-determined by security experts and / or R&D experts based on actual needs. The aforementioned applications can be deployed on a server to support certain business functions, thereby implementing those functions.
[0049] In exemplary embodiments, the various target types include: application-based behavior types, business behavior types, security risk behavior types, and security defense behavior types. The target types in this set are described below:
[0050] The aforementioned basic application behavior classes are the fundamental behavior classes of the application. These basic behavior classes can further include: sending and receiving requests, messages, returning cached data, returning data to the database, reading and writing files, writing logs, etc. The aforementioned requests can include, for example, HTTP requests and PRC requests.
[0051] The aforementioned business behavior classes refer to the application's business behavior classes. These business behavior classes can further include: login behavior, registration behavior, payment behavior, transfer behavior, red envelope behavior, marketing behavior, etc.
[0052] The aforementioned security risk behavior categories refer to the risky behaviors present in the application. These categories can be further included in the following ways: system command execution behavior, sensitive interface call behavior, sensitive data reading behavior, etc.
[0053] The aforementioned security defense behaviors refer to proactive security defense behaviors. These behaviors can be further included in the following categories: authentication behaviors, secondary identity verification behaviors, authorization behaviors, encryption behaviors, and security detection behaviors.
[0054] In an exemplary embodiment, process data generated during application development, such as documents, product pages, code, and process data, can be acquired. These process data can be analyzed using technologies such as Natural Language Processing (NLP), image recognition, program analysis, and machine learning to extract business information in a structured manner and obtain behavioral data of the aforementioned target types.
[0055] In an exemplary embodiment, the implementation method for obtaining behavioral data of various target types from multiple applications in step 101 above can be found in [reference needed]. Figure 2 ,include:
[0056] Step 1011: Perform static program analysis on the above applications respectively to obtain the static program analysis results of each application.
[0057] Step 1012: Perform dynamic program analysis on the above applications respectively to obtain the dynamic program analysis results of each application.
[0058] Step 1013: Based on the static and dynamic program analysis results of the above applications, perform business abstraction modeling on the above applications to obtain behavioral data of various target types for each of the above applications.
[0059] exist Figure 2 In the illustrated embodiment, by performing static program analysis and dynamic program analysis, the results of static program analysis and dynamic program analysis can complement each other, thereby facilitating the more accurate and comprehensive acquisition of behavioral data of various target types from multiple applications.
[0060] The following is about Figure 2 The implementation methods of each step in the illustrated embodiments will be described in detail below:
[0061] In step 1011, static program analysis tools can be used to perform static program analysis on multiple applications separately, obtaining the static program analysis results for each application. These tools can perform basic tasks such as intermediate code generation and instruction simplification, and construct method call graphs and program dependency graphs based on high-precision pointer analysis techniques. The method call graphs and program dependency graphs enable core program analysis algorithms such as data flow analysis, taint analysis, Structured Query Language (SQL) analysis, source code analysis, and configuration analysis. By developing corresponding data flow and call flow analysis rules, information such as data flow, taint flow, call flow, program metadata, and configuration data from individual applications can be collected. This collected information can then be used as the static program analysis result for that single application.
[0062] In an exemplary embodiment, the implementation of step 1011 can be found in [reference needed]. Figure 3 ,include:
[0063] Step 301: Determine the development frameworks corresponding to the above applications.
[0064] Step 302: Perform framework analysis on the development frameworks corresponding to the above applications to obtain the initialization analysis results for each of the above applications.
[0065] Step 303: Analyze the initialization analysis results of the above applications according to the preset flow analysis rules to obtain the static program analysis results of each of the above applications.
[0066] exist Figure 3 In the illustrated embodiment, by performing framework analysis on the development frameworks corresponding to multiple applications, it is equivalent to performing framework modeling on multiple development frameworks. This allows the static program analysis tool to adapt to different development frameworks, which is beneficial to improving the accuracy and speed of subsequent analysis.
[0067] The following is about Figure 3 The implementation methods of each step in the illustrated embodiment will be described in detail below:
[0068] In step 301, the development frameworks used by different applications may be the same or different. The development framework may include: Spring framework, Inversion of Control (IOC) framework, etc.
[0069] Data Access Object (DAO) frameworks, MyBatis framework, etc.
[0070] In step 302, framework analysis can be performed on the development frameworks corresponding to multiple applications to obtain initialization analysis results for each application. Framework analysis can be understood as initialization analysis or framework modeling. For example, performing framework analysis on an IOC framework can be understood as performing IOC modeling, and performing framework analysis on a DAO framework can be understood as performing DAO modeling. Framework modeling can be understood as the rules for initialization analysis, and the results of framework modeling can be the initialization analysis results. In this step, by performing initialization analysis on the application programs, some basic business characteristics of the development framework can be obtained, such as permissions and authentication, thus yielding initialization analysis results for each application.
[0071] In step 303, the initialization analysis results corresponding to the above-mentioned multiple applications can be analyzed according to preset flow analysis rules to obtain the static program analysis results of each of the above-mentioned applications. The flow analysis rules can be set according to actual needs. Through flow analysis rules, information such as data flow, taint flow, call flow, program metadata, and configuration data of a single application can be collected. Since behavior is manifested at the program level as different flows, the flow analysis rules can determine which target type a behavior belongs to, such as whether it is an application basic behavior class or a business behavior class. The above-mentioned flow analysis rules can also include primary classification rules and secondary classification rules. For example, the primary classification rule is a rule to determine whether a behavior belongs to the application basic behavior class, and the secondary classification rule is a rule to identify whether the application has sent requests such as Hypertext Transfer Protocol (HTTP) or Remote Procedure Call (RPC). For example, if an underlying call to send an HTTP request is detected, it is considered that there is an HTTP request behavior.
[0072] In an exemplary embodiment, a structure such as Figure 4 The static program analysis capability shown allows for the use of this capability to perform static program analysis and obtain the results. The static program analysis tool in this embodiment can possess... Figure 4 The static program analysis capability shown. Figure 4 In this framework, static program analysis capabilities are implemented through the functionalities of the base layer, core layer, adaptation layer, and data layer. The base layer handles fundamental tasks such as intermediate code generation and instruction simplification, and constructs method call graphs and program dependency graphs based on high-precision pointer analysis techniques. The core layer uses method call graphs and program dependency graphs to implement core algorithms for program analysis, including data flow analysis, taint flow analysis, SQL analysis, source code analysis, and configuration analysis. The adaptation layer is used for framework modeling of the development frameworks corresponding to multiple applications, such as... Figure 4 The modeling includes IOC and DAO. Dependency modeling and permission modeling go a step further, essentially modeling not only the framework and middleware but also some basic capabilities of the business layer, such as permissions. Permissions can be understood as the authentication and access control system that every application has. Because the permission system is usually relatively fixed within a company, this part can also be modeled, reducing the cost of subsequent analysis. The data layer is used to collect information such as data flow, taint flow, call flow, program metadata, and configuration data from a single application based on the output of the adaptation layer, i.e., the initialization analysis results and preset flow analysis rules.
[0073] In step 1012, dynamic program analysis tools can be used to perform dynamic program analysis on multiple applications separately, obtaining the dynamic program analysis results for each application. It is understood that the advantage of static program analysis technology is that it can analyze the important properties of a program without running the program or relying on sufficient traffic, but it inevitably has a certain degree of false negatives and false negatives. Therefore, this embodiment also performs dynamic program analysis on multiple applications separately.
[0074] In an exemplary embodiment, a structure such as Figure 5 The dynamic program analysis capability shown allows for the use of this capability to perform dynamic program analysis and obtain the analysis results. The dynamic program analysis tool in this embodiment can possess... Figure 5 The dynamic program analysis capability shown. Figure 5 In this implementation, Java agent technology enables unified Java Virtual Machine (JVM) bytecode instrumentation capabilities and provides a plugin mechanism. At the upper layer, interactive application security testing (IAST), runtime application self-protection (RASP), and the dynamic data acquisition component RDATA can be implemented. Based on this component, trace information, call stacks, environment information, and business data can be collected before key method calls, upon return, and during exceptions during program runtime. In this embodiment, the data collected by the aforementioned dynamic data acquisition component can be used as the result of dynamic program analysis.
[0075] In step 1013, based on the static and dynamic program analysis results of each application, business abstraction modeling is performed on each application to obtain behavioral data of various target types for each application. In other words, after collecting the dynamic and static program analysis results of each application, business abstraction modeling can be performed based on these results. In this embodiment, business abstraction modeling can be primarily based on the data flow and call flow in the dynamic and static program analysis results. According to the characteristics of call flow and data flow, using combined link data with call flow as the main component to identify scenarios can ensure a high recall rate, while using combined link data with data flow as the main component to identify risks can ensure a high accuracy rate. Business abstraction modeling rules can include the following four types:
[0076] Basic behavior classes: The basic behaviors of the application, such as sending and receiving requests.
[0077] Business behavior category: Application business behaviors, such as implementing login and registration functions.
[0078] Security risk behaviors: Applications exhibiting risky behaviors, such as executing system commands.
[0079] Security defense behavior category: Actions that apply proactive security defenses, such as authentication and authorization.
[0080] In an exemplary embodiment, the static program analysis results and dynamic program analysis results mentioned above include code comments. The implementation method of step 1013 can be found in [reference needed]. Figure 6 ,include:
[0081] Step 601: Segment the above code comments to obtain several keywords.
[0082] Step 602: Based on the above keywords and the preset mapping library, determine the target keywords corresponding to the risk types and / or scenarios.
[0083] Step 603: Based on the above target keywords, perform business abstract modeling on the above multiple applications to obtain behavioral data of various target types for each of the above multiple applications.
[0084] It should be noted that for a system hosted by a microservice architecture, each service interface can be considered as a minimum unit of business behavior. Dynamic and static program analysis can automatically extract microservice interfaces from the program, extracting information including interface-related code comments, class / enumeration / method / variable names, traffic data, and other features strongly related to business semantics. In this embodiment, word segmentation technology is mainly used to segment interface comments (i.e., code comments). After word segmentation, keyword matching is combined for business abstraction modeling, which helps improve the accuracy of business abstraction modeling.
[0085] The following is about Figure 6 The implementation methods of each step in the illustrated embodiment will be described in detail below:
[0086] In step 601, Natural Language Processing (NLP) segmentation technology can be used to segment the code comments to obtain segmentation results. These segmentation results include several keywords derived from the segmentation.
[0087] In step 602, the preset mapping library can store mapping relationships between keywords and scenarios, or between keywords and risk types, or between keywords, risk types, and scenarios. Therefore, based on the keywords obtained from word segmentation and the preset mapping library, target keywords corresponding to risk types and / or scenarios can be determined. It is understood that each application can have corresponding code comments, thus allowing for the generation of target keywords for multiple applications through keyword matching.
[0088] Understandably, segmenting code comments may yield many keywords, such as a keyword list. However, not all of these keywords will correspond to specific risk types and / or scenarios. Therefore, matching target keywords using a mapping library is crucial; the code corresponding to these target keywords is likely of interest to security experts.
[0089] In step 603, business abstraction modeling can be performed on the multiple applications based on their respective target keywords, resulting in behavioral data for various target types for each application. The target keywords of an application can be used to describe the risk type and / or scenario corresponding to that application. Specifically, performing business abstraction modeling on an application can be understood as establishing a correspondence between the application's target keywords and business scenarios and / or business risks, so that keywords can be mapped to corresponding business scenarios and / or business risks. The behavioral data for multiple target types of an application can be understood as the correspondence data between the target keywords corresponding to the various target types of the application and the business scenarios and / or business risks.
[0090] In an exemplary embodiment, step 603 can be implemented by: obtaining confirmation or supplementary information from security experts regarding the target keyword; and performing business abstraction modeling based on the confirmation or supplementary information from security experts regarding the target keyword to obtain behavioral data for various target types of the multiple applications. In this embodiment, after obtaining the target keyword, security experts can confirm or supplement the target keyword and its corresponding business scenario and / or business risk. For example, they can confirm whether the correspondence between the target keyword and its corresponding business scenario and / or business risk is accurate, such as whether the target keyword truly corresponds to the corresponding business scenario and / or business risk. When confirmation information from security experts regarding the target keyword is obtained, it indicates that the security experts have no doubt about the correspondence between the target keyword and the business scenario and / or business risk. Therefore, business abstraction modeling can be performed based on the target keyword and its corresponding business scenario and / or business risk to obtain behavioral data for various target types of the multiple applications. The supplementary information from security experts can be understood as follows: after matching a target keyword, the security expert supplements the business scenario and / or business risk corresponding to that target keyword, such as adding other scenario markers or risk markers. When supplementary information about target keywords is obtained from security experts, it indicates that the security experts have supplemented the correspondence between target keywords and business scenarios and / or business risks. Therefore, business abstraction modeling can be carried out by combining the supplementary information about target keywords from security experts, and behavioral data of various target types of the above-mentioned applications can be obtained.
[0091] In this embodiment, further incorporating expert experience can more effectively achieve business abstraction modeling for microservice architecture applications, thereby improving the accuracy of abstraction modeling.
[0092] In step 102, a cross-application graph database is constructed based on the behavioral data of various target types from multiple applications. This cross-application graph database stores the relationships between the behavioral data of various target types from multiple applications.
[0093] For example, after obtaining behavioral data of various target types from multiple applications, this data can be collected into an offline database, and a cross-application graph database can be built through offline tasks. The cross-application graph database can include two types: a method call graph database and a data flow graph database. It should be noted that this embodiment only uses the aforementioned offline database and offline tasks as examples; in specific implementations, online databases and online tasks can also be used.
[0094] In an exemplary embodiment, the implementation of step 102 can be found in [reference needed]. Figure 7 include:
[0095] Step 1021: Based on the behavioral data of various target types from the above applications, determine the input nodes, output nodes, and data consumption nodes for each of the above applications.
[0096] Step 1022: Based on the input nodes, output nodes, and data consumption nodes of the above-mentioned multiple applications, construct the first link and the second link for each of the above-mentioned multiple applications; wherein, the first link is the link between the input node and the output node, and the second link is the link between the input node and the data consumption node.
[0097] Step 1023: Construct a cross-application graph database based on the first and second links of each of the above applications.
[0098] The following is about Figure 7 The implementation methods of each step in the illustrated embodiments will be described in detail below:
[0099] In step 1021, the input (in) node, output (out) node, and data consumption (sink) node of each application can be determined based on the behavioral data of various target types for each application. These three types of nodes are explained below:
[0100] The in node refers to all data entry points for the application, such as network (HTTP, RPC, messages, relational database cache), file reading, and database querying.
[0101] out nodes: These are the application's data outputs, such as networks, files, and databases.
[0102] Sink node: This refers to all data consumption nodes of the application, such as log printing and command execution.
[0103] In step 1022, based on the respective in nodes, out nodes, and sink nodes of multiple applications, a first link and a second link are constructed for each application. The first link is the in->out link, and the second link is the in->sink link. For example, see... Figure 8 , Figure 8 This refers to the in->out and in->sink links constructed for a specific application. In the diagram, the inner appedge represents the edge between nodes. Specifically...
[0104] The edge between the in node and the out node (in-out edge) is the edge from the data entry point to the data exit point. The edge between the in node and the sink node (in-sink edge) is the edge from the data entry point to the application behavior. Multiple target types of behavioral data for the application can be stored on the in-out edge and the in-sink edge. For example, the in-out edge can store path data from the in node to the out node, which is related to behavioral data of a certain target type of the application. In this embodiment, the in-out edge and the in-sink edge do not need to store the full amount of application data, but rather store behavioral data of multiple target types of interest for risk identification, thus reducing the amount of data storage.
[0105] In step 1023, a cross-application graph database can be constructed based on the association between the first and second links of each of the multiple applications.
[0106] In an exemplary embodiment, the implementation of step 1023 may include: identifying output nodes and output nodes of the same type among the nodes on the first and second links of the plurality of applications; and constructing a cross-application graph database by connecting the output nodes and output nodes of the same type.
[0107] In this embodiment, both the in and out nodes contain an association id field for cross-application association. In / out nodes of the same type have the same association id format. For example, the association id format for RPC type in / out nodes is:
[0108] nterface.methodName(parameterType):uniqueId:parameterIndex,
[0109] The association ID format for DATABASE type in / out nodes is: database:table_name. By connecting out nodes and in nodes with the same association ID format (i.e., output nodes of the same type as mentioned above), a cross-application graph database can be constructed. This will create an additional cross-application edge, such as... Figure 9 The out-in edge shown is the edge that flows from the data output of app1 to the data input of app3. The out-in edge connects app1 and app3.
[0110] In step 103, risk identification is performed on the service to be identified based on the aforementioned cross-application graph database; the service to be identified includes at least one of multiple applications. For example, the service to be identified may involve more than one of the aforementioned multiple applications, such as two or four applications, etc. This embodiment does not specifically limit this.
[0111] In an exemplary embodiment, the implementation of step 103 can be found in [reference needed]. Figure 10 ,include:
[0112] Step 1031: Determine the starting input node of the service to be identified. That is, determine the starting "in" node of the service to be identified. The starting "in" node is generally a common node, such as an externally provided HTTP interface.
[0113] Step 1032: Determine the target data consumption node among the data consumption nodes in the above cross-application graph database.
[0114] For example, all sink nodes existing across application graph databases can be used as target data consumer nodes. Alternatively, filtering rules can be set to filter sink nodes across application graph databases, resulting in filtered sink nodes. These filtered sink nodes can then be identified as target sink nodes. For instance, each sink node can have corresponding attributes. Suppose the sink node in app1 has the attribute "logging," the sink node in app2 has the attribute "writing files," and the sink node in app3 has the attribute "login." If the current requirement is to identify whether app1 has a login scenario, the filtering condition can be set to whether it has the login attribute, thus identifying the sink node in app3 as the target sink node.
[0115] Step 1033: By traversing the path between the starting input node and the target data consumption node in the cross-application graph database, determine the business scenario and / or risk information of the business to be identified; wherein, the risk information is the final risk type or the estimated potential risk type.
[0116] For example, all reachable paths can be calculated using graph traversal statements, that is, the paths between the starting `in` node and the target `sink` node mentioned above. Below is an example of a Gremlin graph traversal statement:
[0117] gV().hasLabel('in_node').has('app','openhome').repeat(outE().inV()).until(ha sLabel("sink_node")).path()
[0118] Once the paths between the starting `in` node and the target `sink` node are obtained, the business scenario and / or risk information of the business to be identified can be determined based on these paths and preset scenario identification rules and / or risk determination rules. For example, if three paths are obtained and all three paths satisfy the scenario identification rules for scenario 1, then these three paths can be considered to correspond to scenario 1, i.e., the business scenario of the business to be identified is determined to be scenario 1. Similarly, if one path is obtained and this path satisfies the risk identification rules for risk type 1, then this path can be considered to correspond to risk type 1, i.e., the risk type of the business to be identified is determined to be risk type 1.
[0119] For example, a business scenario can have multiple constituent features, meaning a business scenario includes one or more sub-business behavior scenarios. Some business scenarios can be identified simply by examining one sub-business behavior scenario. For instance, the business scenario of merchant coupon issuance includes three sub-business behavior scenarios: creating coupons, configuring coupons, and issuing coupons. The decisive factor is issuing coupons. Therefore, by determining whether the sub-behavior scenario of issuing coupons exists, the existence of the merchant coupon issuance scenario can be determined. In other words, the scenario identification rule for the merchant coupon issuance scenario can be: does the sub-behavior scenario of issuing coupons exist?
[0120] For example, another type of business scenario requires determining whether multiple sub-behavioral scenarios exist simultaneously and their temporal relationship to ascertain the existence of that specific business scenario. For instance, in a transaction payment scenario, it's necessary to accurately identify... Figure 11 The system identifies four sub-scenarios (i.e., four paths) and their temporal relationships to accurately determine the existence of transaction payment scenarios. In other words, the scenario identification rule for transaction payment scenarios can be: existing sequentially in time: transaction creation path, transaction rendering path, transaction payment path, and result polling path.
[0121] For example, when the risk information is the final risk type, it indicates that the risk assessment platform has a high accuracy rate in identifying that risk type and can directly identify the final risk type, automatically completing the risk assessment. When the risk information is an estimated potential risk type, it indicates that the risk assessment platform has a lower accuracy rate in identifying that risk type and can only estimate the potential risk type, i.e., the type of risk that may occur, which can then be confirmed by security experts.
[0122] In an exemplary embodiment, when the business scenario and / or risk information of the business to be identified are determined to be the business scenario for identifying the business to be identified, the above-mentioned risk identification of the business to be identified includes:
[0123] Input the above business scenarios into a preset risk assessment model to output the types of potential risks present in the above business scenarios; output the types of potential risks present in the above business scenarios so that security experts can confirm the types of risks present in the above business scenarios based on the types of potential risks.
[0124] The pre-defined risk assessment model can include three levels: Level 1 is the business scenario, Level 2 is the potential risk types within that scenario, and Level 3 is the corresponding solutions for each risk type. These three levels have a one-to-one mapping relationship. When the risk assessment platform cannot directly output risk information, it can input its output business scenario into the risk assessment model. The model can then output the potential risk types present in that scenario. The risk assessment platform can then provide these potential risk types to security experts, allowing them to determine the final risk type based on the output.
[0125] In an exemplary embodiment, when the above determination of the business scenario and / or risk information of the business to be identified is the risk information of the business to be identified, and the risk information is the estimated potential risk type, the above risk identification of the business to be identified includes: outputting the business scenario and the estimated potential risk type, so that security experts can confirm the risk type existing in the business scenario based on the potential risk type.
[0126] In this embodiment, the risk assessment platform can determine the business scenario of the business to be identified and the estimated potential risk types, but it is difficult to determine the final risk type. Therefore, the risk assessment platform can output the business scenario and estimated potential risk types of the business to be identified to security experts for reference, so that security experts can confirm the risk types existing in the business scenario based on the potential risk types, and this risk type is the final risk type.
[0127] In an exemplary embodiment, the overall technical architecture diagram of the risk assessment platform implementing the risk identification method can be found in [reference needed]. Figure 12 During the coding and testing phases of R&D, the Security Development Lifecycle (SDL) platform can monitor code merging and phase progress messages from the R&D platform, subsequently triggering dynamic and static program analysis on the distributed scanning cluster and aspect modules on the business servers. The results of the dynamic and static program analysis can be written to a graph database through an offline data cleaning channel to build a cross-application graph database. Figure 12In this framework, Object Storage Service (OSS) stores data fed back from the distributed scanning cluster, i.e., static program analysis results. Log Service (SLS) stores data fed back from the business servers, i.e., dynamic program analysis results. Open Data Processing Service (ODPS) integrates and cleans data from OSS and SLS, then feeds the integrated and cleaned data into a graph database to build a cross-application graph database. After graph analysis and computation, the graph computation results are fed back to the SDL platform, representing the business scenarios and / or risk information of the business to be identified. The SDL platform can provide basic scenario / risk assessment models to assist security experts in risk assessment, meeting the most basic needs of purely manual risk assessment, and can also adapt to the assessment needs of different security teams and security domains through customized configuration of scenario / risk assessment models.
[0128] Based on whether automation tools (i.e., the aforementioned risk assessment platform) are introduced in the risk assessment process, and the ability of automation to identify different scenarios / risks, this embodiment provides four risk assessment modes: purely manual assessment, purely automated assessment, automated risk pre-assessment, and automated scenario confirmation. These are described below:
[0129] A diagram illustrating the purely manual evaluation model can be found here. Figure 13 Purely manual assessment, which is an assessment mode without the participation of automated tools, can fully meet the requirements of the universality and configurability of the risk assessment process. Security teams can configure customized risk assessment models and set assessment roles (security engineer / business party) for each assessment action to meet the risk assessment process needs of different security fields.
[0130] A diagram illustrating the fully automated evaluation model can be found here. Figure 14 Purely automated assessment can be understood as follows: if an automated tool has a high accuracy rate in identifying a certain type of risk, it can directly generate risk items, i.e., the final risk type, and automatically complete the risk assessment. While reporting risk information, the automated tool can also report business scenarios, supplementing the business scenario and the risk assessment process, ultimately determining the type of risk present in a specific business scenario.
[0131] A diagram illustrating the automated risk assessment model can be found here. Figure 15In this mode, automated tools can only perform risk prediction, that is, reveal potential risk items and report the necessary information for manual risk confirmation. Risk confirmation items, i.e., the aforementioned potential risk types, are then generated and confirmed manually. While reporting risk prediction information, automated tools can also report business scenarios to ultimately determine the types of risks present in a specific business scenario.
[0132] A diagram illustrating the automated scene confirmation mode can be found here. Figure 16 In this mode, automation can only confirm the business scenario, but cannot provide information about the potential risks in this scenario. At this time, the automation scenario confirmation is completed and the corresponding risk confirmation items are automatically generated according to the risk assessment model, and the subsequent risk confirmation process is completed manually.
[0133] This embodiment focuses on efficiently achieving business understanding by decomposing the risk assessment process. It integrates business and security knowledge through graph databases and graph computing technologies, and leverages platform engineering collaboration tools and expert experience to comprehensively improve precision and recall rates. The graph database enables data flow and call flow association across multiple applications and projects, thus providing high-precision cross-application and cross-service analysis capabilities. A cross-application graph database design at the business abstraction level is proposed, avoiding the exponential explosion problem of excessive traversal caused by too many cross-application graph storage nodes in traditional program analysis.
[0134] By using business abstraction modeling technology to understand the business semantics of programs, we have the basic capability to monitor risks that are strongly related to business semantics.
[0135] Figure 17 This is a schematic diagram of the structure of a risk identification device provided in an embodiment of this application.
[0136] For example, such as Figure 17 As shown, the device includes: an acquisition module 1701, used to acquire behavioral data of multiple target types from multiple applications; a construction module 1702, used to construct a cross-application graph database based on the behavioral data of multiple target types from the multiple applications; wherein the cross-application graph database stores the relationships between the behavioral data of multiple target types from the multiple applications; and an identification module 1703, used to perform risk identification on the business to be identified based on the cross-application graph database; wherein the business to be identified includes at least one of the multiple applications.
[0137] In one possible implementation, the construction module 1702 is specifically used to: determine the input nodes, output nodes, and data consumption nodes of the multiple applications based on the behavioral data of various target types of the multiple applications; construct the first link and the second link of the multiple applications based on the input nodes, output nodes, and data consumption nodes of the multiple applications; wherein the first link is the link between the input node and the output node, and the second link is the link between the input node and the data consumption node; and construct a cross-application graph database based on the first link and the second link of the multiple applications.
[0138] In one possible implementation, the construction module 1702 constructs a cross-application graph database based on the first and second links of the aforementioned multiple applications, including: identifying output nodes and output nodes of the same type among the nodes on the first and second links of the aforementioned multiple applications; and constructing the cross-application graph database by connecting the output nodes and output nodes of the same type.
[0139] In one possible implementation, the identification module 1703 is specifically used to: determine the starting input node of the above-mentioned business to be identified; determine the target data consumption node among the data consumption nodes in the above-mentioned cross-application graph database; and determine the business scenario and / or risk information of the above-mentioned business to be identified by traversing the path between the above-mentioned starting input node and the above-mentioned target data consumption node in the above-mentioned cross-application graph database; wherein the above-mentioned risk information is the final risk type or the estimated potential risk type.
[0140] In one possible implementation, when the business scenario and / or risk information of the business to be identified is determined to be the business scenario of the business to be identified, the identification module 1703 performs risk identification on the business to be identified, including: inputting the business scenario into a preset risk assessment model to output the potential risk types existing in the business scenario; outputting the potential risk types existing in the business scenario so that security experts can confirm the risk types existing in the business scenario based on the potential risk types.
[0141] In one possible implementation, when the business scenario and / or risk information of the business to be identified is the risk information of the business to be identified, and the risk information is the estimated potential risk type, the identification module 1703 performs risk identification on the business to be identified, including: outputting the business scenario and the estimated potential risk type, so that security experts can confirm the risk type existing in the business scenario based on the potential risk type.
[0142] In one possible implementation, the acquisition module 1701 is specifically used to: perform static program analysis on the above-mentioned multiple applications respectively to obtain the static program analysis results of each of the above-mentioned multiple applications; and perform dynamic program analysis on the above-mentioned multiple applications respectively to obtain the dynamic program analysis results of each of the above-mentioned multiple applications.
[0143] Based on the static and dynamic program analysis results of the above applications, business abstraction modeling is performed on each of the above applications to obtain behavioral data of various target types for each of the above applications.
[0144] In one possible implementation, the acquisition module 1701 performs static program analysis on the multiple applications respectively to obtain the static program analysis results of each of the multiple applications, including: determining the development framework corresponding to each of the multiple applications; performing framework analysis on the development framework corresponding to each of the multiple applications to obtain the initialization analysis results corresponding to each of the multiple applications; and analyzing the initialization analysis results corresponding to each of the multiple applications according to preset flow analysis rules to obtain the static program analysis results of each of the multiple applications.
[0145] In one possible implementation, the static and dynamic program analysis results include code comments; the acquisition module 1701 performs business abstract modeling on the multiple applications based on their respective static and dynamic program analysis results, obtaining behavioral data of various target types for each of the multiple applications, including: segmenting the code comments to obtain several keywords; determining target keywords corresponding to risk types and / or scenarios based on the keywords and a preset mapping library; and performing business abstract modeling on the multiple applications based on the target keywords to obtain behavioral data of various target types for each of the multiple applications.
[0146] In one possible implementation, the acquisition module 1701 performs business abstract modeling on the multiple applications based on the aforementioned target keywords to obtain behavioral data of various target types for each of the multiple applications, including: acquiring confirmation information or supplementary information from security experts regarding the aforementioned target keywords; and performing business abstract modeling based on the confirmation information or supplementary information from security experts regarding the aforementioned target keywords to obtain behavioral data of various target types for each of the multiple applications.
[0147] In one possible implementation, the aforementioned target types include: application-based behavior, business behavior, security risk behavior, and security defense behavior.
[0148] It should be noted that the risk identification device provided in the above embodiments is only illustrated by the division of the above functional modules when performing the risk identification method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0149] Furthermore, the risk identification device and risk identification method embodiments provided in the above embodiments belong to the same concept. Therefore, for details not disclosed in the device embodiments of this specification, please refer to the risk identification method embodiments of the characters mentioned above in this specification, which will not be repeated here.
[0150] This specification also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of any of the methods described above.
[0151] Figure 18 This schematic diagram illustrates the structure of an electronic device according to an exemplary embodiment of this specification. Please refer to... Figure 18 As shown, the electronic device 1800 includes a processor 1801 and a memory 1802.
[0152] In the embodiments described in this specification, processor 1801 is the control center of the computer system, and can be a processor of a physical machine or a processor of a virtual machine. Processor 1801 may include one or more processing cores, such as a 4-core processor, a 9-core processor, etc. Processor 1801 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). Processor 1801 may also include a main processor and a coprocessor; the main processor is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state.
[0153] Memory 1802 may include one or more computer-readable storage media, which may be non-transitory. Memory 1802 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments of this specification, the non-transitory computer-readable storage media in memory 1802 is used to store at least one instruction for execution by processor 1801 to implement the methods in the embodiments of this specification.
[0154] In some embodiments, the electronic device 1800 further includes a peripheral device interface 1803 and at least one peripheral device. The processor 1801, memory 1802, and peripheral device interface 1803 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1803 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of a display screen 1804, a camera 1805, and an audio circuit 1806.
[0155] Peripheral interface 1803 can be used to connect at least one input / output (I / O) related peripheral device to processor 1801 and memory 1802. In some embodiments of this specification, processor 1801, memory 1802, and peripheral interface 1803 are integrated on the same chip or circuit board; in some other embodiments of this specification, any one or two of processor 1801, memory 1802, and peripheral interface 1803 may be implemented on separate chips or circuit boards. This specification does not specifically limit the embodiments in this regard.
[0156] Display screen 1804 is used to display a user interface (UI). The UI may include graphics, text, icons, video, and any combination thereof. When display screen 1804 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1801 for processing. In this case, display screen 1804 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments of this specification, there may be one display screen 1804, which is used as the front panel of electronic device 1800; in other embodiments, there may be at least two display screens, respectively disposed on different surfaces of electronic device 1800 or in a folded design; in still other embodiments, display screen 1804 may be a flexible display screen, disposed on a curved or folded surface of electronic device 1800. Furthermore, display screen 1804 may also be configured as a non-rectangular irregular shape, i.e., a non-rectangular screen. The display screen 1804 can be made of materials such as liquid crystal display (LCD) and organic light-emitting diode (OLED).
[0157] Camera 1805 is used to capture images or videos. Optionally, camera 1805 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the electronic device, and the rear-facing camera is located on the back of the electronic device. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, virtual reality (VR) shooting, or other fusion shooting functions. In some embodiments of this specification, camera 1805 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.
[0158] The audio circuit 1806 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals that are input to the processor 1801 for processing. For stereo sound acquisition or noise reduction purposes, there may be multiple microphones, each located in a different part of the electronic device 1800. The microphone may also be an array microphone or an omnidirectional microphone.
[0159] Power supply 1807 is used to supply power to various components in electronic device 1800. Power supply 1807 can be alternating current, direct current, a disposable battery, or a rechargeable battery. When power supply 1807 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.
[0160] The block diagrams of the electronic device shown in the embodiments of this specification do not constitute a limitation on the electronic device 1800. The electronic device 1800 may include more or fewer components than shown, or combine certain components, or use different component arrangements.
[0161] In the description of this specification, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of these terms in this specification based on the specific circumstances. Furthermore, in the description of this specification, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.
[0162] This specification also provides a computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform one or more steps in the above embodiments. If the constituent modules of the character display device described above are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium.
[0163] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this specification are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The aforementioned available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., Digital Versatile Discs (DVDs)), or semiconductor media (e.g., Solid State Disks (SSDs)).
[0164] It should be noted that the above description describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims may be performed in a different order than that shown in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0165] The above description is merely a specific embodiment of this specification, but the scope of protection of this specification is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this specification should be included within the scope of protection of this specification. Therefore, equivalent variations made in accordance with the claims of this specification are still within the scope of this specification.
Claims
1. A risk identification method, wherein, The method includes: Acquire behavioral data of various target types from multiple applications; Based on the behavioral data of various target types from each of the multiple applications, determine the input nodes, output nodes, and data consumption nodes of each of the multiple applications. Based on the input nodes, output nodes, and data consumption nodes of the multiple applications, a first link and a second link are constructed for each of the multiple applications; wherein, the first link is the link between the input node and the output node, and the second link is the link between the input node and the data consumption node; A cross-application graph database is constructed based on the first and second links of each of the multiple applications; wherein, the cross-application graph database stores the association relationships between behavioral data of various target types of each of the multiple applications; Determine the starting input node of the service to be identified; wherein the service to be identified includes at least one of the plurality of applications; Among the data consumption nodes in the cross-application graph database, the target data consumption node is determined; By traversing the path between the starting input node and the target data consumption node in the cross-application graph database, the business scenario and / or risk information of the business to be identified are determined according to the path and preset scenario identification rules and / or risk determination rules; wherein, the risk information is the final risk type or the estimated potential risk type. When determining the business scenario and / or risk information of the business to be identified is to determine the business scenario of the business to be identified, the business scenario is input into a preset risk assessment model to output the potential risk types existing in the business scenario; the potential risk types existing in the business scenario are output so that security experts can confirm the risk types existing in the business scenario based on the potential risk types; When the determination of the business scenario and / or risk information of the business to be identified is the determination of the risk information of the business to be identified, and the risk information is the estimated potential risk type, the business scenario and the estimated potential risk type are output so that security experts can confirm the risk type existing in the business scenario based on the potential risk type.
2. The method of claim 1, wherein, The step of constructing a cross-application graph database based on the first and second links of each of the multiple applications includes: Among the nodes on the first and second links of the various applications, input nodes and output nodes of the same type are identified; A cross-application graph database is constructed by connecting input and output nodes of the same type.
3. The method according to claim 1, wherein, The acquisition of behavioral data of various target types from multiple applications includes: Static program analysis was performed on each of the multiple applications to obtain the static program analysis results for each application. Dynamic program analysis is performed on each of the multiple applications to obtain the dynamic program analysis results for each application. Based on the static and dynamic program analysis results of each of the multiple applications, business abstraction modeling is performed on each of the multiple applications to obtain behavioral data of various target types for each of the multiple applications.
4. The method according to claim 3, wherein, The step of performing static program analysis on the multiple applications respectively to obtain the static program analysis results for each of the multiple applications includes: Determine the development frameworks corresponding to the various applications; Framework analysis is performed on the development frameworks corresponding to the multiple applications to obtain the initialization analysis results for each application. Based on preset flow analysis rules, the initialization analysis results corresponding to the multiple applications are analyzed to obtain the static program analysis results of each application.
5. The method according to claim 3, wherein, The static and dynamic program analysis results include code comments; Based on the static and dynamic program analysis results of each of the multiple applications, business abstraction modeling is performed on each of the multiple applications to obtain behavioral data of various target types for each application, including: The code comments were segmented to obtain several keywords; Based on the aforementioned keywords and a pre-defined mapping library, target keywords corresponding to risk types and / or scenarios are determined; Based on the target keywords, business abstraction modeling is performed on the multiple applications respectively to obtain behavioral data of various target types for each application.
6. The method according to claim 5, wherein, The process involves performing business abstract modeling based on the target keywords to obtain behavioral data of various target types for each of the multiple applications, including: Obtain confirmation or supplementary information from security experts regarding the target keywords; Based on the security experts' confirmation or supplementary information regarding the target keywords, business abstraction modeling is performed to obtain behavioral data of various target types for each of the multiple applications.
7. The method according to claim 1, wherein, The various target types include: application-based behavior, business behavior, security risk behavior, and security defense behavior.
8. A risk identification device, wherein, The device includes: The acquisition module is used to acquire behavioral data of various target types from multiple applications. A construction module is used to determine the input nodes, output nodes, and data consumption nodes of the multiple applications based on behavioral data of various target types for each application; construct a first link and a second link for each application based on the input nodes, output nodes, and data consumption nodes for each application; wherein the first link is the link between the input node and the output node, and the second link is the link between the input node and the data consumption node; and construct a cross-application graph database based on the first link and the second link for each application; wherein the cross-application graph database stores the association relationships between the behavioral data of various target types for each application. An identification module is used to determine the starting input node of the service to be identified; wherein the service to be identified includes at least one of the plurality of applications; among the data consumption nodes in the cross-application graph database, a target data consumption node is determined; by traversing the path between the starting input node and the target data consumption node in the cross-application graph database, the business scenario and / or risk information of the service to be identified is determined according to the path and preset scenario identification rules and / or risk determination rules; wherein the risk information is the final risk type or the estimated potential risk type; when the determination of the business scenario and / or risk information of the service to be identified is... When defining the business scenario of the service to be identified, the business scenario is input into a preset risk assessment model to output the potential risk types existing in the business scenario; the potential risk types existing in the business scenario are output so that security experts can confirm the risk types existing in the business scenario based on the potential risk types; when determining the business scenario and / or risk information of the service to be identified is determining the risk information of the service to be identified, and the risk information is the estimated potential risk type, the business scenario and the estimated potential risk type are output so that security experts can confirm the risk types existing in the business scenario based on the potential risk types.
9. An electronic device, wherein, The electronic device includes: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the electronic device to perform the method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, wherein, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 7.
Citation Information
Patent Citations
Data processing path analysis method, computer device and storage medium
CN110826057A
