Interface monitoring method, device, electronic equipment and storage medium

By obtaining similar domain name information and monitoring its API, the problem of not being able to identify and monitor batch domain names in the existing technology is solved, and efficient monitoring of multiple domain names is achieved, and identification efficiency is improved.

CN112685255BActive Publication Date: 2024-12-03EVERSEC BEIJING TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011607096.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-30
Publication Date
2024-12-03
Estimated Expiration
2040-12-30

AI Technical Summary

Technical Problem

The prior art cannot realize the identification of batch domain names and intercept and monitoring of interfaces connecting similar domain names. It can only analyze and monitor a single domain name.

Method used

By obtaining the target domain name information, we further obtain the same domain name information, and monitor the APIs that access the same domain name, and use batch data of the same domain name information to achieve API monitoring of multiple domain names.

Benefits of technology

It improves the efficiency of identifying batch domain name information, realizes effective monitoring of batch APIs connecting batch domain names, and solves the monitoring problem that can only be targeted at a single domain name in the existing technology.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112685255B_ABST
    Figure CN112685255B_ABST
Patent Text Reader

Abstract

The embodiment of the present invention discloses an interface monitoring method, device, electronic device and storage medium. The interface monitoring method comprises: obtaining target domain name information according to target access data; obtaining similar domain name information according to the target domain name information; and monitoring the target API accessing the similar domain name information. The technical solution of the embodiment of the present invention can improve the recognition efficiency of batch domain name information, thereby effectively monitoring the batch API connected to the batch domain names.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to an interface monitoring method, device, electronic device and storage medium. Background Art

[0002] At present, with the development of Internet technology, network security incidents emerge in an endless stream. Internet network security is receiving more and more attention, and interface monitoring is a technical point of network security. For example, monitoring an interface can monitor the application connected to the interface, and can also monitor the website connected to the interface. Therefore, interface monitoring technology is receiving more and more attention.

[0003] In the prior art, domain names with similar features are identified through feature screening and URLs, and similar domain names / URLs and suspected samples after feature screening are analyzed and judged, and the attributes of similar domain names / URLs and suspected samples are further determined to achieve iterative updates of similar domain name / URL libraries. However, the prior art is an analysis of a single domain name, and cannot achieve the discovery of similar domain names in batches, nor can it achieve the interception and monitoring of interfaces connected to similar domain names. For example, illegal domain names are identified through black and white lists and URLs, and suspected samples are screened using black and white lists. The suspected illegal domain names are further analyzed and judged, the black and white attributes of the suspected illegal domain names are obtained, and the domain names with clear attributes are stored in the library, but it cannot achieve the discovery of illegal domain names in batches, nor can it achieve the interception and monitoring of interfaces connected to illegal domain names. Summary of the invention

[0004] The embodiments of the present invention provide an interface monitoring method, device, electronic device and storage medium, which improve the recognition efficiency of batch domain name information, thereby effectively monitoring batch APIs connected to batch domain names.

[0005] In a first aspect, an embodiment of the present invention provides an interface monitoring method, comprising:

[0006] Obtain target domain name information based on target access data;

[0007] Obtain similar domain name information based on target domain name information;

[0008] Monitor target APIs that access the same domain name information.

[0009] In a second aspect, an embodiment of the present invention further provides an interface monitoring device, including:

[0010] A target domain name information acquisition module is used to acquire target domain name information according to target access data;

[0011] A module for acquiring information of similar domain names, used to acquire information of similar domain names according to information of target domain names;

[0012] The target API monitoring module is used to monitor the target APIs that access the same domain name information.

[0013] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0014] one or more processors;

[0015] A storage device for storing one or more programs;

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the interface monitoring method provided by any embodiment of the present invention.

[0017] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium on which a computer program is stored, and when the program is executed by a processor, the interface monitoring method provided by any embodiment of the present invention is implemented.

[0018] The technical solution of this embodiment obtains the target domain name information according to the target access data, and further obtains the same type of domain name information according to the target domain name information, so as to monitor the API that accesses the same type of domain name information. The above technical solution obtains the same type of domain name information through the target domain name information. Since the same type of domain name information includes batch domain name data, and the same type of domain name information and the target domain name information have similar characteristics, that is, the monitored target API and the API connected to the target domain name information belong to the same type of API, it is possible to monitor the API connected to each domain name according to the batch domain name data, which solves the problem of only discovering and monitoring the API corresponding to the target domain name information in the prior art, realizes the identification of batch domain name data, and improves the identification efficiency of batch domain name information, thereby effectively monitoring the batch API connected to the batch domain name. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a flow chart of an interface monitoring method provided by Embodiment 1 of the present invention;

[0020] Figure 2 This is a schematic diagram of API link information provided by Embodiment 1 of the present invention;

[0021] Figure 3 This is a schematic diagram of a process for obtaining illegal APP samples provided in the first embodiment of the present invention;

[0022] Figure 4 This is a schematic diagram of domain name access for a regular APP and an illegal APP provided in the first embodiment of the present invention;

[0023] Figure 5aThis is a schematic diagram of target domain name information when the domain name acquisition parameter is A03 provided in the first embodiment of the present invention;

[0024] Figure 5b This is a schematic diagram of target domain name information when the domain name acquisition parameter is A02 provided in the first embodiment of the present invention;

[0025] Figure 6 is a flow chart of an interface monitoring method provided by Embodiment 2 of the present invention;

[0026] Figure 7 is a schematic diagram of an interface monitoring device provided by Embodiment 3 of the present invention;

[0027] Figure 8 A schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0028] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention.

[0029] It should also be noted that, for ease of description, only the part relevant to the present invention but not all content is shown in the accompanying drawings. It should be mentioned before discussing exemplary embodiments in more detail that some exemplary embodiments are described as processing or methods depicted as flow charts. Although the flow chart describes each operation (or step) as sequential processing, many operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. When its operation is completed, the processing can be terminated, but it can also have additional steps not included in the accompanying drawings. The processing can correspond to methods, functions, procedures, subroutines, subprograms, etc.

[0030] Embodiment 1

[0031] Figure 1 is a flow chart of an interface monitoring method provided by the first embodiment of the present invention. This embodiment is applicable to monitoring batches of specific types of interfaces. The method can be executed by an interface monitoring device, which can be implemented by software and / or hardware and can generally be integrated into an electronic device. Figure 1 As shown, the method includes the following operations:

[0032] S110. Obtain target domain name information according to target access data.

[0033] The target access data may be Internet access data generated by accessing a website or server and needing to be monitored and processed. The target domain name information may be domain name data included in the target access data, and such domain name data is the domain name that needs to be monitored.

[0034] Specifically, specific types of target access data can be parsed from telecommunications network and / or Internet data according to interface monitoring requirements, and the target access data can be further processed by data cleaning and data screening to obtain target domain name information.

[0035] In an optional embodiment of the present invention, obtaining target domain name information based on target access data may include: obtaining a target application sample; parsing the target application sample to obtain target access data; extracting API link information of the target access data; and obtaining target domain name information based on the API link information.

[0036] Among them, the target application sample can be an application sample data that is already held and needs to be monitored. Exemplarily, the target application sample can be an illegal APP sample. Optionally, the illegal APP sample can be a fraud APP, etc. Based on the illegal APP sample, the network data accessed by the illegal APP sample and the API information connected to the illegal APP can be obtained. In addition, a line search can be performed based on the target application sample, that is, a related information search is performed based on the target application sample. API (Application Programming Interface) link information can be a control parameter that points from an access target to another accessed target. Control parameters can be used to establish a connection relationship between two targets. For example, API link information can be used for an APP (Application) with access requirements to point to an accessed web page, picture, email, file or application. The embodiment of the present invention does not limit the specific content represented by the access target and the accessed target.

[0037] Specifically, the target application sample can be obtained from the known application database, and the access data of the target application sample can be further parsed to obtain the target access data. The target access data is processed to extract the API link information, and finally the API link information is parsed to obtain the target domain name information. In a specific example, the specific data format of the API link information is as follows: Figure 2 It should be noted that Figure 2 This is only a schematic diagram of API link information. It is understandable that different API types have corresponding different API link information. The embodiment of the present invention does not limit the specific information content of the API link information.

[0038] Exemplarily, illegal APP samples can be obtained as target application samples from various channels such as regulatory authorities, law enforcement agencies or third parties, and the Internet access data generated when the illegal APP samples visit illegal websites is further parsed to obtain data of illegal websites, such as the domain name, IP address, and access log of the illegal website. The API connected to the illegal website is obtained based on the domain name or IP address of the illegal website, and the link information of the API is further extracted, so that the domain name data of the corresponding illegal website, that is, the target domain name information, can be obtained based on the link information of the API.

[0039] Figure 3 is a schematic diagram of a flow chart of obtaining illegal APP samples provided by the first embodiment of the present invention. In a specific example, Figure 3 As shown, firstly, the original network data is crawled by Internet crawler technology. The original network data may include network data such as original traffic data, Internet logs, SMS data, and web page frames, and then the original network data is processed. For example, the original network data is screened according to known suspected illegal samples and behavioral feature screening rules, and the original network data is matched and processed according to the URL (Uniform Resource Locator) in the known knowledge base. After the original network data is processed, suspected illegal APP data can be obtained, and the suspected illegal APP data is further detected in combination with the domain name data in the knowledge base, and the illegal APP is finally determined. The detected illegal APP is stored in the known knowledge base to update the illegal APP sample. Among them, the suspected illegal APP data is subjected to static analysis detection, dynamic analysis monitoring or manual confirmation. Static analysis detection may include static analysis detection such as decompilation, disassembly and similarity matching. Dynamic analysis detection may include network behavior analysis, local behavior analysis and sandbox simulation detection. Among them, the knowledge base may be a database storing a large number of illegal sample lists, illegal access behavior logs, illegal website domain names, IP addresses and victim-related information.

[0040] It is understandable that normal APP (Application) can communicate data by accessing the main domain name, while illegal APP communicates differently from normal APP. Every time an illegal APP logs in, it will call a specific API interface to obtain an available dynamic domain name. Once the currently used domain name is blocked, a new domain name will be randomly generated for illegal APP to use. Because the website that provides services for illegal APPs is discovered, the website faces the risk of being blocked. If the server-side website is blocked, the illegal application will not be able to connect to the server, and thus will not be able to communicate with the server. However, the communication method of dynamic domain names will make it more difficult to monitor and intercept illegal domain names. Figure 4This is a schematic diagram of domain name access between a regular APP and an illegal APP provided in the first embodiment of the present invention. In a specific example, Figure 4 As shown in the figure, after the APP is started, the communication process of accessing the main domain name is a regular APP communication process. After the APP is started, it accesses the dynamic domain name API interface, that is, a specific interface to obtain the latest surviving domain name. Further, the APP that communicates by accessing the surviving domain name is an illegal APP. Therefore, the corresponding domain name information can be obtained as the target domain name information through the API link information of the illegal APP.

[0041] In an optional embodiment of the present invention, obtaining target domain name information according to API link information may include: configuring domain name acquisition parameters for the API link information; obtaining target domain name information according to a response result of the domain name acquisition parameters; wherein there are multiple domain name acquisition parameters, and one domain name acquisition parameter corresponds to one target domain name information.

[0042] The domain name acquisition parameter may be data for configuring the API link information, and the response result may be the result of configuring the API link information according to the domain name acquisition parameter.

[0043] In an embodiment of the present invention, before determining the target domain name information, the domain name acquisition parameter may be determined first, so as to configure the API link information according to the domain name acquisition parameter. Optionally, the number of domain name acquisition parameters may be multiple. Accordingly, when configuring the API link information according to the domain name acquisition parameter, multiple domain name data may be obtained, i.e., the response result of the domain name acquisition parameter. The obtained domain name data is further used as the target domain name information. Among them, according to a domain name acquisition parameter, a corresponding target domain name information may be obtained.

[0044] In a specific example, Figure 5a As shown in FIG. 1 , when the domain name acquisition parameter configured for the API link information is A03, the target domain name information acquired according to the response result of the name acquisition parameter A03 is m.5006659.com. Figure 5b As shown, when the domain name acquisition parameter configured for the API link information is A02, the target domain name information acquired according to the response result of the name acquisition parameter A02 is m.204079.com.

[0045] In a specific example, after configuring the API link information according to the domain name, simulated access can be performed according to the configured API link data, such as accessing the corresponding domain name according to the configured API link data through sandbox technology. If the domain name is determined to be a domain name that needs to be monitored, the API connected to the domain name is further monitored, and the domain name is used as the target domain name information.

[0046] S120: Obtain similar domain name information according to the target domain name information.

[0047] The similar domain name information may be domain name data having a certain degree of similarity with the target domain name information.

[0048] Specifically, after obtaining the target domain name information, domain name data with a certain degree of similarity to the target domain name information can be determined according to the target domain name information, and the domain name data with a certain degree of similarity to the target domain name information is regarded as the same type of domain name information. The certain degree of similarity can be a percentage, which is used to represent the data repetition rate.

[0049] For example, an extension search is performed on illegal APP samples to obtain related data under the target domain name information, such as illegal website domain names, related website domain names, criminal identity information, email addresses, and communication addresses. Then, similar illegal domain names are obtained based on the related data, which has higher efficiency and data accuracy than iterative updates of domain name blacklists and whitelists. Illegal domain names can be identified within and between operator networks.

[0050] S130. Monitor target APIs that access the same type of domain name information.

[0051] The target API may be an API connected to a domain name of the same type. The domain name of the same type may be domain name data in domain name information of the same type, and the domain name information of the same type may be a domain name of the same category as the target domain name information.

[0052] Accordingly, after obtaining the domain name information of the same type, data processing can be performed on the domain name information of the same type, and the domain name data included in the domain name information of the same type can be parsed, and the API connected to it, i.e., the target API, can be further determined based on each domain name data, and the target API can be monitored or blocked. In addition, various types of applications connected to the target API can also be determined, thereby realizing the monitoring and blocking of the applications connected to the target API.

[0053] The technical solution of this embodiment obtains the target domain name information according to the target access data, and further obtains the same type of domain name information according to the target domain name information, so as to monitor the API that accesses the same type of domain name information. The above technical solution obtains the same type of domain name information through the target domain name information. Since the same type of domain name information includes batch domain name data, and the same type of domain name information and the target domain name information have similar characteristics, that is, the monitored target API and the API connected to the target domain name information belong to the same type of API, it is possible to monitor the API connected to each domain name according to the batch domain name data, which solves the problem of only discovering and monitoring the API corresponding to the target domain name information in the prior art, realizes the identification of batch domain name data, and improves the identification efficiency of batch domain name information, thereby effectively monitoring the batch API connected to the batch domain name.

[0054] Embodiment 2

[0055] Figure 6 is a flow chart of an interface monitoring method provided by Embodiment 2 of the present invention. This embodiment is specific based on the above embodiment. In this embodiment, a specific optional implementation scheme for obtaining similar domain name information according to target domain name information is provided. Correspondingly, Figure 6 As shown, the method includes the following operations:

[0056] S210: Obtain target domain name information according to target access data.

[0057] S220: Obtain benchmark API information according to the monitoring result of the target domain name information.

[0058] The monitoring result may be information such as programs and interfaces related to the target domain name information that need to be monitored, for example, the monitoring result may include an API connected to the target domain name information, an application accessing the target domain name information, and a website to which the target domain name information belongs, etc. The benchmark API information may be an API connected to the target domain name information.

[0059] Specifically, the API connected to the target domain name information may be first determined according to the monitoring result of the target domain name information, and the API connected to the target domain name information may be further used as the benchmark API information.

[0060] S230 , extracting a benchmark API feature of the benchmark API information according to the API link information of the benchmark API information.

[0061] The API link information of the benchmark API information may be the API link information corresponding to the benchmark API information. The benchmark API feature may be the feature possessed by the benchmark API information. For example, the benchmark API feature may include but is not limited to features such as domain name features and IP address features.

[0062] Specifically, data analysis is performed on the benchmark API information to obtain API link information of the benchmark API information, and feature extraction processing is further performed on the obtained API link information of the benchmark API information to obtain benchmark API features.

[0063] S240. Obtain similar domain name information according to the benchmark API characteristics.

[0064] Specifically, after determining the benchmark API features, similar APIs can be obtained according to the benchmark API features, and domain name information of similar APIs can be used as similar domain name information. Among them, similar APIs can be APIs whose own features have a certain degree of similarity with the benchmark API features.

[0065] In an optional embodiment of the present invention, obtaining similar domain name information based on benchmark API features may include: obtaining domain name information to be monitored; determining the API to be monitored based on the domain name information to be monitored; extracting API features to be monitored of the API to be monitored based on API link information of the API to be monitored; performing feature similarity matching on the API features to be monitored and the benchmark API features; and obtaining similar domain name information based on the feature similarity matching result.

[0066] Among them, the domain name information to be monitored may be the domain name that needs to be monitored. The API to be monitored may be an API that can access the domain name information to be monitored. The API link information of the API to be monitored may be the link information of the API to be monitored. The API features to be monitored may be the features possessed by the API to be monitored. For example, the API features to be monitored may include but are not limited to the IP address, domain name, web page data, web page framework, and application data connected to the API to be monitored. The feature similarity match may be the similarity obtained by comparing the features of each API to be monitored with the benchmark API features. The feature similarity match result may be the feature matching result of each API feature to be monitored with the benchmark API features.

[0067] Specifically, the domain name information to be monitored can be first determined in the user's Internet traffic data, and the API to be monitored that accesses the domain name information to be monitored can be determined, and the API link information of the API to be monitored can be further obtained, and the API link information of the API to be monitored can be feature extracted to obtain the API feature to be monitored of the API to be monitored. The API feature to be monitored and the benchmark API feature can be further matched for feature similarity, so as to further obtain the same domain name information according to the feature similarity matching result.

[0068] In an optional embodiment of the present invention, the monitored API features and the benchmark API features are field data; obtaining similar domain name information based on the feature similarity matching results may include: when the feature similarity matching results meet the feature matching threshold, determining that the monitored API is the target API; and determining the domain name information corresponding to the target API as similar domain name information.

[0069] The field data may be a domain name field or an IP field data. The feature matching threshold may be a preset constant used to determine the feature similarity. The target API may be an API that satisfies the feature similarity.

[0070] Correspondingly, when the features of the API to be monitored and the features of the benchmark API are field data, if the feature similarity matching result of the features of the API to be monitored and the benchmark API meets the feature matching threshold, indicating that the API to be monitored and the benchmark API belong to the same type of API, the API to be monitored is used as the target API, and the domain name information corresponding to the target API is determined as the same type of domain name information. If the feature similarity matching result of the features of the API to be monitored and the benchmark API does not meet the feature matching threshold, indicating that the API to be monitored and the benchmark API do not belong to the same type of API, the API to be monitored is not used as the target API.

[0071] S250. Monitor target APIs that access the same type of domain name information.

[0072] Specifically, when the same type of domain name information is determined according to the target API, the target API accessing the same type of domain name information may be monitored.

[0073] S260: Obtain API link information of the target API.

[0074] In the embodiment of the present invention, after the target API is determined, the API link information of the target API is determined according to the target domain name information of the target API.

[0075] S270: Re-acquire iterative domain name information of the same type according to the API link information of the target API.

[0076] The iterative similar domain name information may be similar domain name information reacquired according to the API link information of the target API.

[0077] Specifically, after obtaining the API link information of the target API, feature extraction and feature similarity matching are performed on the API link information of the target API, and the domain name information corresponding to the target API that meets the feature matching threshold is used as iterative similar domain name information. Further, the API connected to the iterative similar domain name information can be determined, and the API connected to the iterative similar domain name information can be monitored. The target domain name information can be further updated with the iterative similar domain name information, and the updated target domain name information is then used to obtain the similar domain name information again to achieve the update of the similar domain name information, thereby monitoring the target API that accesses the updated similar domain name information. It can be seen that the implementation scheme of the present invention can achieve batch discovery of target domain name information and target APIs, and quickly accumulate domain name information and APIs based on the target domain name information and target APIs, so as to achieve the effect of tracking and monitoring batch target domain name information and batch target APIs. The technical solution of this embodiment obtains benchmark API information based on the monitoring result of the target domain name information, further extracts benchmark API features of the benchmark API information based on the API link information of the benchmark API information, and further obtains similar domain name information based on the benchmark API features. After obtaining the similar domain name information, on the one hand, the target API that accesses the similar domain name information can be monitored, and on the other hand, iterative similar domain name information can be obtained based on the obtained API link information of the target API, which solves the problem that the prior art only discovers and monitors the API corresponding to the target domain name information, and achieves the accumulation of larger-scale API information when identifying batch domain name data, that is, more domain name information and API information are obtained through one API link information, so as to achieve the effect of effectively monitoring batch APIs.

[0078] It should be noted that any arrangement and combination of the technical features in the above embodiments also falls within the protection scope of the present invention.

[0079] Embodiment 3

[0080] Figure 7 is a schematic diagram of an interface monitoring device provided by Embodiment 3 of the present invention, such as Figure 7 As shown, the device includes: a target domain name information acquisition module 310, a similar domain name information acquisition module 320 and a target API monitoring module 330, wherein:

[0081] The target domain name information acquisition module 310 is used to acquire the target domain name information according to the target access data;

[0082] A similar domain name information acquisition module 320 is used to acquire similar domain name information according to the target domain name information;

[0083] The target API monitoring module 330 is used to monitor the target APIs that access the same type of domain name information.

[0084] The technical solution of this embodiment obtains the target domain name information according to the target access data, and further obtains the same domain name information according to the target domain name information, so as to monitor the API accessing the same domain name information. The above technical solution obtains the same domain name information through the target domain name information. Since the same domain name information includes batch illegal domain name data, the illegal APIs connected to each domain name can be monitored according to the batch illegal domain name data, which solves the problem of only discovering and monitoring the illegal API corresponding to the target domain name information in the prior art, and achieves the effect of identifying the batch illegal domain name data and monitoring the batch illegal API.

[0085] Optionally, the target domain name information acquisition module 310 is specifically used to: obtain the target domain name information based on the target access data, including: obtaining a target application sample; parsing the target application sample to obtain the target access data; extracting API link information of the target access data; and obtaining the target domain name information based on the API link information.

[0086] Optionally, the target domain name information acquisition module 310 is specifically used to: obtain the target domain name information according to the API link information, including: configuring domain name acquisition parameters for the API link information; obtaining the target domain name information according to a response result of the domain name acquisition parameters; wherein the number of the domain name acquisition parameters is multiple, and one domain name acquisition parameter corresponds to one target domain name information.

[0087] Optionally, the same domain name information acquisition module 320 is specifically used to: obtain the same domain name information according to the target domain name information, including: obtaining benchmark API information according to the monitoring results of the target domain name information; extracting the benchmark API characteristics of the benchmark API information according to the API link information of the benchmark API information; obtaining the same domain name information according to the benchmark API characteristics.

[0088] Optionally, the module 320 for obtaining the same domain name information is specifically used for: obtaining the same domain name information according to the benchmark API characteristics, including: obtaining the domain name information to be monitored; determining the API to be monitored according to the domain name information to be monitored; extracting the API characteristics to be monitored of the API to be monitored according to the API link information of the API to be monitored; performing feature similarity matching on the API characteristics to be monitored and the benchmark API characteristics; and obtaining the same domain name information according to the feature similarity matching result.

[0089] Optionally, the monitored API features and the benchmark API features are field data; the same type domain name information acquisition module 320 is specifically used to: when the feature similarity matching result meets the feature matching threshold, determine that the monitored API is the target API; determine the domain name information corresponding to the target API as the same type domain name information.

[0090] Optionally, the interface monitoring device also includes: an iterative similar domain name information acquisition module, which is used to, after monitoring the target API that accesses the similar domain name information, also include: acquiring API link information of the target API; and re-acquiring iterative similar domain name information based on the API link information of the target API.

[0091] The technical solution of this embodiment obtains the target domain name information according to the target access data, and further obtains the same type of domain name information according to the target domain name information, so as to monitor the API that accesses the same type of domain name information. The above technical solution obtains the same type of domain name information through the target domain name information. Since the same type of domain name information includes batch domain name data, and the same type of domain name information and the target domain name information have similar characteristics, that is, the monitored target API and the API connected to the target domain name information belong to the same type of API, it is possible to monitor the API connected to each domain name according to the batch domain name data, which solves the problem of only discovering and monitoring the API corresponding to the target domain name information in the prior art, realizes the identification of batch domain name data, and improves the identification efficiency of batch domain name information, thereby effectively monitoring the batch API connected to the batch domain name.

[0092] The above interface monitoring device can execute the interface monitoring method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, please refer to the interface monitoring method provided by any embodiment of the present invention.

[0093] Since the interface monitoring device described above is a device that can execute the interface monitoring method in the embodiment of the present invention, based on the interface monitoring method described in the embodiment of the present invention, the technical personnel in the field can understand the specific implementation of the interface monitoring device of the present embodiment and its various variations, so how the interface monitoring device implements the interface monitoring method in the embodiment of the present invention is not described in detail here. As long as the technical personnel in the field implement the device used in the interface monitoring method in the embodiment of the present invention, it belongs to the scope of protection of this application.

[0094] Embodiment 4

[0095] Figure 8 A schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. Figure 8A block diagram of an electronic device 412 suitable for implementing embodiments of the present invention is shown. Figure 8 The electronic device 412 shown is only an example and should not limit the functions and scope of use of the embodiments of the present invention. The electronic device 412 can be, for example, an electronic device or a server device.

[0096] like Figure 8 As shown, the electronic device 412 is in the form of a general purpose computing device. The components of the electronic device 412 may include, but are not limited to: one or more processors 416, a storage device 428, and a bus 418 connecting different system components (including the storage device 428 and the processor 416).

[0097] Bus 418 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0098] The electronic device 412 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 412, including volatile and non-volatile media, removable and non-removable media.

[0099] The storage device 428 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 430 and / or cache memory 432. The electronic device 412 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 434 may be used to read and write non-removable, non-volatile magnetic media ( Figure 8 not shown, usually called a "hard drive"). Although Figure 8Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a read-only optical disk (Compact Disc-Read Only Memory, CD-ROM), a digital video disk (Digital Video Disc-Read Only Memory, DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 418 via one or more data medium interfaces. The storage device 428 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0100] A program 436 having a set (at least one) of program modules 426 may be stored, for example, in a storage device 428, such program modules 426 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may include an implementation of a network environment. Program modules 426 generally perform the functions and / or methods of the embodiments described herein.

[0101] The electronic device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, camera, display 424, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 412, and / or communicate with any device that enables the electronic device 412 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 422. In addition, the electronic device 412 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through a network adapter 420. As shown, the network adapter 420 communicates with other modules of the electronic device 412 through a bus 418. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 412, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems.

[0102] The processor 416 executes various functional applications and data processing by running the program stored in the storage device 428, such as implementing the interface monitoring method provided in the above-mentioned embodiment of the present invention: obtaining target domain name information according to target access data; obtaining similar domain name information according to the target domain name information; and monitoring the target API that accesses the similar domain name information.

[0103] The technical solution of this embodiment obtains the target domain name information according to the target access data, and further obtains the same type of domain name information according to the target domain name information, so as to monitor the API that accesses the same type of domain name information. The above technical solution obtains the same type of domain name information through the target domain name information. Since the same type of domain name information includes batch domain name data, and the same type of domain name information and the target domain name information have similar characteristics, that is, the monitored target API and the API connected to the target domain name information belong to the same type of API, it is possible to monitor the API connected to each domain name according to the batch domain name data, which solves the problem of only discovering and monitoring the API corresponding to the target domain name information in the prior art, realizes the identification of batch domain name data, and improves the identification efficiency of batch domain name information, thereby effectively monitoring the batch API connected to the batch domain name.

[0104] Embodiment 5

[0105] Embodiment 5 of the present invention further provides a computer storage medium storing a computer program, wherein the computer program, when executed by a computer processor, is used to execute the interface monitoring method described in any of the above embodiments of the present invention: obtaining target domain name information based on target access data; obtaining similar domain name information based on the target domain name information; and monitoring the target API that accesses the similar domain name information.

[0106] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, a device or a device or used in combination with it.

[0107] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0108] The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

[0109] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0110] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An interface monitoring method, characterized in that: include: Obtain target domain name information based on target access data; Acquire similar domain name information according to the target domain name information; Monitor the target application program interface API that accesses the same domain name information; Wherein, obtaining similar domain name information according to the target domain name information includes: Obtaining benchmark API information based on the monitoring result of the target domain name information; Extracting a benchmark API feature of the benchmark API information according to the API link information of the benchmark API information; Obtaining domain name information of the same type according to the benchmark API features; The obtaining of similar domain name information according to the benchmark API feature includes: Get the domain name information to be monitored; Determine the API to be monitored according to the domain name information to be monitored; Extracting the monitored API features of the monitored API according to the API link information of the monitored API; Performing feature similarity matching on the API feature to be monitored and the benchmark API feature; Acquire the domain name information of the same type according to the feature similarity matching result; The obtaining the same type of domain name information according to the feature similarity matching result includes: When the feature similarity matching result meets the feature matching threshold, determining the API to be monitored as a target API; The domain name information corresponding to the target API is determined as the same type of domain name information.

2. The method according to claim 1, characterized in that The step of obtaining target domain name information according to target access data includes: Get samples of target applications; Parsing the target application sample to obtain the target access data; Extracting API link information of the target access data; The target domain name information is obtained according to the API link information.

3. The method according to claim 2, characterized in that The acquiring the target domain name information according to the API link information includes: Configure domain name acquisition parameters for the API link information; Acquire the target domain name information according to the response result of the domain name acquisition parameter; There are multiple domain name acquisition parameters, and one domain name acquisition parameter corresponds to one target domain name information.

4. The method according to claim 1, characterized in that: in, The API feature to be monitored and the benchmark API feature are field data.

5. The method according to claim 1, characterized in that: After monitoring the target API accessing the same type of domain name information, the method further includes: Obtaining API link information of the target API; Re-acquire and iterate domain name information of the same type according to the API link information of the target API.

6. A domain name monitoring device, characterized in that: include: A target domain name information acquisition module is used to acquire target domain name information according to target access data; A module for acquiring information of similar domain names, used to acquire information of similar domain names according to the target domain name information; A target API monitoring module, used to monitor the target API accessing the same domain name information; The module for acquiring information of the same type of domain name is specifically used to: acquire benchmark API information according to the monitoring result of the target domain name information; extract benchmark API features of the benchmark API information according to the API link information of the benchmark API information; and acquire the same type of domain name information according to the benchmark API features; The method of obtaining similar domain name information according to the benchmark API feature includes: obtaining domain name information to be monitored; determining the API to be monitored according to the domain name information to be monitored; extracting the API feature to be monitored of the API to be monitored according to the API link information of the API to be monitored; performing feature similarity matching on the API feature to be monitored and the benchmark API feature; and obtaining the similar domain name information according to the feature similarity matching result; The obtaining of the same type of domain name information according to the feature similarity matching result includes: determining the API to be monitored as a target API when the feature similarity matching result meets a feature matching threshold; and determining the domain name information corresponding to the target API as the same type of domain name information.

7. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the interface monitoring method as described in any one of claims 1-5.

8. A computer storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the interface monitoring method as described in any one of claims 1 to 5 is implemented.