Determination device, determination method, and determination program
Patent Information
- Application Number
- JP2023514299
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-04-16
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-04-16
Smart Images

Figure 0007593483000001 
Figure 0007593483000002 
Figure 0007593483000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a determination device, a determination method, and a determination program for determining whether an attack is successful. [Background technology]
[0002] Conventionally, techniques have been proposed for detecting attacks on web servers and the like. However, if an alert is issued upon detecting all attacks, there is a possibility that a maintenance worker or a monitor may miss the alert. Therefore, it is preferable to issue an alert only when an attack is successful. Conventionally, there is a technique for determining whether an attack has been successful by inspecting the response when an attack is made on a web server or the like (see Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 6708794 Summary of the Invention [Problem to be solved by the invention]
[0004] However, the conventional technology is based on the premise that traces of an attack appear in a response when an attack is made on a web server, etc. Therefore, for attacks in which traces of an attack do not explicitly appear in a response, for example, as shown below, it is not possible to determine whether an attack has been successful or not.
[0005] [Example 1: Authentication bypass] For example, suppose that the web application / login.php has an SQL injection vulnerability and is subject to the following attack:
[0006] GET / login.php?id=admin&pw=1' OR 1=1 <title>Login successful! Welcome admin< / title>
[0007] If this attack is successful, the attacker can log in as admin without knowing the admin user password. Even if this attack is successful, no traces of the attack will appear in the response content.
[0008] [Example 2: Information leakage] For example, suppose a web application that displays personal information, / show.php, has an SQL injection vulnerability and is subject to the following attack.
[0009] GET / show.php?id=alice&pw=1' OR 1=1 alice / tel: 12345678 / alice@example.com admin / tel: 23456789 / admin@example.com
[0010] If this attack is successful, the attacker will not only be able to view Alice's information, but will also be able to view information other than Alice's without knowing the password. Even if this attack is successful, no traces of the attack will appear in the response content.
[0011] In addition, all of the above attacks target vulnerabilities in the functions of web applications, and the damage caused by the attacks varies depending on the functions of the web application, making it difficult to determine whether the attacks were successful.
[0012] Therefore, an object of the present invention is to solve the above-mentioned problems and to determine whether an attack has been successful even if the damage caused by the attack varies depending on the functions of a web application. [Means for solving the problem]
[0013] In order to solve the above-mentioned problems, the present invention is characterized in that it includes an attack detection unit that detects attacks in which damage varies depending on the function of the requested web application using the requested URL of a communication log that is the target of the attack detection, and identifies the presence or absence of a login form in the requested URL, the response size to the request, and a status code from the communication log in which the attack was detected; a success / failure determination unit that determines whether the attack is successful or not using at least one of the presence or absence of a login form in the requested URL, the response size to the request, and the status code for the communication log in which the attack was detected; and a determination result output unit that outputs the result of the determination. Effect of the Invention
[0014] According to the present invention, it is possible to determine whether an attack has been successful even if the damage caused by the attack varies depending on the function of the web application that is the target of the attack. [Brief description of the drawings]
[0015] [Figure 1] FIG. 1 is a diagram for explaining an outline of the operation of the determination device. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of the determination device. [Diagram 3] FIG. 3 is a diagram showing an example of the first communication log and a function profile in FIG. [Figure 4] FIG. 4 is a diagram showing an example of the detection data of FIG. [Diagram 5] FIG. 5 is a diagram showing an example of a result of the determination device as to whether an attack is successful or not. [Figure 6] FIG. 6 is a flowchart illustrating an example of a processing procedure for the determination device to create a function profile. [Figure 7] FIG. 7 is a flowchart illustrating an example of a processing procedure when the determination device determines whether an attack is successful. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a system including a determination device. [Figure 9]FIG. 9 is a diagram illustrating an example of the configuration of a computer that executes a determination program. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] Hereinafter, a mode (embodiment) for carrying out the present invention will be described with reference to the drawings. The present invention is not limited to the embodiment described below.
[0017] [overview] An overview of the determination device 10 of this embodiment will be described with reference to Fig. 1. For example, first, the determination device 10 acquires a communication log to a web server equipped with a web application. Then, the determination device 10 detects an attack request of an attack that causes different damage depending on the function of the web application from the communication log using a prepared attack detection signature or the like. After that, the determination device 10 determines whether the attack is successful or not using a status code, a response, etc. of the response to the detected attack request.
[0018] Here, an example will be described in which requests to the web server are indicated by reference numerals 101 and 102, the status code for the request indicated by reference numeral 101 is "302", and the response size for the request indicated by reference numeral 102 is "10000".
[0019] In this case, the determination device 10 identifies the request indicated by reference symbol 101 as an authentication bypass attack using an attack detection signature (for example, "OR.*=.*#") whose damage varies depending on the function of the web application, and determines that the attack was successful based on the status code ("302"). The determination device 10 also identifies the request indicated by reference symbol 102 as an information leakage attack using an attack detection signature whose damage varies depending on the function of the web application, and determines that the attack was successful based on the response size ("10000").
[0020] According to the determination device 10, it is possible to determine whether an attack has been successful or not even if the damage caused by the attack varies depending on the function of the web application targeted by the attack.
[0021] [Configuration example] Next, a configuration example of the determination device 10 will be described. The determination device 10 includes a storage unit 11 and a control unit 12. The storage unit 11 stores data referenced by the control unit 12 when executing various processes and data generated by the execution of various processes.
[0022] For example, the storage unit 11 stores a first communication log which is a communication log used to create a function profile, a second communication log which is a communication log targeted for attack detection, a function profile (details will be described later) created by the control unit 12, detection data (details will be described later), determination result data on whether the attack was successful, etc. The first communication log and the second communication log are input via, for example, an input / output unit (not shown) of the determination device 10.
[0023] The first communication log includes, for example, the URL of the communication request destination, the status code for the request, the response size, the content of the response, etc., as shown in Fig. 3. The second communication log also includes the same information as above.
[0024] The control unit 12 is responsible for controlling the entire determination device 10. The control unit 12 includes a functional profile creation unit 121, an attack detection unit 122, a success / failure determination unit 123, and a determination result output unit .
[0025] The functional profile creation unit 121 creates profile information (functional profile) for each function of the web application based on the communication log of normal communication between an external device and a web application, the profile information indicating information such as the presence or absence of a login form and the range of response sizes.
[0026] For example, the function profile creation unit 121 extracts communication logs of normal communications (communications other than attacks) from the first communication log shown in Fig. 3. For example, the function profile creation unit 121 acquires communication logs (No. 1, 2, 3) that were not detected as attacks by the attack detection unit 122 from the first communication log shown in Fig. 3.
[0027] Then, the function profile creation unit 121 creates a function profile indicating information such as the presence or absence of a login form, the range of response sizes, and related request numbers for each identification information (profile ID) of a function of the web application. The function profile creation unit 121 stores the created function profile in the storage unit 11.
[0028] For example, the function profile shown in Figure 3 indicates that / login.php of a web application has a login form, and the normal response size range for a request to this function is [0, 100]. It also indicates that the related request is [1, 3].
[0029] Also, / show.php of the web application does not have a login form, and the normal response size range for a request to the function is [0,100]. Also, the related request is [2].
[0030] Returning to the description of Fig. 2, the attack detection unit 122 detects a communication log of an attack causing different damage depending on the function of the web application of the request destination, using the URL of the request destination in the communication log shown in the second communication log.
[0031] For example, if the attack detection signature is the regular expression "OR.*=.*#", the attack detection unit 122 detects communication logs shown in the second communication log in which the requested URL contains "OR.*=.*#" as communication logs of an attack in which the damage varies depending on the function of the web application.
[0032] As an example, the attack detection unit 122 detects communication logs No. 4, 5, and 6 in the second communication log as attack communication logs using the regular expression "OR.*=.*#" as the attack detection signature (see FIG. 4). Then, the attack detection unit 122 stores in the storage unit 11 as detection data information that associates the communication log No. in which the attack was detected (identification information) with the target location where the attack was detected (for example, the location in the requested URL that matches the attack detection signature) and the content of the attack.
[0033] The attack detection signature used by the attack detection unit 122 to detect an attack may be the regular expression "OR (1|'t') (#|--)" or the regular expression ".+['"] (#|--)".
[0034] Returning to the explanation of Fig. 2, the success / failure determination unit 123 determines whether the attack has been successful or not based on at least one of the presence or absence of a login form in the requested URL, the response size, and the status code for the communication log detected by the attack detection unit 122 as the communication log of the attack.
[0035] For example, the success / failure determination unit 123 determines whether the attack is successful or not by comparing the communication log detected by the attack detection unit 122 as an attack communication log with the presence or absence of a login form in the requested URL and the response size, and the functional profile information (see Figure 3).
[0036] The success / failure determining unit 123 determines whether the attack is successful or not based on, for example, the detection data and the function profile information (see FIG. 3) and the following two conditions.
[0037] (1) If the URL of the request destination in the communication log in which the attack was detected has a login form and the status code for the request is a 30X number (any of 300 to 309) indicating successful login, the success / failure determination unit 123 determines that the authentication bypass attack was successful. If not, the success / failure determination unit 123 determines that the attack failed.
[0038] (2) If the request destination URL in the communication log where the attack was detected does not have a login form and the response size to the request significantly exceeds the range of normal response sizes, the success / failure determination unit 123 determines that the attack aimed at leaking information has been successful. If not, the success / failure determination unit 123 determines that the attack has failed.
[0039] Whether or not the response size significantly exceeds the range of normal response sizes is determined, for example, by calculating the standard deviation σ of the response size and determining whether or not the response size in the communication log in which the attack was detected exceeds n×σ, where n is a constant designated by the user of the determination device 10. For example, n=3σ.
[0040] For example, the communication log shown in No. 4 in FIG. 5 is an attack on / login.php of the web application. Therefore, the success / failure determination unit 123 checks whether or not a login form is present in the URL of the request destination (attack destination) of the communication log, based on the function profile (see FIG. 3) of / login.php of the web application. Since the URL of the request destination of this communication log has a login form, the success / failure determination unit 123 determines that the communication log is an attack attempting authentication bypass. Next, when the success / failure determination unit 123 checks the status code of the communication log, it is 302. That is, it is a 30X number (any of 300 to 309) indicating a redirect (that is, successful login). Therefore, the success / failure determination unit 123 determines that the attack attempting authentication bypass has succeeded.
[0041] The communication log indicated by No. 5 in FIG. 5 is also an attack against / login.php of the web application. Therefore, the success / failure determination unit 123 checks whether or not a login form is present in the URL of the request destination (attack destination) of the communication log, based on the function profile (see FIG. 3) of / login.php of the web application. Since the URL of the request destination of this communication log has a login form, the success / failure determination unit 123 determines that the communication log is an attack attempting authentication bypass. Next, when the success / failure determination unit 123 checks the status code of the communication log, it is 200. In other words, it is not a 30X number (any of 300 to 309) indicating a redirect (i.e., successful login). Therefore, the success / failure determination unit 123 determines that the attack attempting authentication bypass has failed.
[0042] Furthermore, the communication log shown in No. 6 in FIG. 5 is an attack on / show.php of the web application. Therefore, the success / failure determination unit 123 checks whether or not a login form is present in the URL of the request destination (attack destination) of the communication log, based on the functional profile of / show.php of the web application (see FIG. 3). Since there is no login form in the URL of the request destination of this communication log, the success / failure determination unit 123 determines that the communication log is an attack aiming at information leakage. Next, when the success / failure determination unit 123 checks the response size of the communication log, it is 10000. This response size significantly exceeds the normal response size range ([0, 100]) indicated in the functional profile of / show.php of the web application. Therefore, the success / failure determination unit 123 determines that the attack aiming at information leakage has succeeded.
[0043] Returning to the explanation of Fig. 2, the determination result output unit 124 outputs the determination result by the success / failure determination unit 123. For example, the determination result output unit 124 outputs the determination result of what kind of attack was made against which function of a web application and whether the attack was successful or not. As one example, the determination result output unit 124 outputs whether an attack aimed at bypassing authentication of / login.php of a web application was made and whether the attack was successful or not, or whether an attack aimed at leaking information of / show.php of a web application was made and whether the attack was successful or not. The determination result is stored in the memory unit 11, for example.
[0044] According to the determination device 10, even when an attack is carried out that causes different damage depending on the function of the web application that is the target of the attack, it is possible to determine whether or not the attack is successful.
[0045] [Example of processing procedure] Next, an example of a processing procedure of the determination device 10 will be described with reference to Fig. 6 and Fig. 7. First, an example of a procedure in which the determination device 10 creates a function profile will be described with reference to Fig. 6.
[0046] When the determination device 10 acquires a new communication log (S1), it determines whether or not the communication log has been detected as a corresponding attack (an attack in which damage varies depending on the function of a web application) by the attack detection unit 122 (S2).
[0047] If the communication log acquired in S1 is not detected by the attack detection unit 122 as a corresponding attack (an attack causing different damage depending on the function of the web application) (No in S2), the function profile creation unit 121 uses the communication log to create a profile (function profile) for each function (URI) of the web application (S3).The function profile creation unit 121 then stores the function profile created in S3 in the storage unit 11.
[0048] On the other hand, if the communication log acquired in S1 is detected by the attack detection unit 122 as a relevant attack (an attack in which the damage varies depending on the function of the web application) (Yes in S2), the function profile creation unit 121 does not perform the process of creating a function profile using the communication log and terminates the process.
[0049] Next, an example of a procedure in which the determination device 10 determines whether or not an attack is successful by using a function profile will be described with reference to FIG.
[0050] First, when the determination device 10 acquires a new communication log (S11), the attack detection unit 122 determines whether or not the communication log has been detected as a corresponding attack (an attack causing different damage depending on the function of the web application) (S12). If the attack detection unit 122 detects the communication log as a corresponding attack (an attack causing different damage depending on the function of the web application) (Yes in S12), the success / failure determination unit 123 determines whether the attack has succeeded or failed based on the function profile (S13). Then, the determination result output unit 124 outputs the result of the determination in S13 (S14). On the other hand, if the communication log has not been detected as a corresponding attack (an attack causing different damage depending on the function of the web application) by the attack detection unit 122 (No in S12), the process ends.
[0051] By performing the above process, the determination device 10 can determine whether an attack has been successful or not, even if the damage caused by the attack varies depending on the function of the target web application. As a result, the maintenance personnel or administrator can distinguish between alerts that should be prioritized and those that should not, regarding the above attacks, and can therefore perform security operations efficiently.
[0052] [Other embodiments] The attack detection unit 122 in the determination device 10 may be installed outside the determination device 10. For example, the attack detection unit 122 may be realized by an attack detection device such as a Web Application Firewall (WAF) installed outside the determination device 10, as shown in (1) and (2) of Fig. 8. The determination device 10 may be configured to be directly connected to a web server that is to be determined as to whether an attack is successful (inline configuration) as shown in (1) of Fig. 8, or may be configured to be connected to the web server via an attack detection device such as a WAF (tap configuration) as shown in (2) of Fig. 8.
[0053] [System configuration, etc.] In addition, each component of each unit shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or a part of it can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc. Furthermore, each processing function performed by each device can be realized in whole or in part by a CPU and a program executed by the CPU, or can be realized as hardware using wired logic.
[0054] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified.
[0055] [program] The above-mentioned determination device 10 can be implemented by installing a program as package software or online software on a desired computer. For example, the above-mentioned program can be executed by an information processing device, so that the information processing device can function as the determination device 10. The information processing device here includes desktop or notebook personal computers. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone System), and further terminals such as PDA (Personal Digital Assistant), etc.
[0056] The determination device 10 may also be implemented as a server device that provides services related to the above-mentioned processes to a client, the client being a terminal device used by the user. In this case, the server device may be implemented as a Web server, or may be implemented as a cloud that provides services related to the above-mentioned processes by outsourcing.
[0057] 8 is a diagram showing an example of a computer that executes a determination program. The computer 1000 includes, for example, a memory 1010 and a CPU 1020. The computer 1000 also includes a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.
[0058] The memory 1010 includes a read only memory (ROM) 1011 and a random access memory (RAM) 1012. The ROM 1011 stores a boot program such as a basic input output system (BIOS). The hard disk drive interface 1030 is connected to a hard disk drive 1090. The disk drive interface 1040 is connected to a disk drive 1100. A removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to a display 1130, for example.
[0059] The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process executed by the above-mentioned determination device 10 is implemented as a program module 1093 in which computer-executable code is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, a program module 1093 for executing a process similar to the functional configuration of the determination device 10 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).
[0060] Data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads out the program module 1093 or the program data 1094 stored in the memory 1010 or the hard disk drive 1090 into the RAM 1012 as necessary and executes them.
[0061] Note that the program module 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1090, but may be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or wide area network (WAN)). The program module 1093 and the program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070. [Explanation of symbols]
[0062] 10 Judgment device 11 Storage section 12 Control section 121 Functional Profile Creation Department 122 Attack detection unit 123 Success / Failure Judgment Department 124 Judgment result output unit
Claims
1. an attack detection unit that detects a communication log of an attack in which damage varies depending on a function of a web application that is the request destination, using a URL of a request destination in a communication log of a target of the attack; a success / failure determination unit that determines whether the attack was successful by comparing the communication log in which the attack was detected with the presence or absence of a login form in the requested URL, the response size for the request, and profile information of the function of the web application that indicates whether the function of the web application has a login form and the range of the response size when returning a response to an external device; a judgment result output unit that outputs a result of the judgment; A determination device comprising:
2. The attack detection unit is At least one of the regular expressions "OR.*=.*#", "OR (1|'t') (#|--)" and ".+['"] (#|--)" is used as an attack detection signature to detect communication logs of attacks whose damage varies depending on the function of the requested web application.
2. The determination device according to claim 1.
3. a function profile creation unit that creates profile information of a function of a web application based on normal communication between an external device and the function of the web application; The determination device according to claim 1 , further comprising:
4. The success / failure determination unit When it is determined that the requested URL contains a login form and the status code is any one of 300 to 309 in the communication log in which the attack was detected, it is determined that the attack attempting authentication bypass was successful.
2. The determination device according to claim 1.
5. The success / failure determination unit When it is determined that the request destination URL does not have a login form and the response size to the request exceeds the range of the response size indicated in the profile information of the function of the web application by a predetermined value or more, the attack aimed at leaking information is determined to be successful.
2. The determination device according to claim 1.
6. A determination method executed by a determination device, detecting a communication log of an attack in which damage varies depending on a function of a web application that is the target of the attack, using a URL of a request destination in the communication log of the target of the attack; determining whether the attack was successful by comparing the communication log in which the attack was detected with the presence or absence of a login form in the requested URL and the response size to the request, with profile information of the function of the web application indicating whether the function of the web application has a login form and the range of the response size when returning a response to an external device; outputting the result of the determination; A method for determining whether or not a particular
7. detecting a communication log of an attack in which damage varies depending on a function of a web application that is the target of the attack, using a URL of a request destination in the communication log of the target of the attack; determining whether the attack was successful by comparing the communication log in which the attack was detected with the presence or absence of a login form in the requested URL and the response size to the request, with profile information of the function of the web application indicating whether the function of the web application has a login form and the range of the response size when returning a response to an external device; outputting the result of the determination; A judgment program for causing a computer to execute the above.
Citation Information
Patent Citations
Web traffic logging system and method for real-time detection of web hacking
JP2019533841A
Determination device, determination method, and determination program
JP6708794B2
