Risk identification method and device, electronic equipment and storage medium
By obtaining and analyzing the application's running list information in the target system and identifying the application's component and class information, the problem of the existing technology being unable to identify risks from within the application is solved, and the application's security risks are identified and identified. Threat protection.
Patent Information
- Application Number
- CN202410937059.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2024-11-12
AI Technical Summary
The existing network security defense methods cannot be identified from within the application, resulting in the blocking of legitimate user operations or the exploitation of security vulnerabilities by hackers.
By performing instrumentation processing in the target system, the operation list information of the target application is obtained, the application operation information is determined, including component information and application-type information, and risk identification is carried out based on this information.
It realizes security risks identification from within the application, improves hidden danger identification efficiency, reduces the risk of false alarms and underreports, and provides protection against internal threat attacks on the application.
Smart Images

Figure CN118940274A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security, and specifically to a risk identification method, device, electronic device and storage medium. Background Art
[0002] As the complexity of network applications continues to increase, enterprises are facing many challenges in application security. The current defense methods mainly use intrusion protection systems (IPS) or web application firewalls (WAF), etc. Although this technology can detect and prevent attacks at the network layer, it cannot see what is happening inside the application. The lack of context may cause the normal operations of legitimate users to be blocked or even bypassed by malicious users. In addition, the open source or third-party software used by enterprises is very likely to contain security vulnerabilities, which can easily allow applications to enter the production environment with vulnerabilities and be discovered and exploited by hackers.
[0003] Therefore, a method for risk identification from within the application is needed. Summary of the invention
[0004] An embodiment of the present application provides a risk identification method that can identify risks from within an application.
[0005] In a first aspect, an embodiment of the present application provides a risk identification method, the method comprising: in a target system that has been instrumented, obtaining, based on the instrumentation, operation list information generated by a target application in the target system during operation; determining application operation information of the target application based on the operation list information, the application operation information including component information and / or application class information; and performing risk identification on the target application based on the application operation information.
[0006] In the second aspect, an embodiment of the present application provides a risk identification device, which includes: a first acquisition module, which is used to obtain, in a target system that has been instrumented, operation list information generated by a target application in the target system during operation based on the instrumentation; a first determination module, which is used to determine application operation information of the target application based on the operation list information, wherein the application operation information includes component information and / or application class information; and a first identification module, which is used to perform risk identification on the target application based on the application operation information.
[0007] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.
[0008] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
[0009] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.
[0010] In an embodiment of the present application, in a target system that has been instrumented, operation list information generated by a target application in the target system during operation is obtained based on the instrumentation; application operation information of the target application is determined based on the operation list information, wherein the application operation information includes component information and / or application class information; and risks of the target application are identified based on the application operation information, so that security risks can be identified from within the application. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 It is a flowchart of a risk identification method provided in an embodiment of the present application;
[0012] Figure 2 is a flow chart of a second risk identification method provided in an embodiment of the present application;
[0013] Figure 3 It is a flowchart of a third risk identification method provided in an embodiment of the present application;
[0014] Figure 4 It is a flowchart of the fourth risk identification method provided in this application specification;
[0015] Figure 5 It is a structural schematic diagram of a risk identification device provided in an embodiment of the present application;
[0016] Figure 6 It is a structural schematic diagram of a risk identification device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0017] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0018] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0019] The risk identification method provided in the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.
[0020] Figure 1 A risk identification method provided by an embodiment of the present invention is shown. The method can be executed by an electronic device, and the electronic device may include: a server and / or a terminal device, wherein the terminal device may be, for example, a vehicle-mounted terminal or a mobile phone terminal. In other words, the method can be executed by software or hardware installed in the risk identification device, and the method includes the following steps:
[0021] Step 102: in the target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by the target application in the target system when it is running;
[0022] The risk identification system obtains the operation list information generated by the target application in the target system when it is running based on the instrumentation from the target system that has been instrumented. In other words, the target system is an instrumented system that can obtain the list information generated by the target application when it is running, wherein the target application is the application running in the target system.
[0023] Specifically, when the target program is running, the stub can monitor and scan all loaded classes in the target system to obtain a class list, that is, running list information. The class list here can include class collection information, and the class collection information can include one or more of identification information, attribute information and storage address, wherein the identification information can be a parameter "name" or "classname", the attribute information can be a parameter "size", and the storage address can be a parameter "path". Of course, the data can also be filtered, such as only recording the two parameters "name" and "path", or only including the "name" parameter, and then obtaining the "path" parameter according to the "classes" directory of "name" under the "target" directory.
[0024] More specifically, the risk identification system includes an Agent module, which can be installed on a target system so as to obtain inventory information generated by the operation of the target application when the target application is running.
[0025] Step 104: Determine application running information of the target application based on the running list information;
[0026] The application running information includes component information and / or application class information.
[0027] After obtaining the operation list information, the risk identification system determines the application operation information of the target application based on the operation list information, wherein the application operation information includes component information and / or application class information, the component information is the operation information of the components in the target application, and the application class information is the class information generated when the target application runs in the target system. In other words, the risk identification system determines the component information and application class information based on the operation list information, and then determines the application operation information based on the component information and / or application class information, such as only the component information can be determined as the application operation information, only the application class information can be determined as the application operation information, or both the component information and the application class information can be determined as the application operation information.
[0028] Specifically, after the Agent module of the risk identification system obtains the running list information of the target application in the target system, the Agent module can parse the component information and application class information of the target application according to the running list information, thereby determining the component information and application class information. For example, the obtained component information can be:
[0029] {
[0030] "name":"spring-boot-autoconfigure-2.7.8.jar",
[0031] "size":1677556,
[0032] "path":
[0033] "file: / rasp / rasp-test / jdbc_demo-0.0.1-SNAPSHOT.jar! / BOOT-INF / lib / spring-boot-autoconfigure-2.7.8.jar! / ",
[0034] "sha1":"6a7a2d0fa596830a24974c7762f40554ff2f64d1",
[0035] "artifact":"Spring Boot AutoConfigure",
[0036] "version":"2.7.8",
[0037] "artifactSource":"MANIFEST"
[0038] }
[0039] It can also be:
[0040] {
[0041] "name":"jackson-databind-2.13.4.2.jar",
[0042] "size":1531681,
[0043] "path":
[0044] "file: / rasp / rasp-test / jdbc_demo-0.0.1-SNAPSHOT.jar! / BOOT-INF / lib / jackson-datab ind-2.13.4.2.jar! / ",
[0045] "sha1":"057ebbf30caf00e47e050bf5f8fbcaeb387414b6",
[0046] "artifact":"com.fasterxml.jackson.core:com.fasterxml.jackson.core",
[0047] "version":"2.13.4.2",
[0048] "artifactSource":"MANIFEST"
[0049] }
[0050] The application class information obtained can be:
[0051] {
[0052] "superClasses":[
[0053] "java.lang.Object"
[0054] ],
[0055] "superName":"java.lang.Object",
[0056] "classLoaders":[
[0057] "sun.misc.Launcher$AppClassLoader@18b4aac2",
[0058] "sun.misc.Launcher$ExtClassLoader@2133c8f8",
[0059] "bootstrapClassloader"
[0060] ],
[0061] "interfaces":[],
[0062] "annotations":[
[0063] "org.springframework.web.bind.annotation.RequestMapping",
[0064] "org.springframework.web.bind.annotation.RestController"
[0065] ],
[0066] "location":"file: / data / code / security / sec / java-sec-code / target / classes / ",
[0067] "className":"org.joychou.controller.XmlRce",
[0068] "artifact":"com.fasterxml.jackson.core:com.fasterxml.jackson.core",
[0069] "artifactSha1":"057ebbf30caf00e47e050bf5f8fbcaeb387414b6"
[0070] }
[0071] Step 106: Identify risks of the target application based on the application operation information.
[0072] After determining the application running information, the risk identification system performs risk identification on the target application based on the application running information to determine whether there is risk information in the running information of the target application. For example, it can determine whether there is risk information in the information of various components of the target application based on the component information in the application running information. It can also determine whether there is risk information in the class information generated by the target application running based on the application class information in the application running information.
[0073] Specifically, when the risk identification system performs risk identification on application operation information, it can identify component information and application class information in the application operation information through a risk identification algorithm, thereby determining a risk index, and determining whether a target application is at risk based on the risk index. It can also determine whether the application operation information meets preset risk information conditions, thereby determining that the target application is a risky application when component information or application class information in the application operation information meets preset risk information conditions. It can also perform risk identification on the application operation information of the target application through other risk identification methods.
[0074] More specifically, after the Agent module included in the risk identification system determines the application running information, the Agent module sends the determined application running information to the Server module of the risk identification system, so that the Server module of the risk identification system can identify the risk of the target application according to the application running information. The Server module can be a set of programs that control the operation of the server, manage and upgrade different levels of software such as processing hardware, operating system and application software, and manage system resources, performance maintenance and monitoring configuration. IT administrators can remotely configure the details of the Server module through the web module of the risk identification system, and monitor the usage and performance of key components such as processors, hard drives, and memory. The server management, deployment and software distribution functions are expanded through optional additional products. The Server module can maintain the basic information of the Agent module, such as the host host name, the address of the Agent, the Agent name, the version of the Agent, and other data of the Agent. The Agent module and the Server module can maintain heartbeat detection logic to ensure that both the Agent module and the Server module can work normally. The Server module is mainly used to provide cloud services, which mainly include data collection, data processing, policy issuance, and log storage. The Server module obtains the identification method from the Web module and identifies the application running information. The Web module of the risk identification system is mainly used for administrator configuration and can configure the identification method. The Server module can build fine-grained application asset information from a security perspective, collect application component libraries in real time, eliminate asset blind spots, and achieve effective management of application assets. It can also clarify the component library and version information used by the application, perform vulnerability detection on the component library, and discover the risk component library called by the application, so as to be targeted for subsequent security reinforcement and protection.
[0075] The risk identification method provided by the embodiment of the present invention obtains the operation list information generated by the target application in the target system during operation based on the instrumentation in the target system after the instrumentation; determines the application operation information of the target application based on the operation list information, and the application operation information includes component information and / or application class information; and identifies the risks of the target application based on the application operation information, which can not only identify security risks from within the application program, but also improve the efficiency of risk identification and reduce the risks of false positives and false negatives.
[0076] In one implementation, before obtaining the running list information generated by the target application in the target system during running (step 102), step A may also be performed:
[0077] Step A: When creating the target system, perform instrumentation processing on the target system to obtain the running list information of the target application when the target application is running.
[0078] Before the risk identification system obtains the operation list information of the target application in the target system, it is necessary to perform instrumentation processing in the target system so that the risk identification system obtains the operation list information of the target application in the target system through instrumentation.
[0079] When performing instrumentation on the target system, the instrumentation can be performed directly on the target system, or when the target system is created. For example, when the target system is a jvm virtual machine, the instrumentation can be performed on the jvm virtual machine each time the jvm virtual machine is created. Specifically, when the target system is a jvm virtual machine, for a host machine with an Agent module installed, instrumentation can be performed in the jxm virtual machine each time the jvm virtual machine is created. The instrumentation can be used to monitor the classes and components loaded in the jvm in real time, that is, the application running information, and then the Agent module sends the monitored application running information to the Server module, and the Server module performs risk identification.
[0080] In one implementation, the determining the application running information of the target application based on the running list information (step 104) may execute steps B1-B4:
[0081] Step B1: determining component location information and application class location information based on the running list information;
[0082] After the risk identification system obtains the operation list information, the risk identification system obtains the component location information and application class location information included in the operation list information, wherein the component location information is used to characterize the storage address information of the component information, and the application class location information is used to characterize the storage address information of the application class information. For example, the path where the file is located can be determined according to the path parameter in the Class list, and the path where the file is located can be determined as the storage address.
[0083] Step B2: determining component files and application class files respectively according to the component location information and the application class location information;
[0084] After the risk identification system determines the component location information and the application class location information, the risk identification system determines the file where the component information is located and the file where the application class information is located according to the file path where the component information is located and the file path where the application class location information is located in the component location information and the application class location information.
[0085] Step B3: determining component information and application class information based on the component file and the application class file respectively;
[0086] After determining the component files and the application class files, the risk identification system determines the component information according to the component files, and determines the application class information according to the application class files. Specifically, after the risk identification system determines the component information related files, i.e., the component files, and the application class information related files, i.e., the application class files, it can parse the component files and the application class files to determine the component information and the application class information.
[0087] Step B4: Determine the application running information according to the component information and the application class information.
[0088] After determining the component information and application class information, the risk identification system determines the application operation information based on the component information and the application class information. Specifically, the risk identification system may determine the component information as the application operation information, may determine the application class information as the application operation information, or may determine the component information and the application class information together as the application operation information.
[0089] Specifically, because the component information may include multiple application class information, when the application operation information is determined based on the component information and the application class information, the component information and the related application class information can be integrated into one piece of information based on the correspondence between the component information and the application class information, and risk identification can be performed based on the combined information.
[0090] Figure 2 is a flow chart of a second risk identification method provided in an embodiment of this specification, such as Figure 2 As shown, the schematic diagram includes:
[0091] Step 202: When creating the target system, perform instrumentation processing on the target system to obtain the running list information of the target application when the target application is running;
[0092] Step 204: in the target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by the target application in the target system when it is running;
[0093] Step 206: Determine component location information and application class location information based on the running list information;
[0094] Step 208: Determine component files and application class files respectively according to the component location information and the application class location information;
[0095] Step 210: Determine component information and application class information based on the component file and the application class file respectively;
[0096] Step 212: Determine the application running information according to the component information and the application class information;
[0097] Step 214: Identify risks of the target application based on the application operation information.
[0098] In the embodiments of the specification, by inserting the target system when creating the target system, the running list information generated by the running of the target application can be obtained, and then the component information and application class information are determined according to the component location information and application class location information in the running list information, and risks of the component information and application class information are identified, which can make up for the internal security perspective that is missing in traditional security, identify risks within the application program, provide powerful threat attack protection capabilities for internal enterprise applications, and ensure the security of application runtime.
[0099] In one implementation, after determining the application running information of the target application based on the running list information (step 104), steps C1-C3 may also be performed:
[0100] Step C1: Obtain the preset field screening rules;
[0101] After determining the application operation information, the risk identification system can obtain preset field screening rules, wherein the field screening rules are used to perform field screening and determine valid fields and redundant fields in the entire field.
[0102] Step C2: performing a redundant field screening operation on the fields in the application running information based on the field screening rule to determine the remaining target valid fields;
[0103] After determining the field screening rules, the risk identification system performs redundant field screening operations on the fields in the application operation information based on the field screening rules to determine the remaining target valid fields.
[0104] Specifically, the application operation information includes multiple field data, and the field screening rules can screen the valid fields and redundant fields in the multiple field data, that is, determine whether each field data in the application operation information is a redundant field or a valid field, and then the risk identification system will screen the redundant fields in the application operation information, remove the redundant fields, and retain the valid fields, and determine the target valid fields from the retained multiple valid fields. Furthermore, when the risk identification system performs a screening operation on the redundant fields in the application operation information, the risk identification system can screen out the fields of useless information, and can also screen out the duplicate fields, and can also screen out the redundant fields in the application operation information through other screening operations.
[0105] Step C3: Determine target operation information based on the target valid field, and identify risks of the target application based on the target operation information.
[0106] After determining the target valid field, the risk identification system determines the target valid field as the target operation information, that is, the target operation information is the valid information in the application operation information, which is a simplification of the application operation information. After determining the target operation information, the risk identification system performs risk identification on the target application based on the target operation information to determine whether there is risk information in the information belonging to the target application.
[0107] Specifically, when determining the target operation information according to the target valid field, the target valid field can be directly determined as the target operation information, and the target operation information can also be determined based on the target valid field and the preset identifier, wherein the preset identifier is determined based on the screening operation, that is, different fields included in different application operation information can be screened using different screening rules, and then different preset identifiers are determined according to different screening rules when based on the target valid field, and then the target operation information is determined according to the target valid field and the preset identifier corresponding thereto. In other words, different application operation information has different screening rules, and different screening rules correspond to different preset identifiers, and when determining the target operation information according to the target valid field, the target operation information can be determined jointly according to the target valid field and the target operation identifier, so that the risk identification system can determine the information content included in the complete application operation information according to the target operation information.
[0108] In one implementation, the redundant field screening operation is performed on the fields in the application running information based on the field screening rule to determine the remaining target valid fields (step C2), and steps D1-D4 may be executed:
[0109] Step D1: Obtain the name field, work artifact field, version field, and search path field in the target application information;
[0110] When the risk identification system performs redundant field screening operations on the fields in the running application, it obtains the name field, work artifact field, version field, and search path field in the target application information. For example, the name field can be "name":"jackson-databind-2.13.4.2.jar", the artifact field can be "artifact":"com.fasterxml.jackson.core:com.fasterxml.jackson.core", the version field can be "version":"2.13.4.2", and the path field can be "path":"file: / rasp / rasp-test / jdbc_demo-0.0.1-SNAPSHOT.jar! / BOOT-INF / lib / jackson-data bind-2.13.4.2.jar! / ".
[0111] Step D2: Identify whether the path field includes the name field, the artifact field, and the version field;
[0112] After determining the path field, name field, artifact field and version field, the risk identification system identifies whether the path field includes the name field, artifact field and version field. For example, when the determined path field is "path":"file: / rasp / rasp-test / jdbc demo-0.0.1-SNAPSHOT.jar! / / BOOT-INF / lib / jackson-databind-2.13.4.2.jar! / ", it determines whether it includes the name field "name":"jackson-databind-2.13.4.2.jar", whether it includes the artifact field "artifact":"com.fasterxml.jackson.core:com.fasterxml.jackson.core", and whether it includes the version field "version":"2.13.4.2".
[0113] Step D3: when the path field includes the name field, the artifact field, and the version field, determining the target valid field based on the path field;
[0114] After the risk identification system determines whether the path field includes the name field, artifact field, and version field, the risk identification system will determine the target valid field based on the path field when the path field includes the name field, artifact field, and version field. In other words, when the path field includes the name field, artifact field, and version field, the name field, artifact field, and version field can be determined based on the path field, indicating that after the name field, artifact field, and version field in the target application information are deleted, the name field, artifact field, and version field can still be determined based on the path field.
[0115] Specifically, after the risk identification system determines that the path field includes the name field, the artifact field and the version field, it can directly determine the target valid field as the target operation information, or it can determine the target operation information based on the target valid field and the preset identifier corresponding to the filtering rule, or it can determine the target operation information based on the target valid field, the information field and the preset identifier corresponding to the filtering rule, wherein the information field is the field in the application operation information except the path field, the name field, the artifact field and the version field, such as the "sha1 field" and the "artifactSource field" in the component information.
[0116] Step D4: When the name field, the artifact field, and the version field are not included in the path field, the target valid field is determined based on the path field and the target field, and the target field is one or more of the name field, the artifact field, and the version field that are not included in the path field.
[0117] When the path field does not include the name field, the artifact field, and the version field, the risk identification system determines the target valid field based on the path field and the target field, where the target field is one or more of the name field, the artifact field, and the version field that are not included in the path field. That is, after determining the name field, the artifact field, or the version field that is not included in the path field, the risk identification system determines the target valid field based on the path field and the name field, the artifact field, and the version field that are not included in the path field. For example, when the path field does not include the name field, the risk identification system determines the target valid field based on the path field and the name field, and when the path field does not include the artifact field and the version field, the path field determines the target valid field based on the artifact field and the version field.
[0118] Specifically, after the risk identification system determines that the path field does not include one or more of the name field, the artifact field, and the version field, the path field and the name field, the artifact field, or the version field not included in the path field can be directly determined as the target operation information, and the path field, the information field, and the name field, the artifact field, or the version field not included in the path field can also be determined as the target operation information. The target operation information can also be determined based on the path field, the information field, the name field, the artifact field, or the version field not included in the path field, and a preset identifier corresponding to the screening rule, wherein the information field is the application operation information except the path field, the artifact field, or the version field. For fields other than the ame field, artifact field, and version field, such as the "sha1 field" and "artifactSource field" in the component information, the preset identifier is the identifier corresponding to the filtering rule. For example, the filtering rules when the path field does not include the name field and when the path field does not include the artifact field are different. When the path field does not include the name field, the artifact field and the version field are filtered out. When the path field does not include the artifact field, the name field and the version field are filtered out. The preset identifier corresponding to filtering the artifact field and the version field is different from the preset identifier for filtering the name field and the version field.
[0119] More specifically, when the path field contains the name field, the artifact field, and the version field, a first identifier is output, and the first identifier is followed by the first message; when the path field does not contain the name field, a second identifier is output, and the second identifier is followed by the second message; when the path field does not contain the artifact field, a third identifier is output, and the third identifier is followed by the second message; when the path field does not contain the version field, a fourth identifier is output, and the fourth identifier is followed by the second message; when the path field does not contain the artifact field and the version field, a fifth identifier is output, and the fifth identifier is followed by the third message; when the path field does not contain the name field and the artifact field, a sixth identifier is output, and the sixth identifier is followed by the third message; when the path field does not contain the name field and the artifact field When the segment does not contain the name field and the artifact field, the seventh identifier is output, and the seventh identifier is followed by the third message; when the path field does not contain the name field, the artifact field and the version field, the eighth identifier is output, and the eighth identifier is followed by the fourth message, wherein the first message can be composed of the path field, and can also be based on the path field and the information field, the second message can be composed of the path field, and can also be based on the path field and the information field, and can also be based on the path field, the information field and a replacement field, the third message can be based on the path field, the information field and two replacement fields, and the fourth message can be based on the path field, the information field and three replacement fields, wherein the replacement field is a fixed field used to characterize the identity of the message.
[0120] Figure 3 is a flow chart of a second risk identification method provided in an embodiment of this specification, such as Figure 3 As shown, the schematic diagram includes:
[0121] Step 302: in a target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by a target application in the target system when it is running;
[0122] Step 304: Determine application running information of the target application based on the running list information;
[0123] The application running information includes component information and / or application class information.
[0124] Step 306: Obtaining preset field screening rules;
[0125] Step 308: Obtain the name field, work artifact field, version field, and search path field in the target application information;
[0126] Step 310: Identify whether the path field includes the name field, the artifact field, and the version field;
[0127] Step 312: when the path field includes the name field, the artifact field, and the version field, determining the target valid field based on the path field;
[0128] Step 314: when the path field does not include the name field, the artifact field, and the version field, determining the target valid field based on the path field and the target field;
[0129] The target field is one or more of the name field, the artifact field, and the version field that are not included in the path field.
[0130] Step 316: determining target operation information based on the target valid field, and performing risk identification on the target application based on the target operation information;
[0131] Step 318: Identify risks of the target application based on the application operation information.
[0132] In the embodiments of the specification, after determining the application running information, the fields included in the application running information are screened and processed, and risks of multi-target applications are identified based on the target running information determined by the remaining fields. This can reduce the amount of data while ensuring the integrity of component information, thereby improving the efficiency of risk identification of target applications.
[0133] In one implementation, the risk identification includes security risk identification. The risk identification of the target application based on the application operation information (step 106) may include executing steps E1-E2:
[0134] Step E1: Obtain a preset safety hazard information database;
[0135] The potential safety hazard information library includes a plurality of sample operation information, and the sample operation information is operation information with potential safety hazard in the application.
[0136] The risk identification system obtains a preset potential safety hazard information library, wherein the potential safety hazard information library includes a plurality of sample operation information, and the sample operation information is operation information with potential safety hazard in the application. In other words, the risk identification system obtains the pre-stored operation information with potential safety hazard in a plurality of applications.
[0137] Specifically, because the application running information of the target application includes component information and application class information, the security risk information library used to identify the application running information also includes sample component information and sample application class information, wherein the sample component information is component information with security risks in multiple applications, and the sample application class information is class information with security risks in multiple applications.
[0138] Step E2: determining whether the security risk information library includes the application running information, and determining that the target application is an application with security risks when the security risk information library includes the application running information.
[0139] After acquiring a preset potential safety hazard information database, the risk identification system determines whether the potential safety hazard information database includes application running information, and then determines the target application as an application with potential safety hazard when the potential safety hazard database includes the application running information.
[0140] Specifically, application operation information includes component information and application class information. Therefore, the security risk information library can include component information with security risks and application class information with security risks in multiple applications. Then the risk identification system determines whether the component information with security risks includes the component information of the target application, and determines whether the application class information with security risks includes the application class information of the target application. Finally, when the component information with security risks includes the component information of the target application or the application class information with security risks includes the application class information of the target application, the target application is determined to be an application with security risks.
[0141] More specifically, when the risk identification system conducts risk identification on the target system, it can determine the security risks of the target application through the security risk information library, that is, the security risk information library pre-stores the security risk information corresponding to each application with security risks. Then, after determining that the target application has security risks, the risk identification system can determine the security risk information corresponding to the operation information with security risks from the preset security risk information library.
[0142] In one implementation, after obtaining the operation list information of the target system (step 104), steps F1-F4 may also be performed:
[0143] Step F1: obtaining preset whitelist information and blacklist information, and determining whether the whitelist information and the blacklist information include the running list information;
[0144] After obtaining the running list information, the risk identification system can also obtain the whitelist information and the blacklist information, and determine whether the whitelist information and the blacklist information include the running list information. The whitelist information includes the running list information of the trusted applications, and the blacklist information includes the running list information of the untrusted applications.
[0145] Step F2: when the whitelist information includes the operation list information, determining that the operation list information is risk-free information;
[0146] When determining that the whitelist information includes the operation list information of the target application, the risk identification system may determine that the operation list information of the target application is the operation list information of a trustworthy application, and thus may determine the operation list information as risk-free information.
[0147] Specifically, after determining that the operation list information of the target application is risk-free, the risk identification system determines that the target application is risk-free, and there is no need to determine the application operation information based on the operation list information, and no longer identify risks for the target application based on the application operation information.
[0148] Step F3: when the blacklist information includes the operation list information, determining that the operation list information is risk information, and intercepting the operation list information;
[0149] When it is determined that the blacklist information includes the operation list information of the target application, the risk identification system can determine that the operation list information of the target application is the operation list information of the application that cannot be trusted, and thus can directly determine the operation list information as risky information. After determining that the operation list information of the target application is risky information, the risk identification system can directly intercept the operation list information of the target application.
[0150] Specifically, after determining that the operation list information of the target application is risk information, the risk identification system directly determines that the target application has risks, and there is no need to determine the application operation information based on the operation list information, and no longer identify risks for the target application based on the application operation information.
[0151] Step F4: when the running list information is not included in the whitelist information and the blacklist information, the application running information is determined based on the running list information.
[0152] When it is determined that neither the whitelist information nor the blacklist information includes the operation list information, the risk identification system cannot directly determine whether the target application has risks based on the operation list information. Therefore, the risk identification system determines the application operation information based on the operation list information, and then identifies risks of the target application through the application operation information.
[0153] Figure 4 is a flow chart of a fourth risk identification method provided in an embodiment of this specification, such as Figure 4 As shown, the schematic diagram includes:
[0154] Step 402: in a target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by a target application in the target system when it is running;
[0155] Step 404: Obtain preset whitelist information and blacklist information, and determine whether the whitelist information and the blacklist information include the running list information;
[0156] Step 406: When the whitelist information includes the operation list information, determining that the operation list information is risk-free information;
[0157] Step 408: When the blacklist information includes the operation list information, determining that the operation list information is risk information, and intercepting the operation list information;
[0158] Step 410: when the running list information is not included in the whitelist information and the blacklist information, determining the application running information based on the running list information;
[0159] The application running information includes component information and / or application class information.
[0160] Step 412: Obtain a preset security risk information database;
[0161] The potential safety hazard information library includes a plurality of sample operation information, and the sample operation information is operation information with potential safety hazard in the application.
[0162] Step 414: Determine whether the security risk information library includes the application running information, and when the security risk information library includes the application running information, determine that the target application is an application with security risks.
[0163] In the embodiments of the specification, after obtaining the running list information, it is determined whether the running list information belongs to the whitelist information or the blacklist information, and then when the running list information does not belong to the whitelist information and the blacklist information, the application running information is determined according to the running list information and the security risks of the target application are identified according to the application running information. This can ensure that the application running information is completed while reducing the amount of data that needs to be processed, thereby improving the efficiency of security risk identification.
[0164] It should be noted that the risk identification method provided in the embodiment of the present application can be executed by a risk identification device or a control module in the risk identification device for executing the risk identification method. In the embodiment of the present application, the risk identification device provided in the embodiment of the present application is described by taking the risk identification method executed by the risk identification device as an example.
[0165] Figure 5 Schematic diagram of the structure of the risk identification device according to an embodiment of the present invention. Figure 5 As shown, the risk identification device includes: a first acquisition module 502 , a first determination module 504 , and a first identification module 506 .
[0166] A first acquisition module 502 is used to acquire, in a target system that has been instrumented, running list information generated by a target application in the target system when the target application is running based on the instrumentation;
[0167] A first determining module 504, configured to determine application running information of the target application based on the running list information, wherein the application running information includes component information and / or application class information;
[0168] The first identification module 506 is used to identify risks of the target application based on the application running information.
[0169] The risk identification device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0170] The risk identification device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0171] The risk identification device provided in the embodiment of the present application can achieve Figures 1 to 4To avoid repetition, the various processes implemented in the method embodiment are not described here.
[0172] Based on the same technical concept, an embodiment of the present application further provides an electronic device, which is used to execute the above-mentioned risk identification method. Figure 6 A schematic diagram of the structure of an electronic device for implementing various embodiments of the present application. The electronic device may have relatively large differences due to different configurations or performances, and may include a processor (processor) 602, a communication interface (Communications Interface) 604, a memory (memory) 606, and a communication bus 608, wherein the processor 602, the communication interface 604, and the memory 606 communicate with each other through the communication bus 608. The processor 602 may call a computer program stored in the memory 606 and executable on the processor 602 to perform the following steps:
[0173] In a target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by a target application in the target system when it is running;
[0174] Determine application running information of the target application based on the running list information, wherein the application running information includes component information and / or application class information;
[0175] Risk identification is performed on the target application based on the application operation information.
[0176] In one implementation, before obtaining the running list information generated by the target application in the target system during running, the method further includes:
[0177] When the target system is created, the target system is instrumented to obtain the running list information of the target application when the target application is running.
[0178] In one implementation, determining the application running information of the target application based on the running list information includes:
[0179] Determine component location information and application class location information based on the running list information;
[0180] Determine component files and application class files respectively according to the component location information and the application class location information;
[0181] Determine component information and application class information based on the component file and the application class file respectively;
[0182] The application running information is determined according to the component information and the application class information.
[0183] In one implementation, after determining the application running information of the target application based on the running list information, the method further includes:
[0184] Get the preset field filtering rules;
[0185] Performing a redundant field screening operation on the fields in the application running information based on the field screening rule to determine the remaining target valid fields;
[0186] Target operation information is determined based on the target valid field, and risk identification is performed on the target application based on the target operation information.
[0187] In one implementation, performing a redundant field screening operation on the fields in the application running information based on the field screening rule to determine the remaining target valid fields includes:
[0188] Get the name field, work artifact field, version field, and search path field in the target application information;
[0189] Identify whether the path field includes the name field, the artifact field, and the version field;
[0190] When the path field includes the name field, the artifact field, and the version field, determining the target valid field based on the path field;
[0191] When the name field, the artifact field, and the version field are not included in the path field, the target valid field is determined based on the path field and the target field, and the target field is one or more of the name field, the artifact field, and the version field that are not included in the path field.
[0192] In one implementation, the risk identification includes security risk identification, and the risk identification of the target application based on the application running information includes:
[0193] Obtaining a preset potential safety hazard information database, wherein the potential safety hazard information database includes a plurality of sample operation information, wherein the sample operation information is operation information with potential safety hazard in the application;
[0194] It is determined whether the security risk information library includes the application running information, and when the security risk information library includes the application running information, it is determined that the target application is an application with security risks.
[0195] In one implementation, after obtaining the operation list information of the target system, the method further includes:
[0196] Obtaining preset whitelist information and blacklist information, and determining whether the whitelist information and the blacklist information include the running list information;
[0197] When the whitelist information includes the operation list information, determining that the operation list information is risk-free information;
[0198] When the blacklist information includes the operation list information, determining that the operation list information is risk information, and intercepting the operation list information;
[0199] When the running list information is not included in the whitelist information and the blacklist information, the application running information is determined based on the running list information.
[0200] The specific execution steps can refer to the various steps of the above-mentioned risk identification method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.
[0201] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals or other devices except terminals.
[0202] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0203] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).
[0204] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.
[0205] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned risk identification method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0206] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0207] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned risk identification method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0208] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0209] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0210] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0211] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A risk identification method, comprising: In a target system that has been instrumented, obtaining, based on the instrumentation, running list information generated by a target application in the target system when it is running; Determine application running information of the target application based on the running list information, wherein the application running information includes component information and / or application class information; Risk identification is performed on the target application based on the application operation information.
2. According to the method of claim 1, before obtaining the running list information generated by the target application in the target system during running, the method further comprises: When the target system is created, the target system is instrumented to obtain the running list information of the target application when the target application is running.
3. The method according to claim 1, wherein determining the application running information of the target application based on the running list information comprises: Determine component location information and application class location information based on the running list information; Determine component files and application class files respectively according to the component location information and the application class location information; Determine component information and application class information based on the component file and the application class file respectively; The application running information is determined according to the component information and the application class information.
4. The method according to claim 1, after determining the application running information of the target application based on the running list information, the method further comprises: Get the preset field filtering rules; Performing a redundant field screening operation on the fields in the application running information based on the field screening rule to determine the remaining target valid fields; Target operation information is determined based on the target valid field, and risk identification is performed on the target application based on the target operation information.
5. The method according to claim 4, wherein the performing a redundant field screening operation on the fields in the application running information based on the field screening rule to determine the remaining target valid fields comprises: Get the name field, work artifact field, version field, and search path field in the target application information; Identify whether the path field includes the name field, the artifact field, and the version field; When the path field includes the name field, the artifact field, and the version field, determining the target valid field based on the path field; When the name field, the artifact field, and the version field are not included in the path field, the target valid field is determined based on the path field and the target field, and the target field is one or more of the name field, the artifact field, and the version field that are not included in the path field.
6. According to the method of claim 1, the risk identification includes security risk identification, and the risk identification of the target application based on the application operation information includes: Obtaining a preset potential safety hazard information database, wherein the potential safety hazard information database includes a plurality of sample operation information, wherein the sample operation information is operation information with potential safety hazard in the application; It is determined whether the security risk information library includes the application running information, and when the security risk information library includes the application running information, it is determined that the target application is an application with security risks.
7. The method according to claim 1, after obtaining the operation list information of the target system, the method further comprises: Obtaining preset whitelist information and blacklist information, and determining whether the whitelist information and the blacklist information include the running list information; When the whitelist information includes the operation list information, determining that the operation list information is risk-free information; When the blacklist information includes the operation list information, determining that the operation list information is risk information, and intercepting the operation list information; When the running list information is not included in the whitelist information and the blacklist information, the application running information is determined based on the running list information.
8. A risk identification device, comprising: A first acquisition module is used to acquire, in a target system that has been instrumented, running list information generated by a target application in the target system when the target application is running based on the instrumentation; A first determination module, configured to determine application running information of the target application based on the running list information, wherein the application running information includes component information and / or application class information; The first identification module is used to identify risks of the target application based on the application running information.
9. A computer device, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions, wherein the executable instructions are configured to be executed by the processor, and the executable instructions include instructions for executing the steps in the risk identification method according to any one of claims 1 to 7.
10. A storage medium, characterized in that: The storage medium is used to store computer-executable instructions, and the executable instructions enable a computer to execute the risk identification method as described in any one of claims 1 to 7.
