Information collection device, information collection method, and information collection program
The information collection system addresses the challenge of limited IoT device information by extracting and managing software and communication details, enabling proactive risk management and security incident handling for IoT devices.
Patent Information
- Application Number
- PCT/JP2023/019400
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-24
- Publication Date
- 2024-11-28
AI Technical Summary
Current technologies face challenges in performing risk management and security incident handling for IoT devices due to limited availability of software information and encrypted firmware, making it difficult to anticipate and prepare for potential threats.
An information collection system that includes an information collection device and an information extraction unit, which collects and extracts information about IoT devices, software, and communication protocols using OSINT and various extraction methods, allowing for proactive risk management and security incident handling.
Enables users to understand IoT device configurations and communications before use, facilitating software vulnerability management and communication whitelist control, thereby minimizing damage from security incidents.
Smart Images

Figure JP2023019400_28112024_PF_FP_ABST
Abstract
Description
Information collection device, information collection method, and information collection program
[0001] The present invention relates to an information collection device, an information collection method, and an information collection program.
[0002] Cyberattacks targeting supply chain vulnerabilities are becoming more prevalent and sophisticated. For this reason, risk management is becoming even more important when companies use IoT (Internet of Things) devices. Furthermore, understanding in advance what software is included in the IoT devices and what kind of communications are taking place is crucial for promptly responding to security incidents. Therefore, there is a demand for technology to collect information about IoT devices for risk management and security incident response.
[0003] A known technology for collecting information about IoT devices is the Software Bill of Materials (SBOM), which represents and manages software configuration information (such as the author, name, and version of an application, and hash values of files) (see, for example, Non-Patent Document 1). A known firmware analysis technique analyzes the firmware of an IoT device and, when a binary similar to an index software binary is found, determines that the software is being used (see, for example, Non-Patent Document 2). Another known technology is to estimate the configuration of an IoT device based on operational information of the IoT device, and to complement and correct configuration information about the IoT device and IoT system.
[0004] SBOM, [online], [Retrieved May 12, 2023], Internet <https: / / www.ntia.gov / files / ntia / publications / sbom_at_a_glance_ja.pdf> Discovery of IoT device supply chain security issues and a large-scale field survey focusing on software differences, Shugo Shiraishi, Ryota Yoshimoto, Eitaro Shioji, Mitsuaki Akiyama, Toshihiro Yamauchi, Research Report Security Psychology and Trust (SPT), [online], [Retrieved May 12, 2023], Internet <2022 https: / / ipsj.ixsq.nii.ac.jp / ej / index.php?active_action=repository_view_main_item_detail&page_id=13&block_id=8&item_id=216671&item_no=1>
[0005] However, conventional technologies may not be able to proactively manage risks or deal with security incidents. For example, while SBOM is beginning to gain popularity, vendors are not obligated to disclose information, so information is currently only available in limited cases, making it difficult to proactively manage risks or deal with security incidents. When analyzing firmware, firmware is not always available, and even if it is available, it is often encrypted or protected by the developer to prevent misuse, so analysis is not always possible and only limited information can be analyzed. For this reason, firmware analysis may not be able to proactively manage risks or deal with security incidents.
[0006] Furthermore, a technology that estimates the configuration of an IoT device based on operational information of the IoT device and complements and corrects configuration information about the IoT device and IoT system presupposes that operational information is available, and it is not possible to evaluate a product before obtaining this information. Therefore, a technology that estimates the configuration of an IoT device and complements and corrects configuration information about the IoT device and IoT system may not allow risk management or security incidents to be handled in advance. An object of the present invention is to solve this problem and allow risk management and security incidents to be handled in advance.
[0007] In order to solve the above-mentioned problems, the present invention is characterized by having an information collection unit that collects information regarding IoT devices, and an information extraction unit that extracts information regarding at least one of the product of the IoT device, the software included in the IoT device, and the communication of the IoT device based on the information regarding the IoT device collected by the information collection unit.
[0008] According to the present invention, risk management and security incident handling can be carried out in advance.
[0009] FIG. 1 is a diagram illustrating an example of the configuration of an information collection system. FIG. 2 is a diagram illustrating an example of the information collection system. FIG. 3 is a diagram illustrating an example of an extraction method. FIG. 4 is a diagram illustrating an example of the configuration of the information collection system. FIG. 5 is a diagram illustrating an example of extraction based on IoT product information. FIG. 6 is a diagram illustrating an example of extraction based on manual / catalog information. FIG. 7 is a diagram illustrating an example of extraction based on search information. FIG. 8 is a diagram illustrating an example of extraction based on license information. FIG. 9 is a diagram illustrating an example of extraction based on vulnerability information. FIG. 10 is a flow diagram illustrating an example of a processing procedure executed by an information collection device. FIG. 11 is a flow diagram illustrating an example of a processing procedure executed by an information collection device. FIG. 12 is a flow diagram illustrating an example of a processing procedure executed by an information collection device. FIG. 13 is a diagram illustrating an example of the configuration of a computer that executes an information collection program.
[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings, but the present invention is not limited to the embodiment.
[0011] [Overview] First, an overview of an information collection system 1 will be described using Figures 1 to 3. Figure 1 is a diagram showing an example of the configuration of an information collection system. Figure 2 is a diagram for explaining an example of an information collection system. Figure 3 is a diagram for explaining an example of an extraction method. In the example of Figure 1, the information collection system 1 has an information collection device 10 and an IoT device 20. In the example of Figure 1, the information collection system 1 has only one IoT device 20, but may have multiple IoT devices 20.
[0012] The information collection device 10 of the information collection system 1 collects information about IoT devices and, based on the information about the IoT devices, extracts information about at least one of the IoT device's product, the software included in the IoT device, and the IoT device's communications. In the example of FIG. 2 , the information collection device 10 collects information about the IoT devices 20 (IoT device information) from web information about the Internet. Next, the information collection device 10 utilizes OSINT (Open Source Intelligence), a method for extracting information based on public information, to extract, based on the IoT device information, information about the IoT device's product, such as IoT device product names "A," "B," and "C" (IoT product information), information about software, such as "openssh / *" and "apache_http_server / *" (software information), and information about communications, such as "http / *" and "ssh / *" (communication information).
[0013] As a result, the information collection device 10 can allow a user, etc., to understand what software is included in an IoT device and what kind of communication will be performed by the IoT device before the user uses the IoT device. Therefore, the information collection device 10 can allow a user, etc., to perform risk management such as software vulnerability management and communication whitelist control, and to deal with security incidents in advance. As a result, even if a security incident occurs, the information collection device 10 can minimize damage.
[0014] Examples of extraction methods by which the information collecting device 10 extracts IoT product information, software information, and communication information include the five extraction methods shown in FIG. 3 . Each of the five extraction methods can extract information marked with a "○" from among IoT product information, software information, and communication information. Therefore, the information collecting device 10 extracts IoT product information using an extraction method based on IoT product information. The information collecting device 10 extracts software information based on at least one of information about at least one of a manual and a catalog (manual catalog information), information about search results (search information), information about licenses (license information), and information about vulnerabilities (vulnerability information). The information collecting device 10 extracts communication information based on at least one of manual / catalog information and search information. Details of each extraction method will be explained in the respective sections below.
[0015] [Example of configuration of information collection system] Next, an example of the configuration of the information collection system 1 will be described in detail with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of the information collection system. The information collection system 1 has an IoT device 20 and an information collection device 10.
[0016] [Example of Configuration of IoT Device] The IoT device 20 transmits IoT device information to the information collection device 10. An example of the IoT device 20 is a client terminal. In the example of Fig. 4, the IoT device 20 has a storage unit 21, a control unit 22, and a communication unit 23.
[0017] [Storage Unit] The storage unit 21 stores various information such as IoT device information, an OS (Operating System) and various programs executed by the IoT device 20. Examples of the storage unit 21 include storage devices such as HDD (Hard Disk Drive), SSD (Solid State Drive), and optical disks, and information-rewritable semiconductor memories such as RAM (Random Access Memory), flash memory, and NVSRAM (Non Volatile Static Random Access Memory).
[0018] [Control Unit] The control unit 22 controls the entire IoT device 20. For example, the control unit 22 is configured with one or more processors having an internal memory in which programs defining various processing procedures and control information are stored, and the processor executes each process using the programs and the internal memory. Examples of the control unit 22 include electronic circuits such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), and a GPU (Graphics Processing Unit), and integrated circuits such as an ASIC (Application Specific Integrated Circuit) and an FPGA (Field Programmable Gate Array).
[0019] [Communication Unit] The communication unit 23 transmits the IoT device information via a network such as the Internet connected to the communication unit 11 of the information collection device 10. For example, the communication unit 23 transmits the IoT device information regarding the IoT device 20 to a web server via the Internet. An example of the communication unit 23 is a network interface card (NIC).
[0020] [Example of Configuration of Information Collection Device] The information collection device 10 collects IoT device information and extracts at least one of IoT product information, software information, and communication information based on the IoT device information. The information collection device 10 may be, for example, a server. In the example of FIG. 4 , the information collection device 10 includes a communication unit 11, a control unit 12, and a storage unit 13.
[0021] [Communication Unit] The communication unit 11 receives IoT device information via a network such as the Internet connected to the communication unit 23 of the IoT device 20. For example, the communication unit 11 receives web information including IoT device information related to the IoT device 20 from a web server via the Internet. The communication unit 11 may transmit a response having response content estimated by the estimation unit 123 (described later) to the user's terminal. An example of the communication unit 11 is a NIC.
[0022] [Control Unit] The control unit 12 controls the entire information collection device 10. For example, the control unit 12 is configured with one or more processors having programs that define various processing procedures and internal memory that stores control information, and the processor executes each process using the programs and internal memory. Examples of the control unit 12 include electronic circuits such as a CPU, MPU, and GPU, and integrated circuits such as an ASIC and FPGA. In the example of FIG. 4, the control unit 12 has an information collection unit 121, an information extraction unit 122, and an estimation unit 123.
[0023] [Information Collecting Unit] The information collecting unit 121 collects information related to IoT devices. In the example of FIG. 4, the information collecting unit 121 collects IoT device information related to IoT device 20. The information collecting unit 121 may collect, as information related to IoT devices, information related to at least one of the IoT device's product, manual, catalog, search results, license, and vulnerability. In the example of FIG. 4, the information collecting unit 121 includes an IoT product information collecting unit 1211, a manual / catalog information collecting unit 1212, a search information collecting unit 1213, a license information collecting unit 1214, and a vulnerability information collecting unit 1215.
[0024] [IoT Product Information Collection Unit] The IoT product information collection unit 1211 collects IoT product information. For example, the IoT product information collection unit 1211 uses a search engine such as Google (registered trademark) to collect IoT product information including information on the product names of IoT devices from the following web information on the Internet: CPE (Common Platform Enumeration) list Google Hacking Database (DB) zoomeye.org / component
[0025] [Manual / Catalog Information Collection Unit] The manual / catalog information collection unit 1212 collects manual / catalog information. For example, the manual / catalog information collection unit 1212 uses a search engine to collect manual / catalog information including software information and communication information from web information on the Internet.
[0026] [Search Information Collecting Unit] The search information collecting unit 1213 collects search information. For example, the search information collecting unit 1213 utilizes a search engine to collect search information including software information and communication information from web information on the Internet.
[0027] The license information collection unit 1214 collects license information. For example, the license information collection unit 1214 uses a search engine to collect license information related to copyleft licenses applied to the GPL / LGPL from the web pages of IoT device vendors, using descriptions related to the GPL / LGPL, such as "source code subject to the GPL (General Public License) / LGPL (Lesser General Public License)," as search keywords.
[0028] [Vulnerability Information Collection Unit] The vulnerability information collection unit 1215 collects vulnerability information. For example, the vulnerability information collection unit 1215 utilizes a search engine to collect vulnerability information from web information on the Internet, such as past vulnerability information published on the web pages of IoT device vendors.
[0029] [Information Extraction Unit] The information extraction unit 122 extracts information about at least one of the IoT device product, the software included in the IoT device, and the communication of the IoT device, based on the information about the IoT device collected by the information collection unit 121. This allows the information extraction unit 122 to perform risk management and deal with security incidents in advance.
[0030] The information extraction unit 122 may extract information about the product name of the IoT device, the software name and version of the software, and the communication protocol name, communication destination, and communication port, based on information about at least one of the IoT device product, manual, catalog, search results, license, and vulnerability collected by the information collection unit 121. This allows the information extraction unit 122 to extract more detailed IoT product information, software information, and communication information, thereby enabling more appropriate risk management and security incident response in advance.
[0031] The information extraction unit 122 may extract description information related to at least one of the product name of the IoT device, the software name and version, the communication protocol name, the communication destination, and the communication port. For example, the information extraction unit 122 extracts at least one of keywords and expressions related to at least one of the product name of the IoT device, the software name and version, the communication protocol name, the communication destination, and the communication port. This allows the information extraction unit 122 to efficiently extract more detailed IoT product information, software information, and communication information, thereby enabling more appropriate risk management and efficient advance measures against security incidents.
[0032] An example of information extraction by the information extraction unit 122 will be described using Figures 4 to 9. Figure 5 is a diagram for explaining an example of extraction based on IoT product information. Figure 6 is a diagram for explaining an example of extraction based on manual / catalog information. Figure 7 is a diagram for explaining an example of extraction based on search information. Figure 8 is a diagram for explaining an example of extraction based on license information. Figure 9 is a diagram for explaining an example of extraction based on vulnerability information.
[0033] 4 and 5 , the information extraction unit 122 extracts IoT product information related to the product names of IoT devices from the IoT product information including information related to the product names of IoT devices collected by the IoT product information collection unit 1211. The information extraction unit 122 registers a list of the extracted product names of IoT devices in the IoT product information DB 131 shown in FIGS. 4 and 5 , which is a DB in which IoT product information is registered.
[0034] 4 and 6, the information extraction unit 122 extracts keywords related to the software name and communication protocol name of the software from the manual / catalog information collected by the manual / catalog information collection unit 1212. The information extraction unit 122 registers the extracted keywords related to the software name and communication protocol name of the software in the software / communication information DB 132 shown in FIGS. 4 and 6, which is a DB in which at least one of software information and communication information (software / communication information) is registered.
[0035] In the example of FIG. 6 , the software name does not include information about the version, and the protocol name does not include information about the version. Therefore, the information extraction unit 122 registers the symbol " / *" indicating that the version of the software name and protocol name is unknown in the software and communication information DB 132. Furthermore, as shown in the "software and communication information DB" of FIG. 6 , the information extraction unit 122 registers the symbol "-" indicating that information has not been extracted from the product name, software information, and communication information of the IoT device in the software and communication information DB 132. The information extraction unit 122 may further extract at least one of keywords and expressions related to at least one of the communication destination and communication port from the manual / catalog information and register the extracted information in the software and communication information DB 132.
[0036] 4 and 7, the information extraction unit 122 extracts at least one of a software name and version of the software and a keyword and expression related to a communication protocol name and a communication port from the search information related to the search results for the product name "D" collected by the search information collection unit 1213. The information extraction unit 122 registers the extracted software name and version of the software and at least one of a keyword and expression related to a communication protocol name and a communication port in the software and communication information DB 132 of FIGS.
[0037] In the example of "Search information related to search results for IoT devices with product name D" in FIG. 7, the communication content includes version "9.2" of the software "openssh." Therefore, as shown in the "Software and communication information DB" in FIG. 7, the information extraction unit 122 registers "openssh / 9.2" as software information in the software and communication information DB 132 in FIG. 4. In the example of "Search information related to search results for IoT devices with product name D" in FIG. 7, the communication port number for the protocol name "ssh" is "22," and the communication port number for the protocol name "http" is "80." Therefore, as shown in the "Software and communication information DB" in FIG. 7, the information extraction unit 122 registers "ssh / 22" and "http / 80" as communication information in the software and communication information DB 132 in FIG. 4.
[0038] 4 and 8, the information extraction unit 122 extracts information about the software name and version from the license information about the copyleft license applied to GPL / LGPL collected by the license information collection unit 1214. Specifically, the information extraction unit 122 accesses the license information about the copyleft license applied to GPL / LGPL, which is the search result, and downloads the source code that is applied to GPL / LGPL. In the example of "License information about source code included in IoT device with product name E" in FIG. 8, the information extraction unit 122 downloads the license information about the source code included in the IoT device with product name E.
[0039] From the source code name included in the license information for the downloaded source code, the information extraction unit 122 extracts the software name "busybox" and information "busybox / 1.28.3" related to the software version "1.28.3" corresponding to this software name. Similarly, the information extraction unit 122 extracts the software name "iptables" and information "iptables / 1.4.21" related to the software version "1.4.21" corresponding to this software name. As shown in the "software and communication information DB" of FIG. 8, the information extraction unit 122 registers the extracted "busybox / 1.28.3" and "iptables / 1.4.21" as software information in the software and communication information DB 132 of FIG. 4.
[0040] In the examples of FIGS. 4 and 9 , the information extraction unit 122 extracts information about the software name and version from the vulnerability information collected by the vulnerability information collection unit 1215. Specifically, the information extraction unit 122 extracts, from the vulnerability information, description information about the description of the software caused by the software vulnerability. If the software vulnerability is classified as a vulnerability by Common Weakness Enumeration (CWE)-1357 or CWE-1104, the vulnerability information also includes description information about the description of other software. In other words, if the software vulnerability is classified as a vulnerability due to a dependency on a vulnerable Open Source Software (OSS) component or the use of an unmaintained third-party component, the vulnerability information also includes description information about the description of other software. For this reason, the information extraction unit 122 also extracts description information about the description of other software.
[0041] From the vulnerability information "bash / 4.3" in the "Vulnerability Information Regarding Vulnerabilities in IoT Devices with Product Name F" in FIG. 9, the information extraction unit 122 extracts the software "bash / 4.3" corresponding to this vulnerability information as description information related to the software "bash / 4.3." The information extraction unit 122 also extracts another software "bash / 4.4" included in the vulnerability information "bash / 4.3" as description information related to the software "bash / 4.4." The information extraction unit 122 registers the extracted description information related to the software "bash / 4.3" with the software name "bash" and version "4.3" and the software "bash / 4.4" with the software name "bash" and version "4.4" as software information in the software and communication information DB 132 in FIG. 4.
[0042] The vulnerability information is linked to vendor information about the vendor of the IoT device, or the vendor information is published on the vendor's web page, so the information extraction unit 122 can determine that vulnerable software is being used by the IoT device. Furthermore, when vulnerability information is published, a patch or correction has already been completed, so the information extraction unit 122 can determine that a patched or corrected version of the software is being used.
[0043] [Estimation Unit] When the estimation unit 123 receives a request for information about at least one of the product, software, and communications of an IoT device, the estimation unit 123 estimates the content of a response to the request based on the information about at least one of the product, software, and communications of the IoT device extracted by the information extraction unit 122. For example, when the estimation unit 123 receives a request from a user's terminal or the like via the communication unit 11 regarding what kind of information at least one of IoT product information, software information, and communication information is, the estimation unit 123 estimates the content of a response to the request based on at least one of the IoT product information, software information, and communication information extracted by the information extraction unit 122. This allows the estimation unit 123 to estimate the content of a response according to the request.
[0044] The estimation unit 123 may estimate the response content based on information related to at least one of the product, software, and communication of the IoT device stored in the storage unit 13. For example, the estimation unit 123 searches for the product name of the IoT device in at least one of the IoT product information DB 131 and the software and communication information DB 132 stored in the storage unit 13, and estimates the software information and communication information obtained as the search result as the response content. As an example, when the estimation unit 123 receives a request for information related to an IoT device with a product name "B," the estimation unit 123 searches for the IoT device's product name "B" in the "Software and Communication Information DB" in FIG. 6. The estimation unit 123 estimates the software information "apache_http_server / *" and communication information "http / *" corresponding to the product name "B" obtained as the search result as the response content. This allows the estimation unit 123 to estimate the response content in response to the request.
[0045] [Storage Unit] The storage unit 13 stores information about at least one of the products, software, and communications of the IoT devices extracted by the information extraction unit 122. In the example of Fig. 4, the storage unit 13 stores various information such as an IoT product information DB 131 and a software / communication information DB 132, an OS and various programs executed by the information collection device 10, etc. Examples of the storage unit 13 include storage devices such as HDDs, SSDs, and optical discs, and rewritable semiconductor memories such as RAMs, flash memories, and NVSRAMs.
[0046] [Example of Processing Procedure] An example of processing procedures executed by the information collection device 10 will be described below with reference to Figures 10 to 12. Figures 10 to 12 are flow diagrams showing an example of processing procedures executed by the information collection device. First, with reference to Figure 10, an example of processing procedures for information collection processing, information extraction processing, and DB registration processing executed by the information collection device 10 will be described. In step S1, the information collection unit 121 collects information related to IoT devices. For example, when an IoT device 20 to be collected is determined, the information collection unit 121 collects at least one of IoT product information, manual / catalog information, search information, license information, and vulnerability information.
[0047] In step S2, the information extraction unit 122 extracts information about at least one of the IoT device product, the software included in the IoT device, and the communication of the IoT device, based on the information about the IoT device collected by the information collection unit 121. For example, the information extraction unit 122 extracts description information about at least one of the IoT device product name, the software name and version, and the communication protocol name, communication destination, and communication port, based on at least one of the IoT product information, manual / catalog information, search information, license information, and vulnerability information collected by the information collection unit 121.
[0048] In step S3, the information extraction unit 122 registers at least one of the IoT product information, software information, and communication information extracted in step S2 in the IoT product information DB 131 in Fig. 4 and the software and communication information DB 132 in Fig. 4. For example, each time at least one of the IoT product information, software information, and communication information is extracted in step S2, the information extraction unit 122 registers the extracted information in the IoT product information DB 131 and the software and communication information DB 132.
[0049] In step S4, the information extraction unit 122 determines whether or not the registration of the extracted information in the software and communication information DB 132 is complete. If the information extraction unit 122 determines that the registration is complete (Yes in step S4), the information extraction unit 122 stops the processing in step S5. If the information extraction unit 122 determines that the registration is not complete (No in step S4), the information extraction unit 122 returns to the processing of step S1.
[0050] Next, an example of the processing procedures for the information collection processing, information extraction processing, and DB registration processing executed by the information collection device 10 will be described in detail using FIG. 11. Steps S1α to S1ε in FIG. 11 are detailed representations of step S1 in FIG. 10, and steps S2α to S2ε in FIG. 11 are detailed representations of step S2 in FIG. 10. Steps S3 to S5 in FIG. 11 are similar to steps S3 to S5 in FIG. 10, and therefore will not be described here. In step S1α, the IoT product information collection unit 1211 collects IoT product information. For example, the IoT product information collection unit 1211 collects IoT product information when the IoT device 20 to be collected is determined.
[0051] In step S1β, the manual / catalog information collection unit 1212 collects manual / catalog information. For example, the manual / catalog information collection unit 1212 collects manual / catalog information when the IoT device 20 to be collected is determined.
[0052] In step S1γ, the search information collection unit 1213 collects search information. For example, when the IoT device 20 from which the search information is to be collected is determined, the search information collection unit 1213 collects the search information.
[0053] In step S1δ, the license information collection unit 1214 collects license information. For example, the license information collection unit 1214 collects license information when the IoT device 20 from which the license information is to be collected is determined.
[0054] In step S1ε, the vulnerability information collecting unit 1215 collects vulnerability information. For example, when the IoT device 20 from which vulnerability information is to be collected is determined, the vulnerability information collecting unit 1215 collects vulnerability information.
[0055] In step S2α, the information extraction unit 122 extracts the product name of the IoT product based on the IoT product information collected by the IoT product information collection unit 1211. For example, the information extraction unit 122 extracts the product name of the IoT product from the IoT product information every time IoT product information is collected by the IoT product information collection unit 1211 in step S1α.
[0056] In step S2β, the information extraction unit 122 extracts software and communication information based on the manual / catalog information collected by the manual / catalog information collection unit 1212. For example, each time manual / catalog information is collected by the manual / catalog information collection unit 1212 in step S1β, the information extraction unit 122 extracts keywords related to the software name and communication protocol name of the software from the manual / catalog information.
[0057] In step S2γ, the information extraction unit 122 extracts software and communication information based on the search information collected by the search information collection unit 1213. For example, each time search information is collected by the search information collection unit 1213 in step S1γ, the information extraction unit 122 extracts at least one of the software name and version of the software and keywords and expressions related to the communication protocol name and communication port from the search information.
[0058] In step S2δ, the information extraction unit 122 extracts software information based on the license information collected by the license information collection unit 1214. For example, each time license information is collected by the license information collection unit 1214 in step S1δ, the information extraction unit 122 extracts information about the software name and version of the software from the license information.
[0059] In step S2ε, the information extraction unit 122 extracts software information based on the vulnerability information collected by the vulnerability information collection unit 1215. For example, every time vulnerability information is collected by the vulnerability information collection unit 1215 in step S1ε, the information extraction unit 122 extracts information about the software name and version of the software from the vulnerability information.
[0060] Next, an example of the processing procedure of the estimation process and the response process executed by the information collection device 10 will be described with reference to FIG. 12 . In step S11, when the estimation unit 123 receives a request for information on at least one of the IoT device's product, software, and communications, the estimation unit 123 estimates the content of a response to the request based on the information on at least one of the IoT device's product, software, and communications extracted by the information extraction unit 122. For example, when the estimation unit 123 receives a request from a user for at least one of IoT product information, software information, and communications information, the estimation unit 123 searches for IoT product names in at least one of the IoT product information DB 131 and the software and communications information DB 132 in the storage unit 13, and estimates the software and communications information obtained as the search result as the content of a response to the request.
[0061] In step S12, the estimation unit 123 causes the communication unit 11 to respond with the response content estimated in step S11. For example, the estimation unit 123 causes the communication unit 11 to transmit the response content estimated in step S11 to the user's terminal.
[0062] [Modification] In the example of FIG. 11 , the information collection unit 121 executes the process corresponding to step S1 in FIG. 10 in the order of steps S1α to S1ε. However, the process corresponding to step S1 may be executed in any order as long as it precedes steps S2α to S2ε, S3, and S4. For example, the information collection unit 121 may execute the process of steps S1α to S1ε simultaneously. Similarly, the information extraction unit 122 executes the process corresponding to step S2 in FIG. 10 in the order of steps S2α to S2ε. However, the process corresponding to step S2 may be executed in any order as long as it precedes steps S1α to S1ε and S3 and S4. For example, the information extraction unit 122 may execute the process of steps S2α to S2ε simultaneously.
[0063] The components of each unit shown in the figure are conceptual functional units and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of the device is not limited to that shown, and all or part of it can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc. Furthermore, all or any part of the processing functions performed by the device can be realized by a CPU and a program executed by the CPU, or can be realized as hardware using wired logic.
[0064] Furthermore, among the above processes, all or part of the processes described as being performed automatically can be performed manually, and all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the processing procedures, specific names, various information, parameters, etc. shown in the above documents and drawings can be changed as desired unless otherwise specified.
[0065] [Program] The information collection device 10 can be implemented by installing an estimation program as package software or online software on a computer. For example, the computer can function as the information collection device 10 by executing the estimation program.
[0066] Fig. 13 is a diagram showing an example of a computer that executes an information collection program. In the example of Fig. 13, the computer 1000 has 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.
[0067] 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. For example, 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, for example, a mouse 1110 and a keyboard 1120. The video adapter 1060 is connected to, for example, a display 1130.
[0068] The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. In other words, the program that defines each process executed by the information collection device 10 is implemented as a program module 1093 in which computer-executable code is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, a program module 1093 for executing processes similar to those of the functional configuration of the information collection device 10 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced with an SSD.
[0069] Data used in the processing of the above-described embodiment is stored as program data 1094, for example, in the memory 1010 or the hard disk drive 1090. The CPU 1020 then reads the program module 1093 or the program data 1094 stored in the memory 1010 or the hard disk drive 1090 into the RAM 1012 as necessary and executes them.
[0070] The program module 1093 and program data 1094 are not limited to being stored in the hard disk drive 1090, but may be stored in a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or a wide area network (WAN)). The program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070.
[0071] REFERENCE SIGNS LIST 1 Information collection system 10 Information collection device 11 Communication unit 12 Control unit 13 Memory unit 20 IoT device 21 Memory unit 22 Control unit 23 Communication unit 121 Information collection unit 122 Information extraction unit 123 Estimation unit 131 IoT product information DB 132 Software / communication information DB 1211 IoT product information collection unit 1212 Manual / catalog information collection unit 1213 Search information collection unit 1214 License information collection unit 1215 Vulnerability information collection unit
Claims
1. An information collection device comprising: an information collection unit that collects information on an IoT (Internet of Things) device; and an information extraction unit that extracts information on at least one of the product of the IoT device, the software included in the IoT device, and the communication of the IoT device based on the information on the IoT device collected by the information collection unit.
2. The information collection device according to claim 1, characterized in that the information collection unit collects, as information about the IoT device, information about at least one of the products, manuals, catalogs, search results, licenses, and vulnerabilities of the IoT device.
3. The information collection device according to claim 2, characterized in that the information extraction unit extracts information regarding the product name of the IoT device, the software name and version of the software, and the communication protocol name, communication destination, and communication port based on information regarding at least one of the IoT device's product, the manual, the catalog, the search results, the license, and the vulnerability collected by the information collection unit.
4. The information collection device according to claim 3, characterized in that the information extraction unit extracts description information regarding at least one description of the product name of the IoT device, the software name and version of the software, and the protocol name, communication destination, and communication port of the communication.
5. The information collection device according to any one of claims 1 to 4, further comprising an estimation unit that, when receiving a request for information relating to at least one of the product of the IoT device, the software, and the communications, estimates the content of a response to the request based on the information relating to at least one of the product of the IoT device, the software, and the communications extracted by the information extraction unit.
6. The information collection device of claim 5, further comprising a memory unit that stores information regarding at least one of the product of the IoT device, the software, and the communication extracted by the information extraction unit, and the estimation unit estimates the response content based on the information regarding at least one of the product of the IoT device, the software, and the communication stored by the memory unit.
7. An information collection method executed by an information collection device, comprising: an information collection step of collecting information on an IoT (Internet of Things) device; and an information extraction step of extracting information on at least one of the product of the IoT device, the software included in the IoT device, and the communication of the IoT device based on the information on the IoT device collected by the information collection step.
8. An information collection program that causes a computer to execute an information collection step of collecting information on an IoT (Internet of Things) device, and an information extraction step of extracting information on at least one of the product of the IoT device, the software included in the IoT device, and the communication of the IoT device based on the information on the IoT device collected by the information collection step.
Citation Information
Patent Citations
Vulnerability management system and program
JP2020021309A
Information processing system
JP2023035334A
Cited By
Information processing system, information processing method and program
JP7775524B1
