Distribution device, distribution program, and abnormality notification system
The distribution device addresses the inefficiency in network monitoring by creating and distributing lists of normal communication information, reducing over-detection and improving the accuracy of abnormality identification in network monitoring systems.
Patent Information
- Application Number
- PCT/JP2023/020029
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-30
- Publication Date
- 2024-12-05
AI Technical Summary
Conventional network monitoring systems face inefficiencies in preparing information for normal communication, leading to over-detection of abnormal communications, especially when Fully Qualified Domain Names (FQDNs) share the same name but have different IP addresses, which can result in false alarms and delayed responses to actual abnormalities.
A distribution device that acquires data on network devices, estimates communication destinations, collects corresponding IP addresses, and creates lists of normal communication information for each network, distributing this information to prevent over-detection by distinguishing between normal and abnormal communications.
This solution enables efficient preparation and distribution of normal communication information, reducing over-detection and allowing for timely identification of true abnormalities, thereby enhancing the accuracy and speed of network monitoring systems.
Smart Images

Figure JP2023020029_05122024_PF_FP_ABST
Abstract
Description
Distribution device, distribution program, and abnormality notification system
[0001] The present invention relates to a distribution device, a distribution program, and an abnormality notification system.
[0002] Conventionally, there is a network status analysis technique that learns normal communications for a certain period of time and determines that communication is abnormal if communication is made to a destination IP address that is different from that used during learning.
[0003] A study on a method for detecting and blocking anomalous communications based on name resolution records using SDN and DNS RPZ (Institute of Electronics, Information and Communication Engineers), [Retrieved May 29, 2023], Internet (https: / / eprints.lib.hokudai.ac.jp / dspace / handle / 2115 / 86960). A study on bot infection detection methods based on DNS communication behavior, [Retrieved May 29, 2023], Internet (https: / / www.iwsec.org / mws / 2008 / manuscript / 1008.pdf). Real-time malicious DNS query classification system using machine learning, [Retrieved May 29, 2023], Internet (https: / / repository.dl.itc.u-tokyo.ac.jp / record / 51888 / files / 48176414.pdf).
[0004] Conventional technologies have had the problem that it is sometimes difficult to prepare information regarding normal communications corresponding to monitored networks. For example, conventional technologies can result in overdetection, where abnormally normal communications (such as when the FQDN (Fully Qualified Domain Name) is the same but the IP address is different) are detected as abnormal. To prevent overdetection and notification, it is necessary to prepare, for example, a list of IP addresses corresponding to FQDNs. However, in an environment where there are many monitored networks, it is inefficient to create and configure list information of IP addresses corresponding to FQDNs, taking into account the communication destinations of devices included in each network.
[0005] The present invention has been made in view of the above, and aims to provide a distribution device, a distribution program, and an abnormality notification system that prepare information on normal communications corresponding to a network to be monitored.
[0006] In order to solve the above-mentioned problems and achieve the object, the distribution device of the present invention is characterized by having an acquisition unit that acquires data of devices included in a network to be monitored, an estimation unit that estimates the communication destinations of the devices using the data of the devices acquired by the acquisition unit, a collection unit that collects address information corresponding to the communication destinations of the devices estimated by the estimation unit, a creation unit that creates information regarding normal communications for each network to be monitored using the data of the devices acquired by the acquisition unit and the address information corresponding to the communication destinations of the devices collected by the collection unit, and a distribution unit that distributes the information regarding normal communications created by the creation unit to the networks to be monitored.
[0007] According to the present invention, information relating to normal communications corresponding to a network to be monitored can be easily prepared.
[0008] FIG. 1 is a table for explaining problems with the conventional technology. FIG. 2 is a block diagram showing an example of the configuration of an abnormality notification system according to an embodiment. FIG. 3 is a block diagram showing an example of the configuration of a distribution device according to an embodiment. FIG. 4 is a block diagram showing an example of the configuration of a notification device according to an embodiment. FIG. 5 is a diagram showing an outline of processing by a distribution device according to an embodiment. FIG. 6 is a diagram showing an outline of processing by a distribution device according to an embodiment. FIG. 7 is a diagram showing an outline of processing by a distribution device according to an embodiment. FIG. 8 is a diagram showing an outline of processing by a notification device according to an embodiment. FIG. 9 is a diagram showing an outline of processing by a notification device according to an embodiment. FIG. 10 is a flowchart showing an example of the flow of processing by a distribution device according to an embodiment. FIG. 11 is a flowchart showing an example of the flow of processing by a notification device according to an embodiment. FIG. 12 is a diagram showing an example of a computer that executes a distribution program.
[0009] Hereinafter, with reference to the drawings, embodiments of a distribution device, a distribution program, and an abnormality notification system according to the present application will be described in detail. Note that the present invention is not limited to these embodiments. In addition, in the description of the drawings, the same parts are denoted by the same reference numerals, and duplicated explanations will be omitted.
[0010] [Introduction] Conventionally, there exist anomalous communication detection systems that identify unusual communications as anomalous communications. While such anomalous communication detection systems can correctly identify unknown anomalous communications that are different from usual as anomalous, they can sometimes suffer from overdetection, where they mistakenly identify normal communications that are different from usual as anomalous communications.
[0011] For example, as shown in Fig. 1, even for communications addressed to the same FQDN, different IP addresses may be required due to name resolution by the DNS (Domain Name System). In particular, when a CDN (Contents Delivery Network) is used, the IP address corresponding to the FQDN may change frequently.
[0012] 1, if the IP address corresponding to terminal A and the DNS response is not learned, an overdetection will occur every time terminal A communicates with each IP address, even though the communication is to the same FQDN. In addition, although an example of only terminal A is shown in FIG. 1, if the number of terminals increases, the occurrence of overdetection will increase exponentially.
[0013] When a large number of false positives occur, it takes a lot of time to check whether the communication is truly abnormal, which is inefficient, and when truly abnormal communication does occur, there is a high risk of a delayed or missed response. Therefore, in order to distinguish between normal and abnormal communication, information on IP addresses corresponding to the same FQDN is required.
[0014] Here, since the devices included in the network and the software installed in the devices differ for each monitored network, in order to identify abnormal communications, it is necessary to prepare information on IP addresses corresponding to the same FQDN for each monitored network. However, in an environment where there are many networks, it is inefficient to create and set list information on IP addresses corresponding to the same FQDN, taking into account the communication destinations of the devices included in each network.
[0015] Therefore, the distribution device 100 performs the following process. First, the distribution device 100 acquires data on devices included in the monitored networks. Next, the distribution device 100 uses the device data to estimate the communication destinations of the devices. Next, the distribution device 100 collects IP addresses corresponding to the communication destinations. After that, the distribution device 100 creates information on normal communication for each monitored network from the device data and the IP addresses corresponding to the communication destinations of the devices. Then, the distribution device 100 distributes the information on normal communication to the monitored networks.
[0016] This allows the distribution device 100 to prepare information about normal communications for each monitored network. For example, the distribution device 100 can create a master list of FQDNs and IP addresses and distribute it to monitored networks, thereby enabling efficient operation of multiple anomalous communication detection systems. Furthermore, for example, the distribution device 100 can automatically distribute updated results of the master list of FQDNs and IP addresses to monitored networks, thereby enabling hassle-free operation of multiple anomalous communication detection systems using the latest lists of FQDNs and IP addresses.
[0017] Furthermore, for example, the distribution device 100 can grasp the devices and software configurations used within the monitored network and then distribute a list of FQDNs and IP addresses corresponding to the network, thereby making it possible to efficiently detect abnormal communications while suppressing overdetection, even in a network where various devices are mixed.
[0018] [Configuration of the abnormality notification system] Next, the configuration of the abnormality notification system 1 will be described using Fig. 2. The abnormality notification system 1 is a system that notifies of communication abnormalities detected by an external system such as an abnormality detection system. As shown in Fig. 2, the abnormality notification system 1 has a distribution device 100 and a notification device 200. An overview of the processing of each of these devices will be described below.
[0019] The distribution device 100 collects address information of the communication destinations of devices estimated from data of devices included in the monitored networks, creates information regarding normal communication for each monitored network using the device data and the address information corresponding to the communication destinations, and distributes the information regarding normal communication to the monitored networks.
[0020] The notification device 200 is placed in each monitored network, acquires information about abnormal communication detected by an external system such as an anomaly detection system, determines whether the information about the abnormal communication corresponds to information about normal communication distributed from the distribution device 100, and if it is determined that they correspond, outputs and notifies the information about the abnormal communication and the information about the normal communication.
[0021] The anomaly detection system given as an example of an external system is a system that detects communication anomalies, and may include the anomaly notification system 1 of this embodiment.
[0022] [Configuration of Distribution Device] Next, the configuration of the distribution device 100 will be described using Fig. 3. As shown in Fig. 3, the distribution device 100 has a communication unit 110, a control unit 120, and a storage unit 130. Note that these units may be distributed and held by multiple devices. The processing of these units will be described below.
[0023] The communication unit 110 is realized by a network interface card (NIC) or the like, and enables communication between the control unit 120 and an external device via a telecommunication line such as a local area network (LAN) or the Internet. For example, the communication unit 110 enables communication between the external device and the control unit 120.
[0024] The storage unit 130 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. The information stored in the storage unit 130 includes, for example, device data, information about normal communication, and other information necessary for distributing information about normal communication. Here, the device data is data for managing devices included in the monitored network, and includes data held by a package management system provided in the device and data held by a configuration management system that manages the devices in an integrated manner. The device data also includes information about the network to which the device belongs, device terminal information, information about software installed in the device, and the like. The information about normal communication also includes information about the FQDN of a normal communication destination, IP address information corresponding to the FQDN of the normal communication destination, and the like. The information stored in the storage unit 130 is not limited to the examples described above.
[0025] The control unit 120 is realized using a CPU (Central Processing Unit), an NP (Network Processor), an FPGA (Field Programmable Gate Array), or the like, and executes processing programs stored in memory. As shown in Fig. 3, the control unit 120 has an acquisition unit 121, an estimation unit 122, a collection unit 123, a creation unit 124, and a distribution unit 125. Each unit of the control unit 120 will be described below.
[0026] The acquisition unit 121 acquires data on devices included in the network to be monitored. For example, the acquisition unit 121 acquires data on the devices included in the network to be monitored, such as data on the target devices, data held by a package management system provided in the target devices, and data held by a configuration management system that manages the target devices in an integrated manner. Here, the device data acquired by the acquisition unit 121 includes, for example, information that can be used to estimate the communication destinations of the devices, such as terminal information on the devices and information on software installed in the devices, as well as information on the network to which the devices belong. Furthermore, the target device data can be in a format appropriate for the purpose, such as Excel format or SBOM (Software Bill of Materials) format.
[0027] Furthermore, when a change occurs in a network to be monitored, the acquiring unit 121 acquires data on devices included in the network to be monitored. For example, when a change (addition, replacement, movement, etc.) occurs in a device included in a network to be monitored, the acquiring unit 121 acquires data on the device included in the network to be monitored.
[0028] The estimation unit 122 estimates the communication destination of a device by using the device data acquired by the acquisition unit 121. For example, the estimation unit 122 estimates the communication destination of a device by using one or more of device terminal information and information on software installed in the device, which are included in the device data acquired by the acquisition unit 121. For example, the estimation unit 122 estimates, from the device terminal information "Manufactured by XX Company: Model Number XXXX" included in the device data acquired by the acquisition unit 121, that the target device accesses an FQDN used by XX Company to distribute security patches.
[0029] Furthermore, for example, the estimation unit 122 estimates that the target device will access the FQDN used by XX Company to distribute pattern files from the information on the software installed in the device included in the device data acquired by the acquisition unit 121, "XX Company: Antivirus Software XX."
[0030] The collection unit 123 collects address information corresponding to the communication destination of the device estimated by the estimation unit 122. For example, the collection unit 123 performs a DNS query using the FQDN of the communication destination of the estimated device, and collects information on the FQDN of the communication destination of the estimated device and the corresponding IP address from the analysis result of capturing the DNS query packet and the response packet.
[0031] The collection unit 123 also collects address information corresponding to the communication destinations of the device at a predetermined cycle. For example, the collection unit 123 sends a DNS query to the communication destinations of the device every 24 hours and collects IP addresses corresponding to the FQDNs of the communication destinations of the device. The predetermined cycle at which the collection unit 123 collects information can be changed as needed.
[0032] The creation unit 124 creates information about normal communications for each network to be monitored, using the device data acquired by the acquisition unit 121 and address information corresponding to the communication destinations of the devices collected by the collection unit 123. For example, the creation unit 124 creates a list in which FQDNs and IP addresses are associated as information about normal communications. For example, the creation unit 124 creates information about FQDNs and corresponding IP addresses including communication destinations of devices included in the network to be monitored, using information about the networks to which the devices belong, which is included in the device data acquired by the acquisition unit 121, and information about IP addresses corresponding to the communication destinations of the devices collected by the collection unit 123.
[0033] The distribution unit 125 distributes, to the monitored network, information relating to normal communication created by the creation unit 124. For example, the distribution unit 125 distributes information relating to normal communication for a certain monitored network created by the creation unit 124 to a notification device 200 included in the monitored network.
[0034] Furthermore, when new information on normal communication that differs from information on normal communication previously created by the creation unit 124 is created, the distribution unit 125 distributes the newly created information on normal communication to the network to be monitored. For example, when new information on normal communication that includes information on a combination of an FQDN and an IP address that is not included in information on normal communication previously created by the creation unit 124 is created, the distribution unit 125 distributes the newly created information on normal communication to the notification device 200 included in the network to be monitored.
[0035] [Configuration of notification device] Next, the configuration of notification device 200 will be described using Fig. 4. As shown in Fig. 4, notification device 200 has a communication unit 210, a control unit 220, and a storage unit 230. Note that each of these units may be held in a distributed manner in multiple devices. The processing of each of these units will be described below.
[0036] The communication unit 210 is realized by a network interface card (NIC) or the like, and enables communication between the control unit 220 and an external device via a telecommunication line such as a local area network (LAN) or the Internet. For example, the communication unit 210 enables communication between the external device and the control unit 220.
[0037] The storage unit 230 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. Information stored in the storage unit 230 includes, for example, information on abnormal communication, information on normal communication, information on the subject of notification, and other information necessary for notification of abnormal communication.
[0038] Here, the information about abnormal communication is detailed information about communication that the external device has identified as abnormal, and includes information such as the destination IP address, the destination port number, the source IP address, the source port number, the source MAC address, etc. Furthermore, the information about normal communication includes information such as the FQDN of the normal communication destination and the IP address corresponding to the FQDN of the normal communication destination.
[0039] The information about normal communication stored in the storage unit 230 may be information distributed to each monitored network by the distribution device 100. The information about the notification target is information indicating the notification target, and includes information such as a user selection and a normal communication destination list. The information stored in the storage unit 230 is not limited to the examples described above.
[0040] The control unit 220 is realized using a CPU (Central Processing Unit), an NP (Network Processor), an FPGA (Field Programmable Gate Array), etc., and executes processing programs stored in memory. As shown in Fig. 4, the control unit 220 has an acquisition unit 221, a determination unit 222, a reception unit 223, and a notification unit 224. Each unit of the control unit 220 will be described below.
[0041] The acquisition unit 221 acquires information about abnormal communication from an external device. For example, the acquisition unit 221 receives information about abnormal communication, such as a destination IP address, a destination port number, a source IP address, a source port number, and a source MAC address, from an anomaly detection system.
[0042] The determination unit 222 determines whether the information regarding abnormal communication acquired by the acquisition unit 221 corresponds to information regarding normal communication distributed from the distribution device 100. For example, the determination unit 222 determines whether a destination IP address included in the information regarding abnormal communication acquired by the acquisition unit 221 matches an IP address corresponding to an FQDN included in the information regarding normal communication distributed from the distribution device 100.
[0043] The reception unit 223 receives information on the notification target, which indicates whether information on the abnormal communication determined by the determination unit 222 to be handled is the notification target. For example, the reception unit 223 receives a selection from the user as information on the notification target, which indicates whether information on the abnormal communication determined by the determination unit 222 to be handled is the notification target. Note that the selection from the user includes a selection from the user of "the notification target" or "not the notification target", etc.
[0044] For example, the receiving unit 223 receives a selection of "not subject to notification" from the user as information regarding the subject of notification, indicating whether the information regarding the abnormal communication that the determining unit 222 has determined to be handled is subject to notification.
[0045] Furthermore, for example, the reception unit 223 receives communication destination information as information on the notification target indicating whether information on abnormal communication determined by the determination unit 222 to be handled is the notification target. Here, one example of the communication destination information is a normal communication destination list that lists normal communication destinations. For example, the reception unit 223 receives the normal communication destination list as information on the notification target indicating whether information on abnormal communication determined by the determination unit 222 to be handled is the notification target.
[0046] When the determination unit 222 determines that a response should be made, the notification unit 224 outputs and notifies the user of information related to the abnormal communication acquired by the acquisition unit 221 and information related to the normal communication distributed from the distribution device 100. The output by the notification unit 224 includes transmitting, displaying, and the like of the target information. For example, when the determination unit 222 determines that a response should be made, the notification unit 224 displays and notifies the user of information related to the abnormal communication acquired by the acquisition unit 221 and information related to the normal communication distributed from the distribution device 100 and stored in the storage unit 230, including an FQDN.
[0047] Also, for example, when the determination unit 222 determines that a response is necessary, the notification unit 224 displays and notifies the user of information regarding the abnormal communication acquired by the acquisition unit 221, such as the destination IP address, the destination port number, the source IP address, the source port number, and the source MAC address, together with the FQDN as information regarding the normal communication distributed from the distribution device 100.
[0048] Furthermore, the notification unit 224 outputs and notifies the information on the abnormal communication acquired by the acquisition unit 221 and the information on the normal communication distributed from the distribution device 100, in accordance with the information on the notification target accepted by the acceptance unit 223. For example, the notification unit 224 outputs and notifies the information on the abnormal communication acquired by the acquisition unit 221 and the information on the normal communication distributed from the distribution device 100, in accordance with the selection from the user accepted by the acceptance unit 223.
[0049] For example, upon receiving a selection from the user that is accepted by the receiving unit 223 as “to be notified,” the notification unit 224 displays and notifies the user of information regarding abnormal communication acquired by the acquisition unit 221 and information regarding normal communication distributed from the distribution device 100.
[0050] Furthermore, for example, the notification unit 224 outputs and notifies information regarding abnormal communication acquired by the acquisition unit 221 and information regarding normal communication distributed from the distribution device 100, in accordance with the information regarding the communication destination accepted by the acceptance unit 223. For example, when the information regarding the confirmed communication destination accepted by the acceptance unit 223 and the information regarding the abnormal communication acquired by the acquisition unit 221 is not included in the normal communication destination list accepted by the acceptance unit 223, the notification unit 224 displays and notifies information regarding the abnormal communication acquired by the acquisition unit 221 and information regarding normal communication distributed from the distribution device 100.
[0051] [Processing by Distribution Device] Next, processing by the distribution device 100 will be described with reference to Figures 5 to 7. Figures 5 to 7 are diagrams for explaining an overview of processing by the distribution device 100 according to the embodiment.
[0052] First, the distribution device 100 acquires data of devices included in the network to be monitored, as shown in Fig. 5. For example, the acquisition unit 121 of the distribution device 100 acquires data (SBOM, etc.) of devices included in the network to be monitored.
[0053] Next, the estimation unit 122 of the distribution device 100 uses the acquired device data to estimate the FQDN of each device's communication destination. For example, from the device's terminal information "XX Company: Model Number XXXX" included in the SBOM, it estimates that "the target device accesses the FQDN used by XX Company to distribute security patches." Also, from the software information installed in the device included in the SBOM, "XX Company: Antivirus Software XX," it estimates that "the target device accesses the FQDN used by XX Company to distribute pattern files."
[0054] Next, as shown in FIG. 6 , the collection unit 123 of the distribution device 100 performs a DNS query for each device using the FQDN of the estimated device's communication destination, and collects information on the IP addresses corresponding to the FQDNs of the estimated device's communication destinations. For example, the collection unit 123 of the distribution device 100 performs a DNS query for the estimated device's communication destinations on a 24-hour cycle and collects information on the corresponding IP addresses. Note that the timing at which the collection unit 123 of the distribution device 100 collects the IP address information corresponding to the FQDNs of the estimated device's communication destinations may be at any timing, such as a predetermined cycle, a predetermined date and time, or timing linked to a predetermined process of an external system.
[0055] The creation unit 124 of the distribution device 100 then uses the device data and the collected address information corresponding to the communication destinations of the devices to create information about normal communication for each network to be monitored. For example, the creation unit 124 of the distribution device 100 uses information about the network to which the device belongs, which is included in the device data, and collected information about IP addresses corresponding to the FQDNs of the communication destinations of the devices, to create a list that associates FQDNs with IP addresses for each network to be monitored.
[0056] Then, the distribution unit 125 of the distribution device 100 distributes the created information about normal communication to the network being monitored, as shown in Fig. 7. For example, when the distribution unit 125 of the distribution device 100 creates information about normal communication that differs from information about normal communication created previously, the distribution unit 125 distributes the newly created information about normal communication to the network being monitored.
[0057] In other words, when an IP address corresponding to an FQDN is changed, the information is collected, and a list correlating the new FQDN with the IP address is created, the distribution unit 125 of the distribution device 100 distributes the newly created list correlating the FQDN with the IP address to the network to be monitored.
[0058] By performing this processing, the distribution device 100 can easily prepare information regarding normal communications corresponding to the networks to be monitored, without considering the communication destinations of the devices included in each network, in an environment where there are multiple networks to be monitored, and always distribute the latest information to the networks to be monitored.
[0059] [Processing by Notification Device] Next, processing by the notification device 200 will be described with reference to Fig. 8 and Fig. 9. Fig. 8 and Fig. 9 are diagrams for explaining processing by the notification device 200 according to the embodiment.
[0060] First, the storage unit 230 of the notification device 200 stores information about normal communication (a list associating FQDNs with IP addresses) distributed from the distribution unit 125 of the distribution device 100. Next, the acquisition unit 221 of the notification device 200 receives information such as the destination IP address, destination port number, source IP address, source port number, and source MAC address from the anomalous communication detection system.
[0061] Next, the judgment unit 222 of the notification device 200 determines whether the destination IP address included in the information regarding abnormal communication acquired by the acquisition unit 221 of the notification device 200 matches the IP address corresponding to the FQDN included in the information regarding normal communication distributed from the distribution device 100 and stored in the memory unit 230 of the notification device 200.
[0062] At this time, if the determination unit 222 of the notification device 200 determines that the destination IP address information acquired by the acquisition unit 221 of the notification device 200 matches the IP address corresponding to the FQDN delivered from the distribution device 100 and stored in the memory unit 230 of the notification device 200, the notification unit 224 of the notification device 200 adds the FQDN information corresponding to the destination IP address delivered from the distribution device 100 and stored in the memory unit 230 of the notification device 200 to the information such as the destination IP address received from the anomalous communication detection system, and notifies the user.
[0063] This makes it easy to determine the possibility of anomalous communication from the FQDN even when a large number of alerts are generated, as shown in Figure 8. For example, if the host name or domain name is known, it is determined that the communication is not anomalous. Also, for example, external communication where the destination IP address is directly entered is determined to be highly likely to be anomalous.
[0064] Next, the notification process by the notification device 200 will be described with reference to FIG. 9. FIG. 9 is a diagram for explaining the process by the notification device 200. FIG. 9(1) is an example of a details screen for an alert that has occurred. FIG. 9(2) is an example of information about normal communication distributed from a terminal having the functions of the distribution device 100. FIG. 9(3) is an example of a normal communication destination list.
[0065] First, the reception unit 223 of the notification device 200 receives information related to the notification target. For example, as shown in Fig. 9 (1), the reception unit 223 of the notification device 200 receives a check mark in a field indicating that notification is not required, thereby receiving a selection from the user that "notification is not required."
[0066] By doing this, the notification unit 224 of the notification device 200 will not subsequently notify any communications having as its destination each IP address linked to the FQDN for which the user has selected "no notification required," as shown in Figure 9 (2).
[0067] Also, for example, the reception unit 223 of the notification device 200 may receive, as communication destination information, an FQDN that has been determined in advance to be a normal communication destination and a list of IP addresses corresponding to the FQDN (normal communication destination list), as shown in Figure 9 (3).
[0068] In this way, the notification device 200 uses the information of the normal communication destination list received in advance to prevent unnecessary notifications from being issued.
[0069] [Flowchart] Next, the flow of processing by the distribution device 100 will be described with reference to Fig. 10. Fig. 10 is a flowchart showing the flow of processing by the distribution device 100. Note that the following steps may be executed in a different order, and some processing may be omitted.
[0070] First, the distribution device 100 determines whether or not it has received a processing command (step S101). If the distribution device 100 has not received a processing command (step S101 "NO"), the distribution device 100 determines again whether or not it has received a processing command. On the other hand, if the distribution device 100 has received a processing command (step S101 "YES"), the distribution device 100 performs the processes from step S102 onward.
[0071] First, the acquisition unit 121 acquires data on devices included in the network to be monitored (step S102). For example, the acquisition unit 121 acquires data on the devices included in the network to be monitored, such as data on the target devices, data held by a package management system included in the target devices, and data held by a package management system included in a configuration management system that performs integrated management of the target devices.
[0072] Next, the estimation unit 122 estimates the communication destination of the device using the device data acquired by the acquisition unit 121 (step S103). For example, the estimation unit 122 estimates the communication destination of the device using one or more of the device terminal information included in the device data acquired by the acquisition unit 121 and information on software installed in the device.
[0073] Then, the collection unit 123 collects address information corresponding to the communication destination of the device estimated by the estimation unit 122 (step S104). For example, the collection unit 123 performs a DNS query using the FQDN of the communication destination of the estimated device, and collects information on the FQDN of the communication destination of the estimated device and the corresponding IP address from the analysis result of capturing the DNS query packet and the response packet.
[0074] Thereafter, the creation unit 124 creates information on normal communications for each network to be monitored, using the device data acquired by the acquisition unit 121 and the address information corresponding to the communication destinations of the devices collected by the collection unit 123 (step S105). For example, the creation unit 124 creates a list of FQDNs and IP addresses associating them with each other as information on normal communications.
[0075] Then, the distribution unit 125 distributes the information about normal communication created by the creation unit 124 to the networks to be monitored (step S106). For example, the distribution unit 125 distributes the information about normal communication for a certain network to be monitored, created by the creation unit 124, to the notification device 200 included in the network to be monitored.
[0076] Next, the flow of processing by notification device 200 will be described using Fig. 11. Fig. 11 is a flowchart showing the flow of processing by notification device 200. Note that the steps below may be executed in a different order, and some processing may be omitted.
[0077] First, the notification device 200 determines whether or not a processing command has been received (step S201). If the notification device 200 has not received a processing command (step S201 "NO"), the notification device 200 again determines whether or not a processing command has been received. On the other hand, if the distribution device 100 has received a processing command (step S201 "YES"), the distribution device 100 performs the processes from step S202 onward.
[0078] Next, the acquisition unit 221 acquires information about the abnormal communication from an external device (step S202). For example, the acquisition unit 121 receives information about the abnormal communication, such as a destination IP address, a destination port number, a source IP address, a source port number, and a source MAC address, from the anomalous communication detection system.
[0079] Then, the determination unit 222 determines whether the information regarding the abnormal communication acquired by the acquisition unit 221 corresponds to information regarding normal communication distributed from the distribution device 100 (step S203). For example, the determination unit 222 determines whether the destination IP address included in the information regarding the abnormal communication acquired by the acquisition unit 221 matches an IP address corresponding to an FQDN included in the information regarding normal communication distributed from the distribution device 100 and stored in the storage unit 230.
[0080] Here, if the judgment unit 222 determines that the information regarding abnormal communication corresponds to information regarding normal communication (step S203 "YES"), the notification unit 224 determines whether the information regarding abnormal communication that the judgment unit 222 determines to correspond is subject to notification (step S204).
[0081] Here, if the notification unit 224 determines that the information regarding the abnormal communication that the judgment unit 222 has determined to be handled is the subject of notification (step S204 "YES"), the notification unit 224 outputs and notifies the information regarding the abnormal communication acquired by the acquisition unit 221 and the information regarding the normal communication that was distributed from the distribution device 100 and stored in the memory unit 230, in accordance with the information regarding the subject of notification received by the reception unit 223 (step S205).
[0082] For example, in response to a selection from the user received by the receiving unit 223, the notification unit 224 displays and notifies the user of information regarding abnormal communication acquired by the acquisition unit 221 and information regarding normal communication distributed from the distribution device 100 and stored in the memory unit 230, including an FQDN.
[0083] Thereafter, the receiving unit 223 receives information on the notification target, which indicates whether the information on the abnormal communication determined by the determining unit 222 to be handled is the notification target (step S206). For example, the receiving unit 223 receives a selection from the user as information on the notification target, which indicates whether the information on the abnormal communication determined by the determining unit 222 to be handled is the notification target.
[0084] On the other hand, in step S203, if the notification unit 224 determines that the information regarding the abnormal communication that the judgment unit 222 has determined to be handled is not subject to notification (step S204 "NO"), the notification unit 224 does not issue a notification.
[0085] On the other hand, if the determination unit 222 determines in step S203 that the information regarding the abnormal communication does not correspond to the information regarding the normal communication (step S203 "NO"), the notification unit 224 outputs and notifies the information regarding the abnormal communication (step S207). For example, the notification unit 224 outputs and notifies information such as the destination IP address, the destination port number, the source IP address, the source port number, and the source MAC address as the information regarding the abnormal communication.
[0086] [Effect] The distribution device 100 according to the embodiment includes an acquisition unit 121 that acquires data on devices included in a network to be monitored, an estimation unit 122 that estimates the communication destinations of the devices using the device data acquired by the acquisition unit 121, a collection unit 123 that collects address information corresponding to the communication destinations of the devices estimated by the estimation unit 122, a creation unit 124 that creates information on normal communication for each network to be monitored using the device data acquired by the acquisition unit 121 and the address information corresponding to the communication destinations of the devices collected by the collection unit 123, and a distribution unit 125 that distributes the information on normal communication created by the creation unit 124 to the network to be monitored.
[0087] As a result, the distribution device 100 can easily prepare information regarding normal communications corresponding to the network being monitored by collecting address information corresponding to the communication destination of the device estimated from the data of the device included in the network being monitored and creating and distributing information regarding normal communications.
[0088] The distribution device 100 can also prepare information about normal communications for each monitored network. For example, the distribution device 100 can create a master list of FQDNs and IP addresses and distribute the master list to monitored networks, thereby enabling efficient operation of the anomalous communication detection system in multiple monitored networks.
[0089] In addition, the distribution device 100 grasps the devices and software configurations used within the monitored network and then distributes a list of FQDNs and IP addresses corresponding to the network, thereby making it possible to efficiently detect abnormal communications while suppressing overdetection, even in networks where various devices are mixed.
[0090] Furthermore, the estimation unit 122 of the distribution device 100 according to the embodiment estimates the communication destination of the device by using one or more of the terminal information of the device included in the device data and information on the software installed in the device.
[0091] As a result, the distribution device 100 can easily prepare information regarding normal communications corresponding to the network being monitored by collecting address information corresponding to the communication destination of the device estimated from terminal information contained in the data of the device included in the network being monitored and information on the installed software, and creating and distributing information regarding normal communications.
[0092] Furthermore, when there is a change in the network to be monitored, the acquisition unit 121 of the distribution device 100 according to the embodiment acquires data of devices included in the network to be monitored.
[0093] As a result, the distribution device 100 can easily prepare information regarding normal communication corresponding to the network being monitored by acquiring device data when the network being monitored changes, collecting address information corresponding to the device's communication destination estimated from the device data, and creating and distributing information regarding normal communication.
[0094] Furthermore, the collection unit 123 of the distribution device 100 according to the embodiment collects address information corresponding to communication destinations of the device at predetermined intervals.
[0095] As a result, the distribution device 100 can easily prepare information regarding normal communications corresponding to the network being monitored by acquiring data on devices included in the network being monitored, collecting address information corresponding to the communication destinations of the devices estimated from the device data at a predetermined interval, and creating and distributing information regarding normal communications.
[0096] In addition, when new information regarding normal communication that differs from information regarding normal communication previously created by the creation unit 124 is created, the distribution unit 125 of the distribution device 100 according to the embodiment distributes the newly created information regarding normal communication to the network being monitored.
[0097] As a result, when new information about different normal communication is created, the distribution device 100 can distribute the newly created information about normal communication to the network being monitored. In other words, by automatically distributing the updated results of the master FQDN and IP address list to the network being monitored, it is possible to easily operate multiple anomalous communication detection systems using the latest FQDN and IP address lists at all times.
[0098] Furthermore, the creation unit 124 of the distribution device 100 according to the embodiment creates a list of FQDNs and IP addresses associated with each other as information regarding normal communication.
[0099] As a result, the distribution device 100 can easily prepare information regarding normal communication corresponding to the network being monitored by collecting the IP addresses corresponding to the FQDNs of the communication destinations of the devices estimated from the data of the devices included in the network being monitored and creating and distributing information regarding normal communication.
[0100] Moreover, the abnormality notification system 1 according to the embodiment includes a distribution device 100 that distributes information on normal communication to a plurality of networks to be monitored, and a notification device 200 that notifies of abnormal communication in each of the networks to be monitored. The distribution device 100 includes an acquisition unit 121 that acquires data on devices included in the networks to be monitored, an estimation unit 122 that estimates communication destinations of the devices from the device data acquired by the acquisition unit 121, a collection unit 123 that collects address information corresponding to the communication destinations of the devices estimated by the estimation unit 122, and a notification device 200 that notifies of abnormal communication in each of the networks to be monitored using the device data acquired by the acquisition unit 121 and the address information corresponding to the communication destinations of the devices collected by the collection unit 123. The notification device 200 has a creation unit 124 that creates information on normal communication for each monitored network, and a distribution unit 125 that distributes the information on normal communication created by the creation unit 124 to the monitored networks. The notification device 200 has an acquisition unit 221 that acquires information on abnormal communication from an external device, a determination unit 222 that determines whether the information on abnormal communication acquired by the acquisition unit 221 corresponds to information on normal communication distributed from the distribution device 100, and a notification unit 224 that outputs and notifies the information on abnormal communication acquired by the acquisition unit 221 and the information on normal communication distributed from the distribution device 100 when the determination unit 222 determines that they correspond.
[0101] As a result, the distribution device 100 of the abnormality notification system 1 creates and distributes information about normal communication, and the notification device 200 determines whether the information about abnormal communication corresponds to pre-stored information about normal communication, and if so, outputs and notifies the user of the information about normal communication together, thereby enabling the accurate identification of abnormal communication. In other words, the distribution device 100 and notification device 200 included in the abnormality notification system 1 operate in cooperation with each other, thereby preventing the issuance of alerts due to overdetection.
[0102] [Program] A program written in a computer-executable language may be created to execute the processes performed by the distribution device 100 described in the above embodiment. In this case, the same effects as those of the above embodiment can be achieved by having a computer execute the program. Furthermore, such a program may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer to achieve the same processes as those of the above embodiment.
[0103] Fig. 12 is a diagram showing an example of a computer that executes a distribution program. As shown in Fig. 12, the computer 1000 includes, for example, a memory 1010, a CPU 1020, 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.
[0104] The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). 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 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.
[0105] 12, the hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. The tables described in the above embodiments are stored in the hard disk drive 1090 or the memory 1010, for example.
[0106] The distribution program is stored in the hard disk drive 1090 as a program module in which instructions to be executed by the computer 1000 are written. Specifically, the hard disk drive 1090 stores a program module 1093 in which each process executed by the computer 1000 described in the above embodiment is written.
[0107] Furthermore, data used for information processing by the distribution program is stored as program data, for example, in hard disk drive 1090. Then, CPU 1020 reads program module 1093 and program data 1094 stored in hard disk drive 1090 into RAM 1012 as necessary, and executes each of the above-described procedures.
[0108] Note that the program module 1093 and program data 1094 related to the distribution program are not limited to being stored in the hard disk drive 1090, and may be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100. Alternatively, the program module 1093 and program data 1094 related to the control program may be stored in another computer connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network), and read by the CPU 1020 via the network interface 1070.
[0109] [Others] Various embodiments have been described in detail in this specification with reference to the drawings, but these embodiments are examples and are not intended to limit the present invention to these embodiments. The features described in this specification can be realized in various ways, including various modifications and improvements based on the knowledge of those skilled in the art.
[0110] Furthermore, the above-mentioned "module (-er suffix, -or suffix)" can be read as a unit, a means, a circuit, etc. For example, a communication module, a control module, and a storage module can be read as a communication unit, a control unit, and a storage unit, respectively.
[0111] REFERENCE SIGNS LIST 1 Abnormality notification system 100 Distribution device 110 Communication unit 120 Control unit 121 Acquisition unit 122 Estimation unit 123 Collection unit 124 Creation unit 125 Distribution unit 130 Storage unit 200 Notification device 210 Communication unit 220 Control unit 221 Acquisition unit 222 Determination unit 223 Reception unit 224 Notification unit 230 Storage unit
Claims
1. A distribution device comprising: an acquisition unit that acquires data on devices included in a network to be monitored; an estimation unit that estimates communication destinations of the devices using the data on the devices acquired by the acquisition unit; a collection unit that collects address information corresponding to the communication destinations of the devices estimated by the estimation unit; a creation unit that creates information regarding normal communications for each network to be monitored using the data on the devices acquired by the acquisition unit and the address information corresponding to the communication destinations of the devices collected by the collection unit; and a distribution unit that distributes the information regarding normal communications created by the creation unit to the networks to be monitored.
2. The distribution device according to claim 1, characterized in that the estimation unit estimates the communication destination of the device using one or more of the terminal information of the device contained in the data of the device and information on the software installed in the device.
3. The distribution device according to claim 1, characterized in that the acquisition unit acquires data of the devices included in the network to be monitored when a change occurs in the network to be monitored.
4. The distribution device according to claim 1, characterized in that the collection unit collects the address information corresponding to the communication destinations of the device at a predetermined cycle.
5. The distribution device according to claim 1, characterized in that when new information regarding normal communication that differs from information regarding normal communication previously created by the creation unit is created, the distribution unit distributes the newly created information regarding normal communication to the network to be monitored.
6. The distribution device according to claim 1 or 5, characterized in that the creation unit creates a list in which FQDNs correspond to IP addresses as information regarding normal communication.
7. A distribution program which causes a computer to execute the following steps: an acquisition step of acquiring data on devices included in a network to be monitored; an estimation step of estimating the communication destinations of the devices from the data on the devices acquired by the acquisition step; a collection step of collecting address information corresponding to the communication destinations of the devices estimated by the estimation step; a creation step of creating information on normal communications for each network to be monitored using the data on the devices acquired by the acquisition step and the address information corresponding to the communication destinations of the devices collected by the collection step; and a distribution step of distributing the information on normal communications created by the creation step to the networks to be monitored.
8. An anomaly notification system comprising a distribution device which distributes information regarding normal communication to a plurality of networks to be monitored, and a notification device which notifies of abnormal communication in each of the networks to be monitored, wherein the distribution device has: an acquisition unit which acquires data on devices included in the networks to be monitored; an estimation unit which estimates a communication destination of the device from the data on the device acquired by the acquisition unit; a collection unit which collects address information corresponding to the communication destination of the device estimated by the estimation unit; a creation unit which creates information regarding normal communication for each of the networks to be monitored using the data on the device acquired by the acquisition unit and the address information corresponding to the communication destination of the device collected by the collection unit; and a distribution unit which distributes the information regarding normal communication created by the creation unit to the networks to be monitored, wherein the notification device has: an acquisition unit which acquires information regarding abnormal communication from an external device; and a determination unit which determines whether the information regarding abnormal communication acquired by the acquisition unit corresponds to the information regarding normal communication distributed from the distribution device; and a notification unit that, when the determination unit determines that a response should be made, outputs and notifies information regarding the abnormal communication acquired by the acquisition unit and information regarding the normal communication distributed from the distribution device.
Citation Information
Patent Citations
User terminal correspondence analysis system and method
JP2012142790A
