JP7835641B2 - Software information management device, software information management method - Google Patents

Description

This invention relates to a device and method for managing software information related to software used in information systems.

Software used in information systems has security flaws known as vulnerabilities. If these vulnerabilities are left unaddressed, the system may be vulnerable to attacks such as unauthorized access by malicious third parties. Therefore, when operating information systems, it is necessary to continuously collect information on software vulnerabilities and take countermeasures as needed.

In the case of an information system composed of one or more software programs and/or one or more information devices provided by one or more suppliers, the manufacturer of the information system may not necessarily have a complete understanding of the software configuration of all information devices within the entire system. Therefore, there is a need for technologies that enable information system manufacturers and their users to appropriately determine the impact of vulnerability information based on the software configuration of each information device within the system.

As a technique for determining whether or not vulnerability information is affected, for example, Patent Document 1 is known. Patent Document 1 describes a vulnerability determination device that determines whether or not computer configuration information is related to vulnerability information, determines whether or not the configuration information related to the vulnerability information is related to service configuration information, and, based on the results of this determination, outputs the configuration information related to the service configuration information and notifies the system administrator.

Japanese Patent Publication No. 2010-67216

In the technology described in Patent Document 1, a computer possesses configuration information about its own software, and a vulnerability assessment device acquires this configuration information to determine whether or not it is related to vulnerability information. However, in the case of an information system consisting of numerous information devices, it is not always possible to acquire the software configuration information of each information device within the information system, making it difficult to apply the technology described in Patent Document 1.

This invention is based on the above background and aims to provide a technology for determining whether or not an information system, which is composed of one or more software programs and/or one or more information devices, is affected by vulnerability information.

The software information management device according to the present invention is a device for managing software information of an information system having a plurality of information devices, comprising: a configuration information database storing configuration information representing the software configuration of the plurality of information devices; a communication unit that receives vulnerability search information relating to a vulnerability to be searched , which is input to a search information terminal, from the search information terminal and transmits search results based on the vulnerability search information to the search information terminal; a search processing unit that searches the configuration information database for information devices having software related to the vulnerability based on the vulnerability search information received by the communication unit and outputs information of the searched information devices as search results to the communication unit; an impact range database storing attribute information representing the attributes of the software each of the plurality of information devices has; and an impact range estimation unit that estimates the impact range of the vulnerability in the information system based on the impact range database, wherein the search processing unit searches for information devices having software containing the vulnerability, prioritizing the configuration information corresponding to the impact range estimated by the impact range estimation unit from among the configuration information stored in the configuration information database .
The software information management method according to the present invention is a method for managing software information of an information system having multiple information devices using a computer , wherein the computer receives vulnerability search information relating to a vulnerability to be searched, which has been entered into a search information terminal, from the search information terminal , the computer estimates the scope of impact of the vulnerability in the information system based on an impact scope database in which attribute information representing the attributes of the software each of the multiple information devices has is stored, the computer searches the configuration information database for information devices having software containing the vulnerability , prioritizing the configuration information corresponding to the estimated scope of impact from the configuration information database in which the software configuration of the multiple information devices has been stored, based on the received vulnerability search information, and the computer transmits the information of the searched information devices to the search information terminal .

According to the present invention, a technology can be provided for determining whether or not there is an impact on vulnerability information in an information system composed of one or more software programs and/or one or more information devices.

This is a block diagram showing the functional configuration of a software information management system according to one embodiment of the present invention. This figure shows an example of a configuration information database. This figure shows an example of an impact scope database. This figure shows an example of a vulnerability-attribute information mapping database. This is a diagram showing an example of a supplier database. This is a sequence diagram showing the processing flow when registering configuration information in a software information management device. This sequence diagram shows the process flow when specifying software containing vulnerabilities as the target of a search and searching for the impact that software has on the managed information system. This sequence diagram shows the process flow when a user specifies vulnerability information they have obtained as the search target and searches for the impact that vulnerability information has on the managed information system. This sequence diagram illustrates the process flow when an information equipment supplier designates software containing vulnerabilities as a target for a search and then searches for the impact that software has on the information equipment in question. This figure shows an example of a screen for registering configuration information. This figure shows an example of a configuration information search screen.

The embodiments of the present invention will be described below with reference to the drawings.

Figure 1 is a block diagram showing the functional configuration of a software information management system according to one embodiment of the present invention. The software information management system S shown in Figure 1 is a system for managing software information of an information system composed of one or more software programs and/or one or more information devices, such as an automobile. It is configured by connecting a software information management device 1, a registration information terminal 2, and a search information terminal 3 to each other via a network 4.

The software information management device 1 comprises a control unit 10, an encryption control unit 20, an input unit 30, an output unit 40, a communication unit 50, a program storage unit 60, and a data storage unit 70.

The control unit 10 is configured using, for example, a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), and functions as a registration processing unit 61, an impact range estimation unit 62, and a search processing unit 63 by executing a program stored in the program storage unit 60. Details of the registration processing unit 61, impact range estimation unit 62, and search processing unit 63 will be described later. Note that in Figure 1, the program storage unit 60 is shown to contain the registration processing unit 61, impact range estimation unit 62, and search processing unit 63. In reality, programs corresponding to these functions are stored in the program storage unit 60, and the control unit 10 executes these programs to realize the registration processing unit 61, impact range estimation unit 62, and search processing unit 63 in the software information management device 1. Alternatively, programs and data for enabling the control unit 10 to function as the registration processing unit 61, impact range estimation unit 62, and search processing unit 63 may be introduced into the software information management device 1 from an external device or non-volatile storage medium and used within the software information management device 1.

The encryption control unit 20 performs encryption of input information and decryption of encrypted information. The encryption control unit 20 can perform encryption and decryption processing using, for example, well-known encryption algorithms. The encryption control unit 20 may be implemented as hardware independent of the control unit 10, or it may be incorporated into the software information management device 1 as part of the functions of the control unit 10.

The input unit 30 receives input operations performed by the administrator of the software information management device 1 and outputs the content of those input operations to the control unit 10. The output unit 40, under the control of the control unit 10, outputs predetermined information to the administrator of the software information management device 1, providing the administrator with necessary information. The input unit 30 and the output unit 40 are configured using, for example, a mouse, keyboard, and display.

The communication unit 50 operates in accordance with the control unit 10 and performs communication interface processing for sending and receiving various types of information between the software information management device 1 and the registration information terminal 2 and the search information terminal 3. Through the communication interface processing performed by the communication unit 50, registration configuration information 80 is transmitted from the registration information terminal 2, and vulnerability search information 90 is transmitted from the search information terminal 3 to the software information management device 1 via the network 4. Conversely, information transmitted from the software information management device 1 is transmitted to the registration information terminal 2 and the search information terminal 3 via the network 4.

The program storage unit 60 and the data storage unit 70 are configured using, for example, large-capacity non-temporary magnetic storage devices such as HDDs (Hard Disk Drives) or SSDs (Solid State Drives), or semiconductor storage devices. The program storage unit 60 stores various programs executed by the control unit 10, and the data storage unit 70 stores various data used in the processing of the control unit 10. Note that the program storage unit 60 and the data storage unit 70 may be implemented using a single common storage device, or they may be implemented using separate storage devices.

The program storage unit 60 stores programs corresponding to the registration processing unit 61, the impact scope estimation unit 62, and the search processing unit 63, respectively. The registration processing unit 61 acquires the registration configuration information 80 transmitted from the registration information terminal 2 to the software information management device 1 and registers the acquired registration configuration information 80 in the configuration information database 71 held by the data storage unit 70. The impact scope estimation unit 62 estimates the impact scope of the vulnerability represented by the vulnerability information specified by the user in the managed information system. The search processing unit 63 acquires the vulnerability search information 90 transmitted from the search information terminal 3 and searches the configuration information database 71 held by the data storage unit 70 for information devices related to the vulnerability specified in the acquired vulnerability search information 90. The operation of each of these functional blocks in the software information management device 1 realizes the software information management system S of this embodiment.

The data storage unit 70 stores a configuration information database 71, an impact scope database 72, a vulnerability-attribute information correspondence database 73, and a supplier database 74. The configuration information database 71 is a database containing configuration information (SBM: Software Bill of Materials) representing the software configurations of multiple information devices owned by the managed information system. The impact scope database 72 is a database containing attribute information representing the software attributes of each of the multiple information devices owned by the information system. The vulnerability-attribute information correspondence database 73 is a database containing vulnerability-attribute information representing the correspondence between publicly available vulnerability information and the attribute information stored in the impact scope database 72. The supplier database 74 is a database containing supplier information representing the suppliers that provide each of the multiple information devices owned by the information system. Details of these databases will be described later.

The registration information terminal 2 is an information terminal used by suppliers of each information device constituting the managed information system to register their respective configuration information with the software information management device 1. The configuration information entered by the supplier into the registration information terminal 2 is used to create the registered configuration information 80, either encrypted or unencrypted. The created registered configuration information 80 is transmitted from the registration information terminal 2 to the software information management device 1 via the network 4 and registered in the configuration information database 71.

The search information terminal 3 is an information terminal operated by a user of the software information management system S. For example, the manufacturer or administrator of a managed information system can, as a user of the software information management system S, input information about vulnerabilities to be searched for in that information system into the search information terminal 3. The vulnerability information entered by the user into the search information terminal 3 is transmitted as vulnerability search information 90 via the network 4 to the software information management device 1, and is used for searches performed by the software information management device 1.

Network 4 is configured using, for example, a LAN (Local Area Network), WAN (Wide Area Network), or the Internet, and transmits data between the software information management device 1, the registration information terminal 2, and the search information terminal 3. The software information management device 1, the registration information terminal 2, and the search information terminal 3 may be installed in the same location or in physically separate locations. Furthermore, these may be implemented on a single computer, or on a virtual computer or cloud service.

Next, the details of the configuration information database 71, the scope of impact database 72, the vulnerability-attribute information correspondence database 73, and the supplier database 74 will be explained with reference to Figures 2 to 5.

Figure 2 shows an example of the configuration information database 71. As shown in Figure 2, the configuration information database 71 is configured such that information shown in columns 711 and 712, for example, is recorded for each of the multiple records set for each information device of the managed information system.

Column 711 records the target device name, which is information used to identify each information device. For example, the target device name information corresponding to the function and role of each information device in the information system is recorded in column 711.

Column 712 records configuration information representing the software configuration of each information device. This configuration information may be recorded in an encrypted state to prevent easy access by third parties, or it may be recorded in an unencrypted state. Furthermore, to enable the search processing of the configuration information by the search processing unit 63 to be performed in an encrypted state, the configuration information may be recorded encrypted using a well-known searchable encryption method.

Figure 3 shows an example of the impact scope database 72. As shown in Figure 3, the impact scope database 72 is configured such that information shown in columns 721 to 724, for example, is associated with and recorded for multiple records set for each software owned by multiple information devices within the managed information system.

Column 721 records information about the parent class representing the classification of the information device corresponding to each software.

Column 722 records information about the target device name of the information equipment corresponding to each software. This includes information common to, for example, column 711 in Figure 2.

Column 723 records information representing the supplier name of the information equipment corresponding to each software.

Column 724 records attribute information representing the attributes of each software.

Figure 4 shows an example of a vulnerability-attribute information database 73. As shown in Figure 4, the vulnerability-attribute information database 73 is configured such that, for each publicly available vulnerability information, multiple records are set up, and the information shown in columns 731 and 732, for example, is recorded accordingly.

Column 731 records the CVE-ID (Common Vulnerabilities and Exposures ID), a unique identifier assigned to each vulnerability.

Column 732 records attribute information representing the attributes of the software affected by each vulnerability. This includes information common to, for example, column 724 in Figure 3.

Figure 5 shows an example of a supplier database 74. As shown in Figure 5, the supplier database 74 is configured such that information shown in columns 741 and 742, for example, is recorded for each supplier that supplies information equipment installed in the managed information system.

Column 741 records information representing the name of each supplier. This includes information common to, for example, column 723 in Figure 3.

Column 742 records information about the target device names of the information equipment supplied by each supplier. This column contains information common to, for example, column 711 in Figure 2 and column 722 in Figure 3.

Next, the processes executed in the software information management system S will be explained with reference to Figures 6 to 9. The following example describes a case where supplier A provides the Telematics Control Unit (TCU) to the information system, and this TCU has a TCP/IP stack manufactured by company X implemented on it.

Figure 6 is a sequence diagram showing the processing flow when registering configuration information in the software information management device 1. The processing shown in the sequence diagram of Figure 6 is executed by the software information management device 1 and the registration information terminal 2 when, for example, the configuration information of the TCU supplied by Company A is input to the registration information terminal 2.

In step S10, the registration information terminal 2 encrypts the input configuration information and combines it with the registrant information of Company A to create the registration configuration information 80. As mentioned above, encryption of the configuration information is not mandatory; the registration configuration information 80 may be created by combining the configuration information and registrant information without encryption. Furthermore, when encrypting, a general encryption method that prevents data retrieval such as keyword searches in the encrypted state may be used, or a searchable encryption method that allows data retrieval in the encrypted state may be used. For example, a searchable encryption method described in Japanese Patent Publication No. 2021-39143 can be used.

In step S20, the registration configuration information 80 created in step S10 is transmitted from the registration information terminal 2 to the software information management device 1. The registration configuration information 80 transmitted in step S20 is received by the communication unit 50 in the software information management device 1 and passed to the registration processing unit 61. This provides the software information management device 1 with the configuration information to be registered in the configuration information database 71 from supplier A.

In step S30, the registration processing unit 61 of the software information management device 1 acquires the registration configuration information 80 transmitted from the registration information terminal 2 in step S20. Then, the target device name of the information equipment is identified from the registrant information contained in the acquired registration configuration information 80. Here, for example, by referring to the impact scope database 72, the target device name corresponding to the supplier name indicated in the registrant information can be identified. In the example in Figure 6, "TCU" is identified as the target device name in step S30.

In step S40, the registration processing unit 61 registers the target device name identified in step S30 and the configuration information contained in the registration configuration information 80 obtained in step S20 in the configuration information database 71, associating them with each other. Here, for example, a new record is added to the configuration information database 71 shown in Figure 2. The target device name is stored in column 711 of this new record, and the configuration information corresponding to the registration configuration information 80 is registered in column 712. As a result, the configuration information obtained from the supplier is registered in the configuration information database 71 of the software information management device 1, either encrypted or unencrypted.

Figure 7 is a sequence diagram showing the process flow when specifying software containing vulnerabilities as the search target and searching for the impact that software has on the managed information system. The process shown in the sequence diagram of Figure 7 is executed by the software information management device 1 and the search information terminal 3 when, for example, Company B, an information system manufacturer, obtains publicly available vulnerability information and inputs information such as the software name and version name from that vulnerability information into the search information terminal 3.

In step S110, the search information terminal 3 transmits the entered software name, version name, and other information as vulnerability search information 90 to the software information management device 1. The vulnerability search information 90 transmitted in step S110 is received by the communication unit 50 in the software information management device 1 and passed to the impact scope estimation unit 62 and the search processing unit 63. This provides the software information management device 1 with vulnerability search information 90 regarding the vulnerability to be searched, from Company B, the user of the software information management system S. In the example in Figure 7, vulnerability search information 90 indicating that the software name specified as the search target is "X Company's TCP/IP stack" is transmitted from the search information terminal 3 to the software information management device 1.

In step S120, the impact scope estimation unit 62 of the software information management device 1 acquires the vulnerability search information 90 transmitted from the search information terminal 3 in step S110. It then extracts attribute information contained in the acquired vulnerability search information 90 and estimates the impact scope of the vulnerability specified in the vulnerability search information 90 based on this information. The estimated impact scope of the vulnerability in step S120 is passed from the impact scope estimation unit 62 to the search processing unit 63. Here, for example, by referring to the impact scope database 72, the target device name corresponding to the extracted attribute information can be identified, and that target device name can be estimated as the impact scope of the vulnerability. In the example in Figure 7, in step S120, the attribute information "TCP/IP" is extracted from the vulnerability search information 90, and the target device names "TCU" and "IVI" (In-Vehicle Infotainment) corresponding to this attribute information are identified in the impact scope database 72, thereby estimating the impact scope of the vulnerability.

In step S130, the search processing unit 63 obtains the vulnerability search information 90 transmitted from the search information terminal 3 in step S110. Then, it searches the configuration information database 71 for configuration information including the name of the software to be searched, as represented by the obtained vulnerability search information 90. This retrieves information devices in the configuration information database 71 that possess software related to the vulnerability specified as the search target.

In step S130, the search processing unit 63 prioritizes the scope of the vulnerability estimated by the scope of impact estimation unit 62 in step S120 when searching for configuration information. For example, the encryption control unit 20 decrypts only the configuration information corresponding to the scope of impact from the encrypted configuration information stored in the configuration information database 71, and searches for configuration information containing the software name to be searched, as represented by the vulnerability search information 90, within the decrypted configuration information. Alternatively, it searches for configuration information containing the software name to be searched, as represented by the vulnerability search information 90, targeting only the configuration information corresponding to the scope of impact from the configuration information encrypted using searchable encryption or from unencrypted configuration information in the configuration information database 71. In this way, the system can prioritize the configuration information corresponding to the scope of impact of the vulnerability estimated by the scope of impact estimation unit 62 from the configuration information stored in the configuration information database 71, and search for information devices having software related to the vulnerability designated as the search target.

However, when performing a search for configuration information prioritizing the scope of the vulnerability's impact in step S130, the search scope does not necessarily have to be limited to the scope of the vulnerability's impact. For example, if, as a result of performing a search for configuration information prioritizing the scope of the vulnerability's impact, no information devices with software related to the specified vulnerability are found, the search may be extended to include configuration information outside the scope of the vulnerability.

In step S140, the search results obtained in step S130 are sent from the search processing unit 63 to the communication unit 50. The communication unit 50 then sends a reply to the search information terminal 3, which sent the vulnerability search information 90 in step S110. As a result, the information of the information device searched in step S130 is transmitted from the software information management device 1 to the search information terminal 3 as information of information devices possessing software related to the vulnerability specified as the search target, and is provided to Company B, the user of the software information management system S. In the example in Figure 7, a TCU manufactured by Company A is searched as an information device possessing the "TCP/IP stack manufactured by Company X" specified as the search target, and the search results indicating that this TCU is affected by the vulnerability are provided to the user via the search information terminal 3.

Figure 8 is a sequence diagram showing the processing flow when a user specifies vulnerability information they have obtained as a search target and searches for the impact that vulnerability information has on the managed information system. The processing shown in the sequence diagram of Figure 8 is executed by the software information management device 1 and the search information terminal 3 when, for example, Company B, an information system manufacturer, obtains publicly available vulnerability information and inputs the identification information such as the CVE-ID attached to that vulnerability information into the search information terminal 3.

In step S210, the search information terminal 3 transmits the input identification information, such as the CVE-ID, as vulnerability search information 90 to the software information management device 1. The vulnerability search information 90 transmitted in step S210 is received by the communication unit 50 in the software information management device 1 and passed to the impact scope estimation unit 62 and the search processing unit 63. This provides the software information management device 1 with vulnerability search information 90 regarding the vulnerability to be searched, from Company B, the user of the software information management system S. In the example shown in Figure 8, vulnerability search information 90 indicating that the CVE-ID of the vulnerability information designated as the search target is "CVE-2022-99999" is transmitted from the search information terminal 3 to the software information management device 1.

In step S220, the impact scope estimation unit 62 of the software information management device 1 acquires the vulnerability search information 90 transmitted from the search information terminal 3 in step S210. Then, using the identification information such as the CVE-ID contained in the acquired vulnerability search information 90, attribute information corresponding to the vulnerability being searched is extracted from the vulnerability search information 90. Here, for example, by referring to the vulnerability-attribute information correspondence database 73, the attribute information corresponding to the CVE-ID represented by the vulnerability search information 90 can be identified and extracted as the attribute information corresponding to the vulnerability being searched. In the example in Figure 8, the attribute information corresponding to "CVE-2022-99999" is identified as "TCP/IP" in the vulnerability-attribute information correspondence database 73, and this attribute information is extracted as the attribute information corresponding to the vulnerability being searched.

In step S230, the impact scope estimation unit 62 estimates the impact scope of the vulnerability specified in the vulnerability search information 90 based on the attribute information extracted in step S220. The impact scope of the vulnerability estimated in step S230 is passed from the impact scope estimation unit 62 to the search processing unit 63. Here, for example, similar to step S120 in Figure 7, the target device name corresponding to the extracted attribute information can be identified by referring to the impact scope database 72, and that target device name can be estimated as the impact scope of the vulnerability. In the example in Figure 8, in step S230, the target device names "TCU" and "IVI" corresponding to "TCP/IP" extracted in step S220 are identified in the impact scope database 72, and the impact scope of the vulnerability is estimated.

In step S240, the search processing unit 63 acquires the vulnerability search information 90 transmitted from the search information terminal 3 in step S210. Then, using the identification information such as the CVE-ID contained in the acquired vulnerability search information 90, the software to be searched is identified. For example, by accessing the servers of public institutions or software companies that publish various vulnerability information and acquiring the vulnerability information corresponding to the identification information, the software to be searched can be identified. In the example in Figure 8, the software to be searched is identified as "X Company's TCP/IP stack."

In step S250, the search processing unit 63 searches the configuration information database 71 for configuration information including the name of the software to be searched, which was identified in step S240. This retrieves information devices in the configuration information database 71 that possess software related to the vulnerability specified as the search target.

Furthermore, in step S250, similar to step S130 in Figure 7, the search processing unit 63 prioritizes the scope of vulnerability estimated by the scope of impact estimation unit 62 in step S230 when searching for configuration information.

In step S260, the search results obtained in step S250 are sent from the search processing unit 63 to the communication unit 50. The communication unit 50 then sends a reply to the search information terminal 3, which sent the vulnerability search information 90 in step S210. As a result, the information of the information device searched in step S250 is transmitted from the software information management device 1 to the search information terminal 3 as information of information devices possessing software related to the vulnerability specified as the search target, and is provided to Company B, the user of the software information management system S. In the example in Figure 8, a TCU manufactured by Company A is searched as the information device corresponding to the CVE-ID of the vulnerability information specified as the search target, "CVE-2022-99999," and the search results indicating that this TCU is affected by the vulnerability are provided to the user via the search information terminal 3.

Figure 9 is a sequence diagram showing the process flow when an information equipment supplier designates software containing vulnerabilities as a search target and searches for the impact that software has on the information equipment. The process shown in the sequence diagram of Figure 9 is executed by the software information management device 1 and the search information terminal 3 when, for example, supplier B obtains publicly available vulnerability information and inputs information such as the software name and version name from that vulnerability information into the search information terminal 3.

In step S310, the search information terminal 3 transmits the entered software name, version name, and other information as vulnerability search information 90 to the software information management device 1, similar to step S110 in Figure 7. The vulnerability search information 90 transmitted in step S310 is received by the communication unit 50 in the software information management device 1 and passed to the impact scope estimation unit 62 and the search processing unit 63.

In step S320, the impact scope estimation unit 62 of the software information management device 1 acquires the vulnerability search information 90 transmitted from the search information terminal 3 in step S310. Then, similar to step S120 in Figure 7, attribute information contained in the acquired vulnerability search information 90 is extracted, and based on this, the impact scope database 72 is referenced to estimate the impact scope of the vulnerability specified in the vulnerability search information 90.

In step S330, the impact scope estimation unit 62 sets a limited search range for each supplier (user) based on the vulnerability's impact scope estimated in step S320. The search range set in step S330 is passed from the impact scope estimation unit 62 to the search processing unit 63. Here, for example, by referring to the supplier database 74, the system identifies the target device names of the information equipment supplied to the information system by the supplier who sent the vulnerability search information 90 using the search information terminal 3. Then, from the target device names estimated as part of the vulnerability's impact scope in step S320, only the identified target device names are set as the search range for that supplier. In the example in Figure 9, of the target device names "TCU" and "IVI" estimated as part of the vulnerability's impact scope in step S320, only "TCU" is set as the search range for Company B.

In step S340, the search processing unit 63 acquires the vulnerability search information 90 transmitted from the search information terminal 3 in step S310. Then, the configuration information, including the name of the software to be searched, represented by the acquired vulnerability search information 90, is searched from the configuration information database 71, limited to the search range set by the impact scope estimation unit 62 in step S330. This retrieves information devices in the configuration information database 71 that have software related to the vulnerability specified as the search target.

In step S350, the search results obtained in step S340 are sent from the search processing unit 63 to the communication unit 50. The communication unit 50 then sends a reply to the search information terminal 3, which sent the vulnerability search information 90 in step S310. As a result, the information of the information device searched in step S340 is transmitted from the software information management device 1 to the search information terminal 3 as information of information devices possessing software related to the vulnerability specified as the search target, and is provided to Company B, the user of the software information management system S. In the example in Figure 9, similar to the case in Figure 7 described above, a TCU manufactured by Company A is searched as an information device possessing the "TCP/IP stack manufactured by Company X" specified as the search target, and the search results indicating that this TCU is affected by the vulnerability are provided to the user via the search information terminal 3.

In the software information management system S of this embodiment, the software information of an information system having multiple information devices is managed by the software information management device 1, the registration information terminal 2, and the search information terminal 3, respectively, performing the processes described above. This allows users such as the manufacturer, administrator, and suppliers of information devices to easily determine whether or not there is an impact on vulnerability information for an information system consisting of numerous information devices.

Next, an example of a display screen in the software information management system S will be described below with reference to Figures 10 and 11.

Figure 10 shows an example of a configuration information registration screen. The registration screen 100 shown in Figure 10 is displayed on the registration information terminal 2 when a supplier inputs configuration information for their provided information equipment, for example, before the start of the process shown in the sequence diagram of Figure 6. This registration screen 100 is presented to the supplier, for example, by being displayed on an unillustrated display of the registration information terminal 2, and functions as a user interface for inputting configuration information to be registered in the configuration information database 71.

The registration screen 100 includes input fields 101 to 103 and a registration button 104. Input field 101 is for entering the file name of the configuration information to be registered. Input field 102 is for entering the supplier name from the registrant information. Input field 103 is for entering the target device name from the registrant information. The supplier can input configuration information to be registered in the configuration information database 71 by operating an input device (mouse, keyboard, etc.) not shown on the registration information terminal 2 and entering this information in input fields 101 to 103.

The registration button 104 is an operation button used to instruct the registration of the entered configuration information. When the supplier enters the necessary information into input fields 101 to 103 on the registration screen 100 and selects the registration button 104, the entered information is registered in the registration information terminal 2, the registered configuration information 80 is created, and it is transmitted to the software information management device 1.

Figure 11 shows an example of a configuration information search screen. The search screen 110 shown in Figure 11 is displayed on the search information terminal 3 when a user, such as the manufacturer or administrator of the information system, specifies the software to be searched, for example, before the start of the process shown in the sequence diagram of Figure 7. This search screen 110 is presented to the user, for example, by being displayed on an unillustrated display of the search information terminal 3, and functions as a user interface for inputting search conditions for software containing vulnerabilities.

The search screen 110 includes an input field 111, a search results display field 112, and a confirmation button 113. The input field 111 is for entering search conditions as a query to the software information management device 1. The confirmation button 113 is an operation button that instructs the user to confirm whether or not the vulnerability resulting from the entered search conditions will have an impact on the information system. When a user enters search conditions in the input field 111 and selects the confirmation button 113 on the search screen 110, vulnerability search information 90 corresponding to those search conditions is created and sent to the software information management device 1.

The search results display frame 112 is the section for displaying search results. When the software information management device 1 executes a search process for configuration information based on the vulnerability search information 90 transmitted from the search information terminal 3, and the results are transmitted from the software information management device 1 to the search information terminal 3, the contents of the transmitted search results are displayed in the search results display frame 112. By checking the contents of the search results display frame 112, the user can confirm whether or not the vulnerability corresponding to the specified search conditions has an impact on the information system, and, if so, the scope of the impact on the information system.

According to the embodiment of the present invention described above, the following effects and benefits can be obtained.

(1) The software information management device 1 is a device that manages software information for an information system having multiple information devices. The software information management device 1 includes a configuration information database 71 that stores configuration information representing the software configurations of multiple information devices, a communication unit 50 that receives vulnerability search information 90 related to the vulnerability to be searched from the user and transmits search results based on the vulnerability search information 90 to the user, and a search processing unit 63 that searches the configuration information database 71 for information devices having software related to the vulnerability based on the vulnerability search information 90 received by the communication unit 50, and outputs the information of the searched information devices to the communication unit 50 as a search result. In this way, it is possible to determine whether or not there is an impact on the vulnerability information for an information system consisting of a large number of information devices.

(2) The software information management device 1 includes an impact range database 72 that stores attribute information representing the attributes of software possessed by multiple information devices, and an impact range estimation unit 62 that estimates the impact range of vulnerabilities in the information system based on this impact range database 72. The search processing unit 63 searches for information devices that have software related to vulnerabilities, prioritizing the configuration information from the configuration information database 71 that corresponds to the impact range estimated by the impact range estimation unit 62 (steps S130, S250). In this way, the scope of the search for configuration information from the configuration information database 71 can be narrowed, thereby reducing the processing load.

(3) The search processing unit 63 searches for information devices having software related to the vulnerability, limiting the search to configuration information corresponding to the scope of impact from the configuration information database 71. Specifically, the software information management device 1 includes a supplier database 74 that stores supplier information representing the suppliers that provide multiple information devices. If the user is a supplier of one of the multiple information devices, the scope of impact estimation unit 62 sets the search scope for that supplier within the scope of impact based on the supplier database 74 (step S330). The search processing unit 63 searches for information devices having software related to the vulnerability, limiting the search to configuration information corresponding to the search scope set in step S330 from the configuration information database 71 (step S340). In this way, when the user is a supplier, the scope of the search for configuration information from the configuration information database 71 can be limited to the scope of information devices provided by that supplier, thereby preventing the erroneous disclosure of configuration information of information devices unrelated to that supplier and ensuring security.

(4) The software information management device 1 includes a registration processing unit 61 that acquires configuration information provided by multiple information equipment suppliers and registers the acquired configuration information in the configuration information database 71. In this manner, the contents of the configuration information database 71 can be updated as needed using the configuration information provided sequentially by the suppliers.

(5) The registration processing unit 61 can obtain encrypted configuration information from the supplier and register it in the configuration information database 71. This prevents the leakage of configuration information and ensures security.

(6) The software information management device 1 includes an encryption control unit 20 that decrypts the configuration information registered in the configuration information database 71 in an encrypted state, within the scope of its impact. The search processing unit 63 can search for information devices having software related to the vulnerability from the configuration information decrypted by the encryption control unit 20 (step S130). In this way, even if the configuration information is registered in the configuration information database 71 in an encrypted state, only the necessary configuration information can be decrypted and searched. Therefore, the processing load can be reduced and speed can be increased, and security can be improved by further strengthening the prevention of leakage of configuration information.

(7) The registration processing unit 61 can also obtain configuration information encrypted using searchable encryption from the supplier and register it in the configuration information database 71. In this case, the search processing unit 63 searches for information devices having software related to the vulnerability from the configuration information registered in the configuration information database 71 in an encrypted state that falls within the scope of impact (step S130). In this way, even if the configuration information is registered in the configuration information database 71 in an encrypted state, a search can be performed without decryption. Therefore, the processing load can be further reduced and the speed can be increased.

(8) The software information management device 1 includes a vulnerability-attribute information correspondence database 73 in which vulnerability-attribute information representing the correspondence between publicly available vulnerability information and attribute information is stored. The impact scope estimation unit 62 extracts attribute information corresponding to the vulnerability information specified in the vulnerability search information 90 from the vulnerability-attribute information correspondence database 73 (step S220), and estimates the impact scope based on the extracted attribute information (step S230). In this way, when performing a search using publicly available vulnerability information, the impact scope of the vulnerability represented by that vulnerability information can be appropriately estimated.

It goes without saying that the present invention is not limited to the embodiments described above, and can be modified in various ways without departing from its essence. For example, the embodiments described above are detailed for the purpose of clearly illustrating the present invention, and are not necessarily limited to those comprising all the described components. Furthermore, it is possible to add, delete, or replace some of the components of the above embodiments.

Furthermore, some or all of the above configurations, functional units, processing units, and processing means may be implemented in hardware, for example, by designing them as integrated circuits. Alternatively, the above configurations and functions may be implemented in software by a processor interpreting and executing programs that realize each function. Information such as programs, tables, and files that realize each function can be stored in memory, hard disks, SSDs, or other recording devices, or on recording media such as IC cards, SD cards, or DVDs.

Furthermore, in the diagrams above, the control lines and information lines shown are those deemed necessary for explanation and do not necessarily represent all control lines and information lines in the actual implementation. For example, it can be assumed that almost all components are interconnected in practice.

Furthermore, the arrangement of the various functional units, processing units, and databases described above is merely an example. The arrangement of these functional units, processing units, and databases can be changed to the optimal configuration from the perspective of the performance, processing efficiency, and communication efficiency of the hardware and software of these devices.

1: Software Information Management Device, 2: Registration Information Terminal, 3: Search Information Terminal, 4: Network, 10: Control Unit, 20: Cryptographic Control Unit, 30: Input Unit, 40: Output Unit, 50: Communication Unit, 60: Program Storage Unit, 61: Registration Processing Unit, 62: Impact Scope Estimation Unit, 63: Search Processing Unit, 70: Data Storage Unit, 71: Configuration Information Database, 72: Impact Scope Database, 73: Vulnerability-Attribute Information Correspondence Database, 74: Supplier Database, 80: Registered Configuration Information, 90: Vulnerability Search Information

Claims (9)

A device for managing software information of an information system having multiple information devices,
A configuration information database containing configuration information representing the software configurations of the aforementioned multiple information devices,
A communication unit that receives vulnerability search information regarding the target vulnerability entered into the search information terminal from the search information terminal and transmits search results based on the vulnerability search information to the search information terminal ,
A search processing unit, based on the vulnerability search information received by the communication unit, searches the configuration information database for information devices having software containing the vulnerability, and outputs the information of the searched information devices to the communication unit as the search results.
A database of influence containing attribute information representing the software attributes of each of the aforementioned multiple information devices,
The system includes an impact range estimation unit that estimates the impact range of the vulnerability in the information system based on the impact range database ,
The search processing unit is a software information management device that searches for information devices having software containing the vulnerability, prioritizing the configuration information among the configuration information stored in the configuration information database that corresponds to the scope of impact estimated by the scope of impact estimation unit . A software information management device according to claim 1 ,
The search processing unit is a software information management device that searches for information devices having software containing the vulnerability, limited to the configuration information corresponding to the scope of impact among the configuration information stored in the configuration information database. A software information management device according to claim 2 ,
The system includes a supplier database containing supplier information representing each of the suppliers that provide the aforementioned multiple information devices,
The impact scope estimation unit, if the user who entered the vulnerability search information into the search information terminal is a supplier of one of the multiple information devices, sets the search scope for that supplier within the impact scope based on the supplier database.
The search processing unit is a software information management device that searches for information devices having software containing the vulnerability, limited to the configuration information corresponding to the search range among the configuration information stored in the configuration information database. A software information management device according to claim 1 ,
A software information management device comprising a registration processing unit that acquires the configuration information entered into the registration information terminal from the registration information terminal and registers the acquired configuration information in the configuration information database. A software information management device according to claim 4 ,
The registration processing unit is a software information management device that obtains the encrypted configuration information from the registration information terminal and registers it in the configuration information database. A software information management device according to claim 5 ,
The system includes an encryption control unit that decrypts the configuration information registered in the configuration information database in an encrypted state with respect to the scope of influence,
The search processing unit is a software information management device that searches for information devices having software containing the vulnerability from the configuration information decrypted by the encryption control unit. A software information management device according to claim 5 ,
The registration processing unit obtains the configuration information encrypted using searchable encryption from the registration information terminal and registers it in the configuration information database.
The search processing unit is a software information management device that searches for information devices having software containing the vulnerability from among the configuration information registered in the configuration information database in an encrypted state, which is included in the scope of influence. A software information management device according to claim 1 ,
The system includes a vulnerability-attribute information correspondence database in which vulnerability-attribute information is stored, representing the correspondence between publicly available vulnerability information and the attribute information.
The impact scope estimation unit is a software information management device that extracts attribute information corresponding to the vulnerability information specified in the vulnerability search information from the vulnerability-attribute information correspondence database and estimates the impact scope based on the extracted attribute information. A method for managing software information of an information system having multiple information devices using a software information management device ,
The aforementioned software information management device receives vulnerability search information regarding the target vulnerability entered into the search information terminal from the search information terminal ,
The software information management device estimates the scope of the vulnerability in the information system based on an impact scope database in which attribute information representing the attributes of the software each of the multiple information devices has is stored.
Based on the vulnerability search information received, the software information management device searches the configuration information database for information devices having software containing the vulnerability , prioritizing the configuration information corresponding to the estimated scope of impact among the configuration information representing the software configuration of the plurality of information devices stored in the configuration information database.
A software information management method comprising transmitting the information of the information device retrieved by the software information management device to the search information terminal .