Unauthorized access detection system

JPWO2024237347A1Undetermined Publication Date: 2024-11-21
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025520658
Authority / Receiving Office
JP · JP
Patent Type
Applications
Priority Date
2023-05-18
Filing Date
2024-05-20
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

As network scales increase, existing methods for detecting unauthorized access by monitoring IP packets between private and external networks face high loads due to the growing number of IP packets, leading to inefficiencies in detecting fraudulent packets.

Method used

A system is implemented with an unauthorized access detection device that collects IP packets, creates a DNS table to associate IP addresses with domain names, and uses this information to detect and identify fraudulent packets by checking against valid and invalid domain lists, and includes a unit to count packet occurrences for alert notifications when thresholds are exceeded.

Benefits of technology

This system effectively detects and identifies fraudulent packets, allowing for early countermeasures against unauthorized access and cyber threats, thereby protecting network resources.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

Provided is a system for detecting unauthorized packets transmitted between a private network and an external network. An unauthorized access detection apparatus 20 is disposed at a relay point between a private network 10 and an external network, wherein: the unauthorized access detection apparatus 20 collects IP packets transmitted between the private network 10 and the external network, converts an IP address into domain names, and records the domain names as profile information; compares the domain names of each IP packet recorded as the profile information with a preset domain list (list in which appropriate domain names are registered); and detects, as packets to be investigated, IP packets of which the domain name is diagnosed as not being within the range of appropriate domain names recorded in the domain list.
Need to check novelty before this filing date? Find Prior Art

Description

Unauthorized Access Detection System

[0001] The present invention relates to a technique for detecting unauthorized access by collecting IP packets transmitted between a private network and an external network in IP communication (Internet Protocol Communication).

[0002] In recent years, as communication network environments have become larger and networks have become more interconnected, threats such as unauthorized access to network systems and cyberterrorism targeting critical infrastructure have increased, making it increasingly important to protect network environment resources from these unauthorized acts.

[0003] Particularly in an environment where networks are interconnected, monitoring IP packets transmitted between a private network and an external network to detect unauthorized access is an effective means of protecting the private network.

[0004] Patent Document 1 discloses that in an IP communication network system comprising a plurality of autonomous systems, border relay devices are placed at the boundaries of the plurality of autonomous systems, the border relay devices discard the unauthorized packets based on filtering information for detecting re-entry of the unauthorized packets, and distribute the filtering information to all other border relay devices within the same autonomous system, and further, a host computer within the autonomous system detects unauthorized access when the number of unauthorized attempts for each message type of the IP packet (e.g., ICMP, Telnet, ftp, ...) exceeds a predetermined threshold.

[0005] JP 2002-185539 (Patent No. 3723076)

[0006] As mentioned above, it is effective to detect unauthorized access by monitoring IP packets transmitted between a private network and an external network. For example, in Patent Document 1, unauthorized packets are detected based on the number of unauthorized attempts for each message type as predetermined judgment information.

[0007] However, the detection method of Patent Document 1 has a problem in that as the scale of the network increases, the total number of IP packets also increases, resulting in a heavy load.

[0008] In order to solve the above problems, an object of the present invention is to provide a system that collects IP packets transmitted between a private network and an external network, identifies the domain name of each IP packet, and detects malicious packets.

[0009] In order to achieve the above object, the invention of claim 1 is a system for detecting malicious packets transmitted between a private network and an external network in an IP communication network, comprising an malicious access detection device arranged at a relay point between the private network and the external network and detecting malicious packets transmitted by IP communication, the malicious access detection device comprising: a monitoring unit that collects IP packets transmitted between the private network and the external network; a DNS table creation unit that extracts DNS (Domain Name System) response packets from the IP packets collected by the monitoring unit and creates a DNS table that associates IP addresses with domain names based on the packet information; a profile creation unit that converts source IP addresses and destination IP addresses contained in the IP packets collected by the monitoring unit into source domain names and destination domain names based on the DNS table information and records IP packet information including {date and time, source domain name, destination domain name} for each domain name as profile information; and an malicious packet detection unit that detects IP packets that could not be converted into source domain names or destination domain names in the profile creation unit as packets to be investigated, the malicious packet detection unit comprising: The system is characterized by comprising: a domain list in which valid domain names are registered; an invalid packet detection unit that compares the domain name of each IP packet recorded as profile information in the profile creation unit with the domain list, and detects, as a packet to be investigated, an IP packet whose domain name is diagnosed as not being included in the range of valid domain names registered in the domain list.

[0010] The invention of claim 2 is characterized in that, in the unauthorized access detection device of claim 1, the unauthorized packet detection unit has a domain list in which unauthorized domain names are registered in addition to legitimate domain names, and compares the domain name of each IP packet recorded as profile information in the profile creation unit with the domain list, and detects as an unauthorized packet an IP packet whose domain name is diagnosed as being included in the range of unauthorized domain names registered in the domain list.

[0011] The invention of claim 3 is characterized in that, in the unauthorized access detection device of claim 1 or claim 2, the unauthorized packet detection unit has a time list in which appropriate date and time information is registered, and compares the date and time information of each IP packet recorded as profile information in the profile creation unit with the time list, and detects IP packets whose date and time information is diagnosed as not being within the range of appropriate date and time information registered in the time list as packets to be investigated.

[0012] The invention according to claim 4 is the system according to claim 1, further comprising: a DNS resolver (Domain Name System Resolver) disposed within the private network; a DNS packet monitoring device M1 that collects DNS response packets transmitted by the DNS resolver and records information including {date and time, source IP address, domain name} from the packet information as DNS log information D1; and a DNS packet monitoring device M2 that collects DNS response packets transmitted by a NAT (Network Address Translation) compatible router disposed within the private network and records information including {date and time, source IP address, domain name} from the packet information as DNS log information D2; and the unauthorized access detection device executes identification means 1 that searches the DNS log information D1 based on the {date and time, domain name} information of the unauthorized packet / investigation target packet detected by the unauthorized packet detection unit, and identifies the unauthorized access terminal from the source IP address of the corresponding DNS packet, and The device is characterized in that it is provided with an unauthorized access terminal identification unit that, when the identification means 1 is unable to identify the unauthorized access terminal, executes identification means 2 that searches the DNS log information D2 based on the {date and time, domain name} information of the unauthorized packet / packet to be investigated detected by the unauthorized packet detection unit, and identifies the unauthorized access terminal from the source IP address of the corresponding DNS packet.

[0013] The invention of claim 5 is characterized in that, in claim 1, it comprises a DNS packet monitoring device M2 that collects DNS response packets transmitted by a NAT-compatible router located within the private network and records information including {date and time, source IP address, domain name} from the packet information as DNS log information D2, and the unauthorized access detection device comprises an unauthorized access terminal identification unit that searches the DNS log information D2 based on the {date and time, domain name} information of the unauthorized packet / packet to be investigated detected by the unauthorized packet detection unit, and executes means for identifying the unauthorized access terminal from the source IP address of the corresponding DNS packet.

[0014] The invention of claim 6 is characterized in that, in the unauthorized access detection device of claim 1, the unauthorized access detection unit has means for counting the number of IP packets for the same domain name for each fixed time slot from each IP packet recorded as profile information in the profile creation unit, and issuing an alert notification when the number of IP packets exceeds a preset threshold T1.

[0015] The invention of claim 7 is characterized in that, in the unauthorized access detection device of claim 1, the unauthorized access detection unit has means for counting the number of different domain names for each fixed time slot from each IP packet recorded as profile information in the profile creation unit, and issuing an alert notification when the number of domain names exceeds a preset threshold T2.

[0016] According to the present invention, by collecting IP packets transmitted between a private network and an external network, identifying the domain name of the IP packet, and comparing the domain name with a pre-defined domain list, it becomes possible to easily detect malicious packets / packets to be investigated. Furthermore, since it becomes possible to identify the target terminal related to the malicious packets / packets to be investigated, it becomes possible to take measures against unauthorized access at an early stage, and it is expected to be effective in protecting network environment resources from unauthorized access to network systems and malicious acts such as cyber terrorism targeting critical infrastructure.

[0017] FIG. 1 is a schematic diagram showing an example of a system configuration diagram illustrating an unauthorized access detection system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a functional configuration diagram of an unauthorized access detection device in the unauthorized access detection system according to an embodiment of the present invention. FIG. 3 is a schematic diagram showing an example of DNS table information created by a packet monitoring device in the unauthorized access detection system according to an embodiment of the present invention. FIG. 4 is a schematic diagram showing an example of profile information recorded by the unauthorized access detection device in the unauthorized access detection system according to an embodiment of the present invention. FIG. 5 is a flowchart showing an example of an unauthorized packet detection processing procedure executed by the unauthorized access detection device in the unauthorized access detection system according to an embodiment of the present invention. FIG. 6 is a schematic diagram showing an example of DNS log information recorded by the packet monitoring device in the unauthorized access detection system according to an embodiment of the present invention.

[0018] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the following embodiments.

[0019] FIG. 1 shows an example of a system configuration diagram of an unauthorized access detection system according to an embodiment of the present invention.

[0020] <System Configuration> As shown in Figure 1, the unauthorized access detection system is a system that detects unauthorized packets transmitted between a private network 10 and an external network in an IP communication network, and is equipped with an unauthorized access detection device 20 that is placed at a relay point between the private network 10 and the external network and detects unauthorized packets transmitted via IP communication.

[0021] The unauthorized access detection system also includes a DNS resolver 11 located within the private network 10, a DNS packet monitoring device M1 that collects DNS response packets transmitted by the DNS resolver 11 and records the packet information as DNS log information D1, and a DNS packet monitoring device M2 that collects DNS response packets transmitted by a NAT-compatible router 12 located within the private network 10 and records the packet information as DNS log information D2.

[0022] The unauthorized access detection device 20 collects IP packets transmitted between the private network 10 and an external network, identifies a domain name in each IP packet, and detects unauthorized packets / packets to be investigated by diagnosing the domain name.

[0023] In addition, the unauthorized access detection device 20 searches the DNS log information D1 based on the information of the unauthorized packets / packets to be investigated detected above, and if it finds a corresponding DNS packet, it executes the identification means 1 to identify the unauthorized access terminal from the DNS packet.

[0024] If the identification means 1 is unable to identify the unauthorized access terminal, the identification means 2 searches the DNS log information D2 based on the information of the unauthorized packet / investigation target packet, and executes the identification means 2 to identify the unauthorized access terminal from the corresponding DNS packet.

[0025] In the system configuration shown in Figure 1, a DNS resolver 11 is placed within the private network 10, but in a system in which the DNS resolver 11 is not placed, the system does not have a DNS packet monitoring device M1 that records DNS log information D1, and therefore the unauthorized access detection device 20 is configured to execute only the identification means 2 without executing the identification means 1.

[0026] <Functional Configuration> Next, the functional configuration of the unauthorized access detection device 20 will be described using the functional block diagram shown in Fig. 2. Fig. 2 shows an example of a functional configuration diagram of the unauthorized access detection device 20. As shown in Fig. 2, the unauthorized access detection device 20 includes a monitoring unit 21, a DNS table creation unit 22, a profile creation unit 23, an unauthorized packet detection unit 24, and an unauthorized access terminal identification unit 25.

[0027] The monitoring unit 21 collects IP packets transmitted between the private network 10 and an external network. Here, it is assumed that all IP packets are collected, and for example, a configuration may be adopted in which the period for collecting IP packets is appropriately set.

[0028] The DNS table creation unit 22 extracts DNS response packets from the IP packets observed by the monitoring unit 21, and creates a DNS table that associates IP addresses with domain names based on the packet information. For example, the information shown in Fig. 3 is recorded as DNS table information. In the example shown in Fig. 3, "IP addresses" and "domain names corresponding to IP addresses" are recorded as DNS table information.

[0029] Based on the DNS table information created by the DNS table creation unit 22, the profile creation unit 23 converts the source IP address and destination IP address contained in the IP packets collected by the monitoring unit 21 into a source domain name and a destination domain name, and records the IP packet information including {date and time, source domain name, destination domain name} for each domain name as profile information.

[0030] Profile information is recorded for each domain, for example, the information shown in Fig. 4. In the example of Fig. 4, for an IP packet whose source domain is <Domain-1>, "date and time information," "source information," and "destination information" are recorded in chronological order as profile information.

[0031] Here, "date and time information" includes, for example, holiday information <holiday>. Also, "source information" records packet information of <domain name: Domain-1> in chronological order, which includes information on <message type (TCP / UDP)> and <port number>. Also, "destination information" records packet information of <domain name: Domain-A> <domain name: Domain-B> ... in chronological order, which includes information on <message type (TCP / UDP)> and <port number>.

[0032] Furthermore, in the example of FIG. 4, for an IP packet whose destination domain is <Domain-2>, "date and time information," "source information," and "destination information" are recorded in chronological order as profile information.

[0033] Here, "date and time information" includes, for example, holiday information <holiday>. Also, "source information" records packet information of <domain name: Domain-C> <domain name: Domain-D> ... in chronological order, which includes information on <message type (TCP / UDP)> and <port number>. Also, "destination information" records packet information of <domain name: Domain-2> in chronological order, which includes information on <message type (TCP / UDP)> and <port number>.

[0034] As shown in the example of FIG. 4, the profile creation unit 23 records the profile information in chronological order for each source domain / destination domain.

[0035] The fraudulent packet detection unit 24 detects, as a packet to be investigated, an IP packet that could not be converted into a source domain name or a destination domain name by the profile creation unit 23. Here, the packet to be investigated indicates a packet that has been diagnosed as possibly being a fraudulent packet and therefore needs to be investigated.

[0036] The fraudulent packet detection unit 24 also has a domain list in which valid domain names are registered, and compares the domain name of each IP packet recorded as profile information in the profile creation unit 23 with the domain list, and detects as a packet to be investigated any IP packet whose domain name is diagnosed as not being included in the range of valid domain names registered in the domain list.

[0037] The fraudulent packet detection unit 24 also has a domain list in which fraudulent domain names are registered in addition to legitimate domain names, and compares the domain name of each IP packet recorded as profile information in the profile creation unit 23 with the domain list, and detects as a fraudulent packet any IP packet whose domain name is diagnosed as being included in the range of fraudulent domain names registered in the domain list.

[0038] Here, the domain list setting information can be updated (added, changed, deleted) manually or remotely as needed.

[0039] The fraudulent packet detection unit 24 also has a time list in which appropriate date and time information is registered, and compares the date and time information of each IP packet recorded as profile information in the profile creation unit 23 with the time list, and detects IP packets whose date and time information is diagnosed as not being within the range of appropriate date and time information registered in the time list as packets to be investigated.

[0040] The time list setting information can be updated (added, changed, deleted) manually or remotely as needed.

[0041] The unauthorized access terminal identification unit 25 searches the DNS log information D1 based on the {date and time, domain name} information of the unauthorized packet / packet to be investigated detected by the unauthorized packet detection unit 24, and executes identification means 1 to identify the unauthorized access terminal from the source IP address of the corresponding DNS packet.

[0042] If the identification means 1 is unable to identify the unauthorized access terminal, the unauthorized access terminal identification unit 25 searches the DNS log information D2 based on the {date and time, domain name} information of the unauthorized packet / packet to be investigated detected by the unauthorized packet detection unit 24, and executes identification means 2 to identify the unauthorized access terminal from the source IP address of the relevant DNS packet.

[0043] Here, since the source IP address of the malicious packet / investigation target packet detected by the malicious packet detection unit 24 is a global IP address converted by a NAT-compatible router, it is not possible to identify the malicious access terminal based on this IP address, and therefore it is necessary to execute the identification means 1 and the identification means 2.

[0044] 6 is an example of DNS log information D1 and DNS log information D2. In the example shown in Fig. 6, "date and time information," "sender information," and "domain name" are recorded as DNS log information. Here, "sender information" includes information on the IP address, message type (TCP / UDP), and port number.

[0045] In addition, in a system in which a DNS resolver 11 is not placed within the private network 10, there is no DNS packet monitoring device M1 that records DNS log information D1, and therefore the unauthorized access detection device 20 is configured to execute only the identification means 2 without executing the identification means 1.

[0046] The above is the basic configuration of the unauthorized access detection system, but in addition to unauthorized access, it also has the function of detecting DDoS attacks, spam mail, spoofing attacks, etc., which will be explained below.

[0047] The malicious packet detection unit 24 has means for extracting IP packets of the same domain name at regular time slots from each IP packet recorded as profile information in the profile creation unit 23, counting the number of IP packets for each domain name, and issuing an alert notification if the number of IP packets exceeds a preset threshold T1. In other words, if the number of accesses to the same domain increases within a certain period of time and exceeds the threshold T1, an alert notification is issued because there is a high possibility that an abnormal situation has occurred. The threshold T1 can also be set in advance for each domain, and can be updated as appropriate manually or remotely.

[0048] The malicious packet detection unit 24 also has means for counting the number of IP packets of different domain names for each fixed time slot from each IP packet recorded as profile information in the profile creation unit 23, and issuing an alert notification when the number of IP packets exceeds a preset threshold T2. In other words, when the number of accessed domains within a fixed period of time increases and exceeds the threshold T2, an alert notification is issued because there is a high possibility that an abnormal situation such as a spoofing attack or port scan attack has occurred. The aforementioned threshold T1 can also be set in advance, and can be updated manually or remotely as needed.

[0049] <Processing Procedure 1> Next, an unauthorized packet detection process in the unauthorized access detection device 20 will be described with reference to the flowchart shown in Fig. 5. Fig. 5 is a flowchart showing an example of an unauthorized packet detection process procedure, and each step will be described below.

[0050] <Step S11> Collect IP packets transmitted between the private network 10 and the external network. Here, it is assumed that all IP packets are collected, and for example, a period for collecting IP packets may be set appropriately.

[0051] <Step S12> Based on the DNS table information, the source IP address and destination IP address contained in the IP packets collected in step S11 are converted into a source domain name and a destination domain name, and the IP packet information including {date and time, source domain name, destination domain name} for each domain name is recorded as profile information.

[0052] Profile information is recorded for each domain, for example, the information shown in Fig. 4. In the example of Fig. 4, for an IP packet whose source domain is <Domain-1>, "date and time information," "source information," and "destination information" are recorded in chronological order as profile information.

[0053] Here, "date and time information" includes, for example, holiday information <holiday>. Also, "source information" records packet information of <domain name: Domain-1> in chronological order, which includes information on <message type (TCP / UDP)> and <port number>. Also, "destination information" records packet information of <domain name: Domain-A> <domain name: Domain-B> ... in chronological order, which includes information on <message type (TCP / UDP)> and <port number>.

[0054] In the example of FIG. 4, even for IP packets whose source domain is <Domain-1>, "date and time information," "source information," and "destination information" are recorded in chronological order as profile information.

[0055] Here, "date and time information" includes, for example, holiday information <holiday>. Also, "source information" records packet information of <domain name: Domain-C> <domain name: Domain-D> ... in chronological order, which includes information on <message type (TCP / UDP)> and <port number>. Also, "destination information" records packet information of <domain name: Domain-2> in chronological order, which includes information on <message type (TCP / UDP)> and <port number>.

[0056] <Step S13> IP packets that could not be converted to a source domain name or a destination domain name in step S12 are detected as packets to be investigated. Here, the packets to be investigated indicate packets that have been diagnosed as possibly being fraudulent packets and therefore require investigation.

[0057] <Step S14> Next, using a domain list in which valid domain names are registered, the domain name of each IP packet converted in step S12 is compared with the domain list to determine whether the domain name is included in the range of valid domain names registered in the domain list, and IP packets determined not to be included are detected as packets to be investigated. The domain list includes, for example, "domain names" and "organization names corresponding to domain names." The domain list can be updated (added, changed, deleted) manually or remotely as needed.

[0058] <Step S15> Next, using a domain list in which invalid domain names are registered in addition to valid domain names, the domain name of each IP packet converted in step S12 is compared with the domain list, and IP packets whose domain name is diagnosed as being included in the range of invalid domain names registered in the domain list are detected as invalid packets. The setting information of this domain list can be updated (added, changed, deleted) as appropriate manually or remotely.

[0059] <Step S16> Next, using the time list in which the appropriate date and time information is registered, the date and time information of each IP packet recorded as profile information in step S12 is compared with the time list to determine whether the date and time information is within the range of appropriate date and time information registered in the time list. IP packets that are determined not to be within the range are detected as packets to be investigated. The setting information of this time list may include, for example, "day of the week" and "time period corresponding to the day of the week." The setting information of the time list can also be updated (added, changed, deleted) manually or remotely as needed.

[0060] There may also be cases where no time list exists, in which case, although not shown in the flowchart, the process ends without performing step S16.

[0061] <Processing Procedure 2> Next, the unauthorized access terminal identification process in the unauthorized access detection device 20 will be described with reference to the flowchart shown in Fig. 7. Fig. 7 is a flowchart showing an example of the unauthorized access terminal identification process procedure, and each step will be described below.

[0062] <Step S21> Determine whether a DNS resolver 11 is installed in the private network 10. If a DNS resolver 11 is installed, proceed to step S22; if not, proceed to step S23.

[0063] <Step S22> Based on the {date and time, domain name} information of the unauthorized packet / investigation target packet detected in steps S14 / S15 / S16, the DNS log information D1 is searched and identification means 1 is executed to identify the unauthorized access terminal from the source IP address of the corresponding DNS packet. If the unauthorized access terminal can be identified in this step, the process ends; if not, the process proceeds to step S23.

[0064] In this identification means 1, based on the {date and time, domain name} information of the malicious packet / investigation target packet detected in steps S14 / S15 / S16, a match with the {date and time, domain name} in the DNS log information D1 is searched for, and if a match is found, the malicious access terminal is identified from the corresponding source information. Note that there may be a slight time lag between the date and time information of the malicious packet and the date and time information in the DNS log information D1, and the search process takes this into consideration.

[0065] <Step S23> Based on the {date and time, domain name} information of the malicious packet / packet to be investigated detected in steps S14 / S15 / S16, the DNS log information D2 is searched and the identification means 2 is executed to identify the malicious access terminal from the source IP address of the corresponding DNS packet.

[0066] In this identification means 2, based on the {date and time, domain name} information of the malicious packet / investigation target packet detected in steps S14 / S15 / S16, a match with the {date and time, domain name} in the DNS log information D2 is searched for, and if a match is found, the malicious access terminal is identified from the corresponding source information. Note that there may be a slight time lag between the date and time information of the malicious packet and the date and time information in the DNS log information D2, and the search process takes this into consideration.

[0067] Here, since the source IP address of the malicious packet / investigated packet detected in steps S14 / S15 / S16 is a global IP address converted by a NAT-compatible router, it is not possible to identify the malicious access terminal based on this IP address, and therefore it is necessary to execute the identification means 1 and the identification means 2.

[0068] Next, although not shown in this flowchart, it is also possible to notify a designated information terminal of information relating to the unauthorized access terminal identified in step S23. The information terminal to which the notification is to be sent is set in advance, and the setting information can be updated manually or remotely as needed.

[0069] The "illegal packet detection process" and "illegal access terminal identification process" described above may be realized as a method executed by a computer, or may be realized as a program to be executed by a computer.

[0070] <Other system configurations> In the system configuration diagram shown in Figure 1, the unauthorized access detection device 20 is configured to be placed at a relay point between the private network 10 and an external network, but it is also possible to configure the unauthorized access detection device 20 to be placed within the private network 10.

[0071] In this case, the source IP address of the malicious packet / investigation target packet detected by the malicious packet detection unit 24 is the private IP address before being converted by the NAT-compatible router, so it is possible to identify the malicious access terminal based on this IP address.

[0072] Therefore, in this case, the DNS packet monitoring device M1 that records DNS log information D1 and the DNS packet monitoring device M2 that records DNS log information D2 shown in the system configuration diagram of FIG. 1 are not required.

[0073] REFERENCE SIGNS LIST 10 Private network 11 DNS resolver 12 NAT compatible router 20 Unauthorized access detection device 21 Monitoring unit 22 DNS table creation unit 23 Profile creation unit 24 Unauthorized packet detection unit 25 Unauthorized access terminal identification unit M1 DNS packet monitoring device M2 DNS packet monitoring device D1 DNS log information D1 DNS log information

Claims

1. A system for detecting unauthorized packets transmitted between a private network and an external network in an IP communication network, comprising: an unauthorized access detection device disposed at a relay point between the private network and the external network and detecting unauthorized packets transmitted by IP communication, the unauthorized access detection device comprising: a monitoring unit for collecting IP packets transmitted between the private network and the external network; a DNS table creation unit for extracting DNS response packets from the IP packets collected by the monitoring unit and creating a DNS table that associates IP addresses with domain names based on the packet information; a profile creation unit for converting a source IP address and a destination IP address contained in the IP packets collected by the monitoring unit into a source domain name and a destination domain name based on the DNS table information and recording IP packet information including {date and time, source domain name, destination domain name} for each domain name as profile information; and an unauthorized packet detection unit for detecting IP packets that could not be converted into a source domain name or destination domain name by the profile creation unit as packets to be investigated, the unauthorized packet detection unit having a domain list in which valid domain names are registered, an unauthorized packet detection unit that compares the domain name of each IP packet recorded as profile information in the profile creation unit with the domain list, and detects, as a packet to be investigated, an IP packet whose domain name is diagnosed as not being included in the range of appropriate domain names registered in the domain list.

2. An unauthorized access detection system as described in claim 1, wherein in the unauthorized access detection device, the unauthorized packet detection unit has a domain list in which unauthorized domain names are registered in addition to legitimate domain names, and compares the domain name of each IP packet recorded as profile information in the profile creation unit with the domain list, and detects as an unauthorized packet an IP packet whose domain name is diagnosed as being included in the range of unauthorized domain names registered in the domain list.

3. An unauthorized access detection system as claimed in claim 1 or claim 2, characterized in that in the unauthorized access detection device, the unauthorized packet detection unit has a time list in which proper date and time information is registered, and compares the date and time information of each IP packet recorded as profile information in the profile creation unit with the time list, and detects IP packets whose date and time information is diagnosed as not falling within the range of proper date and time information registered in the time list as packets to be investigated.

4. An unauthorized access detection system as claimed in claim 1, comprising: a DNS resolver disposed within said private network; a DNS packet monitoring device M1 which collects DNS response packets transmitted by said DNS resolver and records information from said packet information including {date and time, source IP address, domain name} as DNS log information D1; and a DNS packet monitoring device M2 which collects DNS response packets transmitted by a NAT-compatible router disposed within said private network and records information from said packet information including {date and time, source IP address, domain name} as DNS log information D2, said unauthorized access detection device searches said DNS log information D1 based on the {date and time, domain name} information of the unauthorized packet / investigation target packet detected by said unauthorized packet detection section, and executes a specification means 1 which specifies the unauthorized access terminal from the source IP address of the relevant DNS packet, and if said specification means 1 is unable to specify the unauthorized access terminal, An unauthorized access detection system characterized by comprising an unauthorized access terminal identification unit that executes an identification means 2 that searches the DNS log information D2 based on the {date and time, domain name} information of the unauthorized packet / investigation target packet detected by the unauthorized packet detection unit and identifies the unauthorized access terminal from the source IP address of the corresponding DNS packet.

5. An unauthorized access detection system as described in claim 1, comprising a DNS packet monitoring device M2 that collects DNS response packets transmitted in a NAT-compatible router arranged within the private network and records information including {date and time, source IP address, domain name} from the packet information as DNS log information D2, and the unauthorized access detection device further comprises an unauthorized access terminal identification unit that searches the DNS log information D2 based on the {date and time, domain name} information of the unauthorized packet / packet to be investigated detected by the unauthorized packet detection unit, and executes a means for identifying the unauthorized access terminal from the source IP address of the corresponding DNS packet.

6. An unauthorized access detection system as described in claim 1, wherein in the unauthorized access detection device, the unauthorized access detection unit has a means for counting the number of IP packets of the same domain name for each fixed time slot from each IP packet recorded as profile information in the profile creation unit, and for issuing an alert notification when the number of IP packets exceeds a preset threshold T1.

7. An unauthorized access detection system as described in claim 1, wherein in the unauthorized access detection device, the unauthorized access detection unit has a means for counting the number of different domain names for each fixed time slot from each IP packet recorded as profile information in the profile creation unit, and for issuing an alert notification when the number of domain names exceeds a preset threshold T2.