Formalization detection method and system for malicious URL (uniform resource locator)

Abstract

The invention discloses a formalization detection method for a malicious URL (uniform resource locator). The formalization detection method comprises the following steps of: splitting the URL to be detected into syntactic element character strings according to a URL syntactic structure on the basis of the standard of RFC (request for comments); extracting designated character strings from the character strings obtained by splitting; performing completing treatment on the non-existent character strings; reordering the character strings obtained after completing treatment to obtain a new URL, and calculating the hash value of the new URL; and traversing a malicious URL feature library, and performing contrast detection on feature data in the malicious URL feature library and the hash value of the URL to be detected. The invention further discloses a formalization detection system for the malicious URL. The technical scheme disclosed by the invention can be effectively used against the variability in the formats of the URL; and compared with the traditional URL detection method, the detection rate against the malicious URL which often changes the format is higher, and a single feature can also be adopted for corresponding to multiple format variants of the malicious URL, so that the volume of a virus feature library required for the detection method is smaller, and the space of a memory and a magnetic disk can be further saved.

Description

technical field [0001] The invention relates to the technical field of computer network security, in particular to a formal detection method and system for malicious URLs. Background technique [0002] According to the RFC specification, the grammatical format of URL (Uniform Resource Locator) is as follows: "scheme: / / username:passworddomain:port / path?query_string#fragment_id" (see: RFC1738 standard http: / / www.ietf.org / rfc / rfc1738 .txt), all URLs must follow this rule. If the protocol (scheme) part is omitted, it defaults to the HTTP protocol. The username and password (username:password) part can be omitted. In the HTTP protocol, the port number (port) The default is 80, which can also be omitted, and the fragment_id part has no practical value in detecting whether it is a malicious URL. According to the above characteristics of the URL format, it can be considered that the format of the URL is variable, and multiple URLs that are not exactly the same may point to the same...

AI Technical Summary

Problems solved by technology

[0003] Currently, malicious URL detection methods are all based on string matching. Security vendors collect a large number of malicious URLs and store them in the signature database. Part of the malicious URL detection problem, but due to the variability of the URL format mentioned above, a simple change of a malicious URL, without changing the nature of its malicious link, its content has been matched with the characteristics of the virus database It is not completely consistent, which

Images