Method, device, electronic device and storage medium for application protection status verification

By analyzing and verifying the status of the subdomain name protection of Internet applications, the problem of omission or failure of Internet application protection policies is solved, and protection of various types of attacks and real-time security monitoring is achieved to ensure enterprise data security.

CN117879877BActive Publication Date: 2024-11-12QIAN JIN NETWORK INFORMATION TECH SHANGHAI LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311689734.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-12-08
Publication Date
2024-11-12
Estimated Expiration
2043-12-08

AI Technical Summary

Technical Problem

After the Internet application went online, the protection policy was omitted or invalid due to unauthorized audits or improper operation, resulting in successful hacker attacks, resulting in enterprise data leakage and huge losses.

Method used

By resolving the DNS configuration file of the target first-level domain name, obtaining and verifying all subdomains associated with it, using the attack feature list to periodically verify the protection status of each subdomain, including XSS attack, SQL injection and command injection features, verifying feedback The content matches the response characteristics, determines the protection status, and obtains updated subdomain names through IPC filing information query and monitoring to ensure comprehensive protection.

Benefits of technology

It realizes comprehensive protection status verification for Internet applications, ensures that there are no subdomain names, can prevent multiple types of attacks, and can sense application protection in real time, prevent applications from being out of protection, and improve security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117879877B_ABST
    Figure CN117879877B_ABST
Patent Text Reader

Abstract

The present application discloses a method, device, electronic device and storage medium for verifying the application protection status. The method includes: parsing the DNS configuration file of the target first-level domain name to obtain all subdomains associated with the target first-level domain name; periodically verifying the validity of each subdomain based on one or more attack features in the attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features and command injection features; verifying whether one or more of the feedback contents matches one or more of the response features in the response feature list to obtain a matching result; and determining the protection status of each subdomain at least based on the matching result. The present application can timely verify whether the protection strategy is enabled for each subdomain, thereby improving the security performance of the domain name application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet security technology, and in particular to a method, device, electronic device, computer-readable storage medium, and computer program product for verifying application protection status. Background Art

[0002] In the current Internet environment, cyber attacks are increasing day by day, and hackers use various technical means to attack Internet applications. The databases of Internet applications store a large amount of corporate data, such as customer information, financial information, and business secrets. If corporate data is leaked, it will cause huge losses to the company. Therefore, the Internet needs to take protective measures to protect the security of Internet applications.

[0003] Internet application protection measures can effectively prevent hackers from attacking with various technical means. However, due to various reasons, Internet application protection fails. For example, because the application is not reviewed before it goes online, the application is omitted from the protection list and no protection deployment is performed; for example, a protection strategy is deployed when the application goes online, but the protection strategy is taken offline due to improper operation, accidental deletion, or application migration. Therefore, there is an urgent need for an application protection status verification method to verify the protection status of each application in real time. Summary of the invention

[0004] In view of this, embodiments of the present application provide a method, device, electronic device, computer-readable storage medium and computer program product for verifying application protection status, which are used to solve at least one technical problem.

[0005] An embodiment of the present application provides a method for verifying an application protection status, comprising: parsing a DNS configuration file of a target first-level domain name to obtain all subdomains associated with the target first-level domain name; periodically verifying the validity of each subdomain name based on one or more attack features in an attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features, and command injection features; verifying whether one or more of the feedback contents matches one or more response features in a response feature list to obtain a matching result; and determining the protection status of each subdomain name at least based on the matching result.

[0006] Optionally, according to the method of an embodiment of the present application, the target first-level domain name is obtained through IPC registration information query; the DNS configuration file in the target first-level domain name is parsed to obtain an A record and a CNAME record; and all subdomains associated with the target first-level domain name are obtained based on the A record and the CNAME record.

[0007] Optionally, according to the method of the embodiment of the present application, the target first-level domain name change is continuously monitored through IPC filing information query to obtain an updated full subdomain name.

[0008] Optionally, the method according to the embodiment of the present application further includes basic protection verification, and the basic protection verification includes: directly calling one or more attack features to launch an attack on each subdomain; wherein the IP address called for each attack is different.

[0009] Optionally, the method according to the embodiment of the present application further includes enhanced protection verification, which includes: obtaining one or more attack features; encoding one or more of the attack features to obtain one or more variant attack features; launching an attack on each subdomain name based on one or more of the variant attack features; wherein the IP address called for each attack is different.

[0010] Optionally, the method according to the embodiment of the present application further includes: if the content of one or more of the feedback partially matches one or more response features, determining a defect score based on the amount and importance of the non-matching content; determining a protection score by subtracting the defect score from the full score; and determining the protection status of the corresponding subdomain name based on the protection score.

[0011] Optionally, the method according to the embodiment of the present application further includes: allocating a weight coefficient according to the importance of the mismatched content; and determining a defect score according to the amount of the mismatched content and the allocated weight coefficient.

[0012] Optionally, according to the method of an embodiment of the present application, the protection status includes: no protection, effective protection and defective protection.

[0013] Optionally, according to the method of the embodiment of the present application, the attack feature also includes: one or more of a file upload feature, a deserialization feature, a file inclusion feature and a code injection feature.

[0014] An embodiment of the present application provides a device for verifying the application protection status, including: a parsing module, used to parse the DNS configuration file of a target first-level domain name to obtain all subdomain names associated with the target first-level domain name; a verification module, used to periodically verify the validity of each subdomain name based on one or more attack features in an attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features, and command injection features; a verification module, used to verify whether one or more of the feedback contents matches one or more response features in a response feature list to obtain a matching result; and a determination module, used to determine the protection status of each subdomain name at least based on the matching result.

[0015] Optionally, the device according to the embodiment of the present application further includes: an acquisition module, used to obtain the target first-level domain name through IPC registration information query; a configuration file parsing module, used to parse the DNS configuration file in the target first-level domain name to obtain an A record and a CNAME record; and a subdomain name acquisition module, used to obtain all subdomains associated with the target first-level domain name based on the A record and the CNAME record.

[0016] Optionally, the device according to the embodiment of the present application further includes: a monitoring module, configured to continuously monitor changes in the target first-level domain name through IPC filing information query to obtain an updated full subdomain name.

[0017] Optionally, the device according to the embodiment of the present application further includes: a basic protection verification module, which is used to directly call one or more attack features to launch an attack on each subdomain; wherein the IP address called for each attack is different.

[0018] Optionally, the device according to the embodiment of the present application also includes: an enhanced protection verification module, which is configured to include: an attack feature acquisition unit, which is configured to acquire one or more attack features; an encoding processing unit, which is configured to encode one or more of the attack features to obtain one or more variant attack features; an attack unit, which is configured to launch an attack on each subdomain name according to one or more of the variant attack features; wherein the IP address called for each attack is different.

[0019] Optionally, the device according to the embodiment of the present application further includes: a matching module, which is used to determine the defect score according to the number and importance of the unmatched content if one or more of the feedback contents partially match one or more of the response features; a protection score determination module, which is used to determine the protection score by subtracting the defect score from the full score; and a protection status determination module, which is used to determine the protection status of the corresponding subdomain name according to the protection score.

[0020] An embodiment of the present application provides an electronic device, which includes a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the steps of the method described above are implemented.

[0021] An embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the steps of the method described above are implemented.

[0022] An embodiment of the present application provides a computer program product, wherein the computer program product includes computer program instructions, and when the computer program instructions are executed by a processor, the steps of the method described above are implemented.

[0023] This application obtains all subdomains associated with the target first-level domain name by parsing the DNS configuration file of the target first-level domain name, which can ensure that there will be no problems with missing subdomains and achieve the purpose of comprehensive protection status verification. The attack feature list of this application includes multiple types of attack features, each type of attack feature can verify whether a protection strategy is enabled, and the attack features are subdivided into multiple types, which can ensure that the domain name application service can prevent multiple types of attacks. In addition, this application provides task scheduling capabilities, periodically monitors the protection status of domain name applications, can perceive the application protection status in real time, and ensure that no application is out of protection. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following briefly introduces the drawings in the embodiments of the present application.

[0025] Figure 1 It is a schematic diagram of the system architecture of an embodiment of the present application.

[0026] Figure 2 A flow chart of the application protection status verification method according to an embodiment of the present application is shown.

[0027] Figure 3 A flow chart of a domain name asset management method according to an embodiment of the present application is shown.

[0028] Figure 4 A flow chart of the application protection effectiveness verification method according to an embodiment of the present application is shown.

[0029] Figure 5 A schematic diagram of the feedback content interface of an embodiment of the present application is shown.

[0030] Figure 6 It is a structural block diagram of the application protection status verification device of an embodiment of the present application.

[0031] Figure 7 A schematic diagram of a parsing module according to an embodiment of the present application is shown.

[0032] Figure 8 A schematic diagram of a verification module according to an embodiment of the present application is shown.

[0033] Fig. 9 A schematic diagram of a determination module in an embodiment of the present application is shown.

[0034] Fig.10 A schematic diagram showing the hardware structure of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0035] The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that the purpose of providing these embodiments is to make the principles and spirit of the present application clearer and more thorough, so that those skilled in the art can better understand and implement the principles and spirit of the present application. The exemplary embodiments provided herein are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments herein, all other embodiments obtained by ordinary technicians of the art without creative work are within the scope of protection of this application.

[0036] Embodiments of the present application relate to terminal devices and / or servers. Those skilled in the art will appreciate that the embodiments of the present application may be implemented as a system, apparatus, device, method, computer-readable storage medium, or computer program product. Therefore, the present disclosure may be specifically implemented in at least one of the following forms: complete hardware, complete software, or a combination of hardware and software. According to the embodiments of the present application, the present application requests protection for a method, apparatus, electronic device, computer-readable storage medium, and computer program product for application protection status verification. Figure 1 A schematic diagram of a system architecture of an embodiment of the present application is shown. Figure 1 As shown, the system includes a terminal device 102 and a server 104. Among them, the terminal device 102 may include at least one of the following: a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart TV, various wearable devices, an augmented reality AR device, a virtual reality VR device, etc. A client can be installed on the terminal device 102. For example, the client can be a client that specifically performs a specific function (such as an application app), or a client with multiple application applets (different functions) embedded in it, or a client logged in through a browser. The user can operate on the terminal device 102. For example, the user can open the client installed on the terminal device 102 and input instructions through the client operation, or the user can open the browser installed on the terminal device 102 and input instructions through the browser operation. After the terminal device 102 receives the instruction input by the user, the request information containing the instruction is sent to the server 104. After receiving the request information, the server 104 performs corresponding processing and then returns the processing result information to the terminal device 102. The user instruction is completed through a series of data processing and information interaction.

[0037] In this document, terms such as first, second, third, etc. are only used to distinguish one entity (or operation) from another entity (or operation), but not to require or imply any order or relationship between these entities (or operations).

[0038] The following is a brief description of the concepts and technical terms that may be involved in the embodiments of the present application.

[0039] The Internet application in this application can be an application software that uses a browser to operate on the Internet or an enterprise intranet. An Internet application is an application program written in a web page language that can run on various computer platforms and mobile terminals.

[0040] Figure 2 A schematic diagram of a process flow of an application protection status verification method according to an embodiment of the present application is shown, and the method comprises the following steps:

[0041] S101: parsing a DNS configuration file of a target first-level domain name to obtain all subdomains associated with the target first-level domain name;

[0042] S102: Periodically verify the validity of each subdomain based on one or more attack features in the attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features, and command injection features;

[0043] S103: Verify whether one or more of the feedback contents match one or more of the response features in the response feature list to obtain a matching result;

[0044] S104: Determine the protection status of each subdomain at least according to the matching result.

[0045] One application service corresponds to one domain name. An enterprise often launches new application services, and accordingly, new domain names are added. One first-level domain name may be associated with multiple subdomains, which include N-level domain names, and N-level domain names include one or more of the second-level domain name, the third-level domain name, and the fourth-level domain name. Since all application services publish content through the DNS system, all subdomain names associated with the target first-level domain name can be obtained by parsing the DNS configuration file of the target first-level domain name, which can ensure that there will be no subdomain name omissions and achieve the purpose of comprehensive protection status verification.

[0046] The attack feature list of the present application includes multiple types of attack features, each type of attack feature can verify whether a protection strategy is enabled, and the attack features are subdivided into multiple types, which can ensure that the domain name application service can prevent multiple types of attacks. It should be noted that not every subdomain needs to be verified using all the attack features in the attack feature list. One or more attack features in the attack feature list can be selected for verification based on the business function, protection requirements and other conditions corresponding to the subdomain. For example, the business function of subdomain A is only to display web page content, and it does not have functions such as information input and output. Therefore, there is no need to perform protection verification of SQL injection features and command injection features, which can shorten the verification time and improve verification efficiency.

[0047] Furthermore, the present application performs periodic protection verification on each subdomain. The time unit of the period can be hours, days, weeks and months, for example, the period is any day from 1 to 10 days. The present application provides task scheduling capabilities, and periodically monitors the protection status of domain name applications. It can perceive the application protection status in real time to ensure that no application is out of protection. After the attack feature launches an attack, the corresponding feedback content will be obtained. If the feedback content matches the corresponding response feature in the response feature list, it is determined that the protection strategy has been enabled and the protection status of the corresponding subdomain is judged. The response feature list is stored in the verification device, and the response features in the response feature list correspond one-to-one to the attack features in the attack feature list.

[0048] According to an embodiment of the present application, optionally, it also includes: obtaining the target first-level domain name through IPC filing information query; parsing the DNS configuration file in the target first-level domain name to obtain A records and CNAME records; and obtaining all subdomains associated with the target first-level domain name based on the A record and CNAME record. Further, continuously monitoring the changes of the target first-level domain name through IPC filing information query to obtain the updated full subdomain name.

[0049] All external businesses of enterprises need to be registered with ICP based on compliance requirements. By capturing the first-level domain name information of the enterprise's ICP registration, the enterprise's enterprise domain name list can be fully obtained. All domain name applications need to go through the DNS service when they are published to the Internet. Therefore, by parsing the A record and CNAME record in the configuration information of the DNS service, the second-level domain name list can be fully obtained to ensure that no domain name is missed. Furthermore, this application will also periodically detect changes in ICP registration information and changes in the first-level domain name in the enterprise's ICP registration, so that it can respond quickly to new domain names and effectively manage the comprehensiveness of domain names.

[0050] According to an embodiment of the present application, optionally, basic protection verification is further included, and the basic protection verification includes: directly calling one or more attack features to launch an attack on each subdomain; wherein the IP address called for each attack is different. Basic protection verification is to directly call the attack feature to launch an attack. There is no requirement for the ability to encode and parse subdomains, and it tests the primary protection capabilities of subdomains. In the process of determining the protection status, if the same request source IP is used to send a certain amount of attack packets to the same domain name or application, the source IP may be blocked by the application protection, and any subsequent requests will trigger protection, resulting in inaccurate protection status determination. Therefore, the above problems can be avoided by calling different IP addresses through a proxy pool (dynamic IP) during each attack.

[0051] According to an embodiment of the present application, optionally, it further includes: enhanced protection verification, which includes: obtaining one or more attack features; encoding one or more of the attack features to obtain one or more variant attack features; launching an attack on each subdomain according to one or more variant attack features; wherein the IP address called for each attack is different. Enhanced protection verification tests whether the subdomain has the ability to encode and parse variant attack features. During the attack process, due to the existence of protective measures, hackers may hide or mutate the attack features by encoding to bypass the protective measures. Therefore, when the security requirements of some application services are high, enhanced protection verification can be performed. In addition, both basic protection verification and enhanced protection verification can be performed on the same domain name to achieve multiple levels of protection. Among them, the encoding method for the attack feature includes base64 encoding. Furthermore, the present application can also customize and add new encoding methods according to the update of the encoding method to achieve the ability to parse multiple encoding methods and improve security.

[0052] According to an embodiment of the present application, optionally, it further includes: if one or more of the feedback contents partially match one or more of the response features, then the defect score is determined according to the number and importance of the non-matching contents; the protection score is determined by subtracting the defect score from the full score; and the protection status of the corresponding subdomain is determined according to the protection score. Among them, the weight coefficient is assigned according to the importance of the non-matching contents; and the defect score is determined according to the number of non-matching contents and the assigned weight coefficient.

[0053] When determining the defect score, this application also refers to the number and importance of mismatched content, which can avoid the problem that a certain important response feature is ignored because the defect score is not prominent, resulting in huge losses to the application service. Therefore, different weight coefficients are assigned according to the importance of the mismatched content, and the calculated protection score can scientifically and reasonably reflect the safety factor of the corresponding domain name.

[0054] According to an embodiment of the present application, optionally, the protection status includes: no protection, effective protection and defective protection. Among them, the protection score corresponding to no protection is 0 points, the score corresponding to effective protection is full marks, and the score corresponding to defective protection is any score between 0 and full marks.

[0055] According to an embodiment of the present application, optionally, the attack feature also includes: one or more of a file upload feature, a deserialization feature, a file inclusion feature, and a code injection feature. In order to further refine the types of attack features, the attack features of the present application may also include: one or more of a file upload feature, a deserialization feature, a file inclusion feature, and a code injection feature. In addition, the present application may customize and add new attack features to cope with attacks of new attack features.

[0056] The above describes the implementation method and advantages of the embodiments of the present application through multiple embodiments. The following describes the specific processing process of the embodiments of the present application in detail with reference to specific examples. This application takes a recruitment company as an example. The company's recruitment information and the resume information of the applicants are stored in the server of the recruitment company. Once a leak occurs, it will cause huge losses to the company and users. Therefore, the server security protection requirements of the recruitment company are relatively high, and the effectiveness of the protection needs to be verified in real time.

[0057] Figure 3 FIG. 1 is a flow chart showing a domain name asset management method according to an embodiment of the present application. Figure 3 As shown, the domain name management method can be executed by the domain name asset management module 300, and the domain name management method includes:

[0058] S301, obtain the enterprise's first-level domain name through ICP filing information query;

[0059] S302, obtaining the location of the first-level domain name DNS server through internal interviews and surveys within the enterprise;

[0060] S303, parsing all A records and CNAME records in the first-level domain name DNS configuration file;

[0061] S304, format and output the list of secondary domain names;

[0062] S305, storing and determining whether the domain name exists in the enterprise domain name asset table;

[0063] S306, if not stored, store it into the warehouse; if it exists, end this method.

[0064] S307, continuously monitor the changes of the first-level domain names in the enterprise ICP record;

[0065] S308, if there is a new domain name in the first-level domain name, execute S302-306; if there is, end this method.

[0066] Enterprises' external businesses need to be registered with ICP for compliance purposes. By capturing the first-level domain name information of the enterprise's ICP registration, the enterprise's enterprise domain name list can be fully obtained. By continuously testing the ICP registration information, new domain names can be quickly responded to to ensure effective domain name management. Since all domain name applications need to be published on the Internet through the DNS service, the second-level domain name list can be fully obtained by parsing the CNAME record and A record in the configuration information of the DNS service to ensure that no domain name is missed.

[0067] This application obtains the first-level domain name of the enterprise by querying the enterprise ICP filing information, and then directly extracts the full amount of second-level or N-level domain names through the configuration of the DNS service of the first-level domain name to ensure that all subdomains associated with it are obtained. By periodically capturing the first-level domain name information of ICP filing and DNS service configuration information, it is possible to monitor in real time whether there are new application releases and promptly verify the protection effectiveness of new applications.

[0068] An example of a CNAME record is: danone IN CNAME 51co.51job.com;

[0069] An example of an A record is: essential IN A 58.111.111.111.

[0070] As an example, the enterprise domain name asset table is shown in Table 1 below:

[0071] Table 1

[0072] Company Name First-level domain name Second level domain name XXX Co., Ltd. Test01.com www.test01.com XXX Co., Ltd. Test01.com Job.test01.com XXX Co., Ltd. Test02.com www.test02.com ..... ..... .....

[0073] Figure 4 The flowchart of the application protection validity verification method of the embodiment of the present application is shown. The application protection validity verification method is mainly completed by the domain name application protection verification request module 400, the domain name application protection verification module 500, and the domain name application protection rating module 600. The method executed by the domain name application protection verification request module 400 includes:

[0074] S401, calling the browser access engine to initiate access to the subdomain name in the enterprise domain name asset table;

[0075] S402, verifying whether the access response returned is reachable;

[0076] If it is reachable, execute S403 to mark the domain name as valid and with a protection level to be determined (the score is 100 by default);

[0077] If it is unreachable, execute S404, mark the domain name as invalid, and the protection level is not applicable to the two marks;

[0078] Optionally, S405, basic protection verification is performed on the attack features in the "attack feature list" of the basic protection level for the access URL of the domain name one by one;

[0079] S406, calling the IP proxy pool to switch IP access;

[0080] Optionally, S407, performing enhanced protection verification on the attack features in the "attack feature list" of the enhanced protection level for the access URL of the domain name one by one;

[0081] S408, calling the IP proxy pool to switch IP access.

[0082] like Figure 4 As shown, the attack feature list includes one or more of: XSS attack features, file upload features, deserialization features, file inclusion features, SQL injection features, code injection features, and command injection features. As attack features evolve and update, new features can also be customized and added to the attack feature list, so that the protection verification items keep pace with the times.

[0083] Basic protection verification is to directly call the original attack signature in the attack signature list to attack the accessed domain name. Each time an attack is made, a different IP address is used for access. The original attack signature is the attack signature without any variation or hiding. For example, the original attack signature is as follows:

[0084] XSS attack characteristics: value = <script>alert(1)< / script> ;

[0085] SQL injection characteristics: value = where% 201 = 1;

[0086] Command injection characteristics: value = eval (phpinfo ());

[0087] Enhanced protection verification is to encode the original attack features in the attack feature list and use the encoded attack features to attack the domain name. During the attack process, due to the existence of protection, it is often necessary to hide the attack features through encoding, which requires the protection system to have the ability to parse the encoding and variants. For example, the attack features encoded by base64 are as follows:

[0088] XSS attack characteristics: value= <script>alert(1)< / script> ;

[0089] Encoded XSS attack characteristics:

[0090] value=PHNjcmlwdD5hbGVydCgxKTwvc2NyaXB0Pg==;

[0091] SQL injection characteristics: value = where% 201 = 1;

[0092] The encoded SQL injection feature: value=d2hlcmUlMjAxPTE=.

[0093] The method performed by the domain name application protection verification module 500 includes:

[0094] S501, obtaining a response code and response content in the access request feedback content;

[0095] S502, verifying whether the content matches the protection feature list;

[0096] If there is a match, S503 is executed and the domain name protection score is not increased or decreased;

[0097] If there is no match, execute S504 and deduct (1 / total number of feature lists)×100 from the domain name protection score.

[0098] Figure 5 A schematic diagram of the feedback content interface of an embodiment of the present application is shown. Figure 4 and Figure 5 , the feedback content includes the response code and the response content. The feedback content corresponding to different application firewalls is stored in the local protection response feature list. The application firewalls include: Changting Technology Application Firewall, Alibaba Cloud Application Firewall, Green Alliance Technology Application Firewall and one or more of the self-developed application firewalls. Each firewall corresponds to a feedback content. For example, the response code corresponding to the Alibaba Cloud Application Firewall is: "405"; the response content is: "Sorry, your access is blocked because the URL you visited may pose a security threat to the website." The feedback content can be used to determine the type of application firewall.

[0099] The response code and response content can be extracted from the access request interface. If they match the information in the response feature list, it means that the application firewall has enabled the protection function, and no points will be deducted from the full score. If they do not match the information in the response feature list, it means that the application firewall has not enabled the protection function for this attack or the protection is ineffective, and points will be deducted from the full score technology.

[0100] According to an embodiment of the present application, the protection score is calculated using the following formula:

[0101] T=T0-T d (1)

[0102]

[0103] Where T is the protection score, T0 is the initial score (the default is 100 points), T d is the defect score, n is the total number of items in the protection verification, and w is the number of items whose feedback content does not match the information in the response checklist.

[0104] For example, five attack features in the attack feature list are selected to verify the effectiveness of protection for subdomain A. Two of the attack feature feedback contents do not match the information in the response list. The initial score is 100 points. The calculation results according to formulas (1) and (2) are as follows:

[0105]

[0106] T=100-40=60

[0107] As can be seen from the above, the protection score of this protection effectiveness verification is 60. Formulas (1) and (2) evenly distribute the initial score to multiple attack features, and each attack feature has the same score. However, some attack features correspond to relatively serious vulnerabilities. Once there are no protective measures for the vulnerabilities, the consequences for the enterprise are fatal. Therefore, the protection score calculated according to the above method cannot objectively experience the security of the domain name application. Therefore, improvements have been made on the basis of formulas (1) and (2), and the improved formulas are as follows:

[0108] T=T0-T d ; (3)

[0109]

[0110]

[0111] Where T is the protection score, T0 is the initial score (the default is 100 points), T d is the defect score, n is the total number of protection verification items, w is the number of items that do not match the information in the feedback list, s i is the weight coefficient corresponding to the feedback content.

[0112] Among them, s i The larger the value, the more important the attack feature corresponding to the feedback content is. i The calculated protection score can objectively reflect the security performance of the corresponding domain application service. For example, select 5 attack features in the attack feature list to verify the effectiveness of protection for subdomain A. The 5 attack features are: XSS attack feature, SQL injection feature, command injection feature, deserialization feature and file upload feature. Among them, the feedback content of XSS attack feature and deserialization feature does not match the information in the response list. The initial score is 100 points. The weight coefficients assigned to the 5 attack features are as shown in Table 2:

[0113] Table 2

[0114]

[0115]

[0116] According to formulas (3), (4) and (5), the calculation results are as follows:

[0117]

[0118] T = 100-42 = 58

[0119] From the above, we can see that the protection score of this protection effectiveness verification is 58.

[0120] The method performed by the domain name application protection rating module 600 includes:

[0121] Optionally, perform S601, basic protection level scoring;

[0122] S602, scoring and determination;

[0123] If the score is 100, execute S603 and the domain name protection level is marked as basic protection;

[0124] If the score is 0, S604 is executed and the domain name protection level is marked as no effective protection;

[0125] If the score is between 0 and 100, execute S605 and the domain name protection level is marked as defective basic protection;

[0126] Optionally, executing S606 to enhance the protection level score;

[0127] S607, scoring and determination;

[0128] If the score is 100, execute S608 and the domain name protection level is marked as enhanced protection;

[0129] If the score is 0, S609 is executed and the domain name protection level is marked as no enhanced protection;

[0130] If the score is between 0 and 100, S610 is executed and the domain name protection level is marked as enhanced protection of defects.

[0131] According to the embodiments of the present application, the basic protection of defects and / or the enhanced protection of defects can also be graded in detail, for example, they can be divided into level one defects, level two defects and level three defects according to the value of the protection score. The higher the defect level, the lower the protection score, which means the lower the safety performance, for reference by staff to take remedial measures of the corresponding level.

[0132] This application is based on the protection requirements of domain name applications and is divided into two verification methods: basic protection and enhanced protection. Basic protection and enhanced protection call different attack features and encoding methods to initiate requests to the application, and determine the protection results by collecting the response features of different types of real-time protection systems. If some domain name applications only have basic protection capabilities, they can only perform the basic protection verification steps. If they have both basic protection capabilities and enhanced protection capabilities, they can perform both basic protection verification steps and enhanced protection verification steps. In this way, it can adapt to the work of protecting the effectiveness of various types of domain name applications.

[0133] According to an embodiment of the present application, the domain name application protection status is output according to the domain name protection level. There are two ways to classify the protection status. Method 1: The protection status includes: no protection, effective protection and defective protection. Method 2: The protection status includes: basic protection and enhanced protection. Basic protection includes perfect and defective. Enhanced protection includes: perfect, defective and no protection. Multiple classification methods can use the requirements of multiple applications to achieve fine rating of protection status.

[0134] Corresponding to the method embodiment of the present application, the present application also provides an application protection status verification device, such as Figure 6 As shown, the application protection status verification device 100 includes:

[0135] A parsing module 110, configured to parse a DNS configuration file of a target first-level domain name to obtain all subdomains associated with the target first-level domain name;

[0136] A verification module 120, configured to periodically verify the validity of each subdomain based on one or more attack features in the attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of an XSS attack feature, an SQL injection feature, and a command injection feature;

[0137] A verification module 130 is used to verify whether one or more of the feedback contents matches one or more of the response features in the response feature list to obtain a matching result; and

[0138] The determination module 140 is used to determine the protection status of each subdomain at least according to the matching result.

[0139] According to an embodiment of the present application, the parsing module 110 further includes: an acquisition module 111, a configuration file parsing module 112, a subdomain acquisition module 113 and a monitoring module 114. Figure 7 , Figure 7 The schematic diagram of the parsing module of the embodiment of the present application is shown. The acquisition module 111 is used to obtain the target first-level domain name through IPC filing information query; the configuration file parsing module 112 is used to parse the DNS configuration file in the target first-level domain name to obtain the A record and the CNAME record; the subdomain acquisition module 113 is used to obtain all subdomains associated with the target first-level domain name based on the A record and the CNAME record; the monitoring module 114 is used to continuously monitor the changes of the target first-level domain name through IPC filing information query to obtain the updated full subdomain name.

[0140] According to an embodiment of the present application, the verification module 120 further includes a basic protection verification module 121 and an enhanced protection verification module 122. Figure 8 , Figure 8A schematic diagram of the verification module of an embodiment of the present application is shown. The basic protection verification module 121 is used to directly call one or more attack features to launch an attack on each subdomain; wherein, the IP address called for each attack is different. The enhanced protection verification module 122 includes: an attack feature acquisition unit 1221, an encoding processing unit 1222, and an attack unit 1223. The attack feature acquisition unit 1221 is configured to acquire one or more attack features; the encoding processing unit 1222 is configured to encode one or more of the attack features to obtain one or more variant attack features; the attack unit 1223 is configured to launch an attack on each subdomain according to one or more of the variant attack features; wherein, the IP address called for each attack is different.

[0141] According to an embodiment of the present application, the determination module 140 further includes a matching module 141, a protection score determination module 142 and a protection status determination module 143. Fig. 9 , Fig. 9 A schematic diagram of a determination module of an embodiment of the present application is shown. A matching module 141 is used to determine a defect score according to the number and importance of unmatched content if one or more of the feedback contents partially match one or more of the response features; a protection score determination module 142 is used to determine a protection score by subtracting the defect score from the full score; and a protection status determination module 143 is used to determine the protection status of the corresponding subdomain name according to the protection score.

[0142] The electronic device in the embodiment of the present application may be a user terminal device, a server, other computing devices, or a cloud server. Fig.10 A schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application is shown. The electronic device may include a processor 601 and a memory 602 storing computer program instructions. When the processor 601 executes the computer program instructions, the process or function of any of the above-mentioned embodiments of the method is implemented.

[0143] Specifically, the processor 601 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application. The memory 602 may include a large-capacity memory for data or instructions. For example, the memory 602 may be at least one of the following: a hard disk drive (HDD), a read-only memory (ROM), a random access memory (RAM), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a tape, a universal serial bus (USB) drive or other physical / tangible memory storage device. For another example, the memory 602 may include a removable or non-removable (or fixed) medium. For another example, the memory 602 may be inside or outside the integrated gateway disaster recovery device. The memory 602 may be a non-volatile solid-state memory. In other words, the memory 602 usually includes a tangible (non-transitory) computer-readable storage medium (such as a memory device) encoded with computer-executable instructions, and when the software is executed (such as executed by one or more processors), the operation described in the method of the embodiment of the present application can be performed. The processor 601 implements the process or function of any method in the above embodiments by reading and executing the computer program instructions stored in the memory 602.

[0144] In one example, Fig.10 The electronic device shown may also include a communication interface 603 and a bus 610. Among them, the processor 601, the memory 602, and the communication interface 603 are connected through the bus 610 and complete the communication between each other. The communication interface 603 is mainly used to realize the communication between each module, device, unit and / or device in the embodiment of the present application. The bus 610 includes hardware, software or both, and can couple the components of the online data traffic billing device to each other. For example, the bus may include at least one of the following: an accelerated graphics port (AGP) or other graphics bus, an enhanced industrial standard architecture (EISA) bus, a front-end bus (FSB), a hypertransport (HT) interconnect, an industrial standard architecture (ISA) bus, an infinite bandwidth interconnect, a low pin count (LPC) bus, a memory bus, a micro channel architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a video electronics standard association local (VLB) bus or other suitable buses. The bus 610 may include one or more buses. Although the embodiments of the present application describe or illustrate a specific bus, the embodiments of the present application may consider any suitable bus or interconnection method.

[0145] In combination with the method in the above embodiments, an embodiment of the present application also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the process or function of any method in the above embodiments is implemented.

[0146] In addition, an embodiment of the present application further provides a computer program product, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the process or function of any one of the methods in the above embodiments is implemented.

[0147] The above exemplarily describes the flowcharts and / or block diagrams of the methods, devices, systems and computer program products of the embodiments of the present application, and describes the relevant various aspects. It should be understood that each box or combination thereof in the flowchart and / or block diagram can be implemented by computer program instructions, or by dedicated hardware that performs a specified function or action, or by a combination of dedicated hardware and computer instructions. For example, these computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to form a machine that enables these instructions executed by such a processor to enable the implementation of the functions / actions specified in each box or combination thereof in the flowchart and / or block diagram. Such a processor can be a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.

[0148] The functional blocks shown in the structured block diagram of the embodiment of the present application can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc.; when implemented in software, it is a program or code segment used to perform the required task. The program or code segment can be stored in a memory, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0149] It should be noted that the present application is not limited to the specific configurations and processes described above or shown in the figures. The above is only a specific implementation mode of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the described system, device, module or unit can refer to the corresponding process in the method embodiment without further description. It should be understood that the scope of protection of the present application is not limited to this. Any technician familiar with the technical field can think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application.

Claims

1. A method for verifying application protection status, characterized in that: include: Parsing the DNS configuration file of the target first-level domain name to obtain all subdomains associated with the target first-level domain name, which includes: obtaining the target first-level domain name through ICP filing information query; parsing the DNS configuration file in the target first-level domain name to obtain A records and CNAME records; and obtaining all subdomains associated with the target first-level domain name based on the A record and the CNAME record; Periodically verify the validity of each subdomain based on one or more attack features in the attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features, and command injection features; Verify whether one or more of the feedback contents matches one or more of the response features in the response feature list to obtain a matching result; and Determining a protection status of each subdomain at least based on the matching result; It further includes basic protection verification and enhanced protection verification, and the basic protection verification includes: Directly call one or more attack features to attack each subdomain; the IP address called for each attack is different; The enhanced protection verification includes: obtaining one or more attack features; encoding one or more attack features to obtain one or more variant attack features; launching an attack on each subdomain according to one or more variant attack features; wherein the IP address called for each attack is different; If one or more of the feedback contents partially match one or more of the response features, a defect score is determined based on the amount and importance of the unmatched contents; a protection score is determined by subtracting the defect score from the full score; and a protection status of the corresponding subdomain is determined based on the protection score.

2. The method according to claim 1, characterized in that The target first-level domain name changes are continuously monitored through ICP filing information query to obtain the updated full subdomain name.

3. The method according to claim 1, characterized in that Further including: Assign weight coefficients according to the importance of the mismatched content; The defect score is determined based on the number of mismatches and the assigned weight factor.

4. The method according to claim 3, characterized in that The protection status includes: no protection, effective protection and defective protection.

5. The method according to claim 1, characterized in that The attack features also include: one or more of: a file upload feature, a deserialization feature, a file inclusion feature, and a code injection feature.

6. A device for verifying application protection status, characterized in that: include: A parsing module, used for parsing a DNS configuration file of a target first-level domain name to obtain all subdomains associated with the target first-level domain name; A verification module, used to periodically verify the validity of each subdomain based on one or more attack features in the attack feature list to obtain one or more feedback contents, wherein the attack features include: one or more of XSS attack features, SQL injection features, and command injection features; A verification module, used to verify whether one or more of the feedback contents matches one or more of the response features in the response feature list to obtain a matching result; and A determination module, configured to determine a protection status of each subdomain at least according to the matching result; Further comprising: an acquisition module, configured to acquire the target first-level domain name through ICP filing information query; A configuration file parsing module, used to parse the DNS configuration file in the target first-level domain name to obtain an A record and a CNAME record; and A subdomain acquisition module, used for acquiring all subdomains associated with the target first-level domain name based on the A record and the CNAME record; A basic protection verification module, which is used to directly call one or more attack features to launch an attack on each subdomain; wherein the IP address called for each attack is different; It also includes: an enhanced protection verification module, which is configured to include: an attack feature acquisition unit, which is configured to acquire one or more attack features; an encoding processing unit, which is configured to encode one or more of the attack features to obtain one or more variant attack features; an attack unit, which is configured to launch an attack on each subdomain according to one or more variant attack features; wherein the IP address called for each attack is different; It also includes: a matching module, which is used to determine the defect score according to the number and importance of the unmatched content if one or more of the feedback content partially matches one or more of the response features; a protection score determination module, which is used to determine the protection score by subtracting the defect score from the full score; and a protection status determination module, which is used to determine the protection status of the corresponding subdomain name according to the protection score.

7. The device for verifying application protection status according to claim 6, characterized in that: Also includes: The monitoring module is used to continuously monitor the changes of the target first-level domain name through ICP filing information query to obtain the updated full subdomain name.

8. An electronic device, characterized in that: The electronic device comprises: a processor and a memory storing computer program instructions; when the electronic device executes the computer program instructions, the method according to any one of claims 1 to 5 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented.