Information management device, system, method, and program

Abstract

An information management device (1) that comprises: a first registration unit (11) that, in any first stage from a development stage for at least the first element among a plurality of elements that constitute an information system to an operation stage for the information system, acquires first evaluation information for a first element, associates the first evaluation information and first configuration information corresponding to the first element, and registers same in a database; a second registration unit (12) that, in a second stage from the development stage to the operation stage, other than the first stage, acquires first state information indicating the state of the first element and associates the first configuration information and the first state information and registers same in a database; and a display unit (13) that, in response to a display request, displays a plurality of pieces of configuration information corresponding to each of the plurality of elements by using a connection format on the basis of the relationship between the elements, and displays the first configuration information, the first state information, and the first evaluation information by using a connection format on the basis of the associations therebetween in the database.

Description

[Technical Field]

[0001] The present invention relates to an information management device, system, method, and computer-readable medium, and more particularly to an information management device, system, method, and computer-readable medium for managing configuration information of an information system. [Background technology]

[0002] An information system is made up of various components, such as hardware such as numerous information processing devices and network devices, software installed on each device, and the communication networks connecting these devices. Therefore, an information system is built by complex interactions between multiple components.

[0003] Furthermore, information systems are developed through component manufacturers, testing companies, and system integrators, and are then delivered to user companies, who then operate them. In this way, information systems involve a supply chain from manufacturers to user companies.

[0004] Patent Document 1 discloses a technique relating to a log collection control system that enables a system administrator to monitor the risk of vulnerabilities in devices that make up a system to be managed. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-170568 Summary of the Invention [Problem to be solved by the invention]

[0006] As the functionality of devices that make up information systems increases, they are now implemented with a variety of software, including open source software. This has resulted in the emergence of supply chain risks, for example, due to the increasing complexity of the internal configuration of network devices and the ease of modification. Supply chain risks here refer to risks arising from the supply chain, such as the incorporation of malicious programs or firmware tampering during the manufacturing and distribution processes of supply chain vendors involved in the information system construction stage. However, the technology disclosed in Patent Document 1 involves a system administrator collecting logs from an operating information system, and has the drawback of not being able to access information on the manufacturing and distribution processes of each component.

[0007] In view of the above-mentioned problems, the purpose of the present disclosure is to provide an information management device, system, method, and program for supporting the operation of an information system by sharing information obtained at each stage from manufacturing to operation regarding each component of the information system and the relationships between the elements. [Means for solving the problem]

[0008] An information management device according to a first aspect of the present disclosure includes: a first registration means for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system, at a first stage from a development stage of the first element to an operation stage of the information system, and for associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration means for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and for registering the first configuration information and the first status information in the database in association with each other; a display means for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; Equipped with.

[0009] An information management system according to a second aspect of the present disclosure includes: a database in which first configuration information corresponding to at least a first element among a plurality of elements constituting an information system is registered; an information management device connected to the database; Equipped with The information management device At a first stage from a development stage of the first element to an operation stage of the information system, first evaluation information for the first element is acquired, and the first configuration information and the first evaluation information are associated with each other and registered in the database; acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and registering the first configuration information and the first status information in the database in association with each other; In response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database.

[0010] An information management method according to a third aspect of the present disclosure includes: The computer acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at a first stage from a development stage of the first element to an operation stage of the information system; registering first configuration information corresponding to the first element and the first evaluation information in a database in association with each other; acquiring first status information indicating a status of the first element in a second stage other than the first stage from the development stage to the operation stage; registering the first configuration information and the first status information in the database in association with each other; In response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database.

[0011] A non-transitory computer-readable medium storing a program according to a fourth aspect of the present disclosure includes: a first registration process for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at any one of a development stage and an operation stage of the information system, and associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration process for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and associating the first configuration information with the first status information and registering them in the database; a display process for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; to be executed by the computer. [Effects of the Invention]

[0012] The present disclosure provides an information management device, system, method, and program for supporting the operation of an information system by sharing information obtained at each stage from manufacturing to operation regarding each component of the information system and the relationships between the elements. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram showing a configuration of an information management device according to a first embodiment. [Figure 2]1 is a flowchart showing the flow of an information management method according to the first embodiment. [Figure 3] FIG. 10 is a block diagram showing the overall configuration of an information management system according to a second embodiment. [Figure 4] FIG. 10 is a diagram for explaining the concept of sharing information regarding the information system according to the second embodiment. [Figure 5] FIG. 11 is a diagram illustrating an example of a configuration information table in a shared database according to the second embodiment. [Figure 6] 10A and 10B are diagrams illustrating examples of a state information table and an evaluation information table in a shared database according to the second embodiment. [Figure 7] FIG. 10 is a block diagram showing the configuration of an information management device according to a second embodiment. [Figure 8] FIG. 10 is a sequence diagram showing the flow of an information management method according to the second embodiment. [Figure 9] FIG. 10 is a sequence diagram showing the flow of an information management method according to the second embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a connection form of configuration information, status information, and evaluation information of an information system according to the second embodiment. [Figure 11] FIG. 10 is a diagram showing an example of display information of a plurality of pieces of configuration information, state information, and evaluation information according to the second embodiment. [Figure 12] FIG. 11 is a block diagram showing the configuration of an information management device according to a third embodiment. [Figure 13] FIG. 10 is a diagram showing the relationship between software configuration information and software inspection result information according to Example 3-1 of the third embodiment. [Figure 14] 10 is a flowchart showing the flow of update processing according to Example 3-1 of the third embodiment. [Figure 15] FIG. 10 is a diagram showing the relationship between software configuration information, hash value history, and software inspection result information according to Example 3-2 of the present embodiment 3. [Figure 16] 10 is a flowchart showing the flow of update processing according to Example 3-2 of the third embodiment. [Figure 17]FIG. 10 is a diagram showing an example of display information of a plurality of pieces of configuration information, state information, and evaluation information according to Example 3-2 of the present embodiment 3. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and for clarity of explanation, duplicate explanations will be omitted as necessary.

[0015] <Embodiment 1> 1 is a block diagram showing the configuration of an information management device 1 according to the first embodiment. The information management device 1 is an information processing device for managing information relating to an information system (not shown) that is made up of multiple elements. Here, the "elements" include the information system itself, hardware such as network devices and computer servers, and software, hardware components, software components, etc., installed on each piece of hardware. The "information system" is constructed through multiple stages, such as a development stage and an inspection stage for each of the multiple elements at various manufacturers, etc., and an integration stage in which a system integrator integrates the elements to construct an information system.

[0016] At each stage, each business operator, such as a manufacturer, an inspection company, or a system integrator, registers configuration information for each element in a database (not shown) via the information management device 1. Furthermore, each business operator acquires and generates status information and evaluation information for each element as needed at each stage and registers the information in the database via the information management device 1. At this time, the information management device 1 associates the configuration information with the status information or evaluation information and registers it in the database. Furthermore, for example, a system integrator inputs relationships between multiple elements to the information management device 1. In response, the information management device 1 associates multiple pieces of configuration information corresponding to each element based on the relationships between the elements and registers them in the database. Then, in the operation stage, the user business operator provides services by operating the information system constructed by the various businesses through each stage described above. Furthermore, in the operation stage, the information management device 1 visualizes and displays the relationships between multiple pieces of configuration information related to the information system and the relationships between each piece of configuration information and the status information or evaluation information in response to requests from the user business operator or other businesses.

[0017] Here, "configuration information" refers to information corresponding to an element. For example, configuration information includes the identification information, content, and specifications of an entire information system, equipment, model, software, component, etc. "Specifications" define the "intrinsic functions" of each system, equipment, component (hardware or software), etc., represented by the configuration information, and how they are provided to the outside world. For example, specifications define the physical or electrical input / output (physical actions, displays, sending and receiving of data and signals, etc.) of the target. By referencing and using this information, users of configuration information can objectively confirm whether the target system, equipment, or component is performing its "intrinsic functions." "Relationships between elements" refer to the connections, topology, and inclusion relationships between elements in an information system. Examples of relationships between elements include, but are not limited to, the relationship between a "finished product" element and its constituent "components," and the relationship between components of a specific finished product. "Status information" refers to information resulting from the operation or manipulation of an element. For example, status information includes logs of equipment and software, resource usage, etc. "Evaluation information" is information calculated based on any index for an element. For example, evaluation information may be inspection results for equipment, software, or the entire information system, security risk information, etc.

[0018] The information management device 1 includes a first registration unit 11, a second registration unit 12, and a display unit 13. The information management device 1 is connected to the above-mentioned database and the terminals of each business operator via a communication network. However, the information management device 1 may have a built-in database.

[0019] In the first stage, the first registration unit 11 acquires first evaluation information for the first element, associates first configuration information corresponding to the first element with the first evaluation information, and registers the first evaluation information in the database. Here, the first stage refers to any stage from the development stage of at least the first element among the multiple elements constituting the information system to the operation stage of the information system. In other words, the development stage to the operation stage include each stage in which each player (business operator) in the supply chain is involved in the development, inspection, integration, operation, etc. of each element of the information system.

[0020] The second registration unit 12 acquires first status information indicating the status of the first element in the second stage, associates the first configuration information with the first status information, and registers the information in the database. Here, the second stage refers to a stage other than the first stage among the development stage to operation stage of the information system described above. Therefore, the first and second stages may be performed in any order, or may be performed in parallel. However, the information management device 1 acquires and registers status information and evaluation information regarding at least the common first element in different stages, such as the first and second stages. Also, different players in the supply chain may be involved in the first and second stages. Alternatively, multiple departments within a single player may provide information and request registration in the first and second stages, respectively.

[0021] In response to a display request, the display unit 13 displays multiple pieces of configuration information corresponding to each of multiple elements in a connection topology based on the relationships between the elements. In addition, in response to a display request, the display unit 13 displays first configuration information, first status information, and first evaluation information in a connection topology based on the associations in the database. Here, the "connection topology" refers to a display topology that visualizes the associations between pieces of information, such as links between pieces of configuration information, or links between configuration information, status information, and evaluation information. The connection topology may be display information that visualizes a predetermined topology. For example, the connection topology may be a tree topology, a ring topology (loop topology), a daisy chain topology (line topology), a star topology, a bus topology, a mesh topology, or any other topology, or a combination of some or all of these.

[0022] FIG. 2 is a flowchart showing the flow of the information management method according to the first embodiment. First, in a first stage, the first registration unit 11 acquires first evaluation information for a first element among a plurality of elements (S11). For example, the first registration unit 11 receives the first evaluation information from a terminal of one of the above-mentioned businesses. At this time, the first registration unit 11 may acquire first configuration information corresponding to the first element together with the first evaluation information. Alternatively, the first configuration information may have been registered in a database in advance.

[0023] Next, the first registration unit 11 associates the first configuration information with the first evaluation information and registers them in the database (S12).

[0024] In addition, in a second stage different from the first stage, the second registration unit 12 acquires first status information indicating the status of the first element (S13). For example, the second registration unit 12 receives the first status information from a terminal of a carrier different from that of step S11. At this time, the second registration unit 12 may acquire the first configuration information together with the first status information.

[0025] Next, the second registration unit 12 associates the first configuration information with the first status information and registers them in the database (S14). Note that, although steps S11 and S12 and steps S13 and S14 are parallel in FIG. 2, as described above, these steps can be performed in any order. For example, steps S11 and S12 of the first stage may be performed first, and then steps S13 and S14 of the second stage may be performed. Alternatively, steps S13 and S14 of the second stage may be performed first, and then steps S11 and S12 of the first stage may be performed.

[0026] After steps S12 and S14, the display unit 13 receives a display request for information about the information system from the terminal of one of the above-mentioned businesses. At this point, the database is assumed to have registered a plurality of pieces of configuration information corresponding to each of the plurality of elements in association with each other based on the relationships between the elements. In response to the display request, the display unit 13 displays the plurality of pieces of configuration information in a connection form based on the relationships between the elements, and also displays the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database (S15). Step S15 may be executed consecutively in the later of the first and second stages.

[0027] As described above, in the first embodiment, status information and evaluation information for a specific element are acquired from different businesses at different times. The configuration information, status information, and evaluation information corresponding to the specific element are associated and registered in a common database. The information management device 1 then visualizes the associated configuration information, status information, and evaluation information in a predetermined connection configuration. Therefore, a user who has made a display request can easily understand the relationship between the configuration information, status information, and evaluation information. Furthermore, in the first embodiment, multiple pieces of configuration information are visualized in a connection configuration based on the relationships between the elements. Therefore, a supply chain player who has made a display request, such as a user business, can easily understand the relationships between multiple elements that make up an information system. The user business can then view the status information and evaluation information for a specific element by tracing the relationships between the configuration information. In other words, the user business can obtain information that cannot be obtained during the operational phase alone without inquiring with each business, thereby identifying security risks, etc., for the information system and taking appropriate measures. This reduces supply chain risks. Furthermore, manufacturers and other parties can easily access log information, alert information, and evaluation information by third parties during the operational phase. This information can also be used to improve their own products. Therefore, by sharing information about each component of an information system and the relationships between the components, acquired at each stage from manufacturing to operation, it is possible to support the operation of the information system.

[0028] The database described above is a storage location for electronic data realized by means that can be shared by each business. For example, the database may be connected to multiple computers via a network or the like and shared by each computer, and sharing may be realized by various means. In this case, the database is not limited to a relational database, and other database systems may be used. For example, the database may be placed on a publicly accessible web server and shared by freely accessing it using a uniform resource locator (URL) as the ID of the configuration information. Alternatively, the database may be shared by distributing it using a peer-to-peer (P2P) network. Alternatively, the database may be shared among each business using a blockchain. Alternatively, the database may be shared by writing it to an electronic recording medium such as a compact disc (CD) or a digital versatile disc (DVD) and periodically publishing it, which each business may obtain.

[0029] The information management device 1 includes a processor, a memory, and a storage device (not shown). The storage device stores a computer program that implements the processing of the information management method according to this embodiment. The processor then loads the computer program from the storage device into the memory and executes the computer program. This allows the processor to implement the functions of a first registration unit 11, a second registration unit 12, and a display unit 13.

[0030] Alternatively, each component of the information management device 1 may be realized by dedicated hardware. Furthermore, some or all of the components of each device may be realized by general-purpose or dedicated circuits, processors, etc., or a combination of these. These may be configured by a single chip, or by multiple chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and programs. Furthermore, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (Field-Programmable Gate Array), quantum processor (quantum computer control chip), etc., may be used as the processor.

[0031] <Embodiment 2> Here, we will explain again the problem that this embodiment aims to solve. First, a user company, which is the final player in the supply chain, acquires and monitors alert information and log information of an information system during the operation phase. However, the user company was unable to access detailed configuration information, inspection result history, and the like for each element in the information system. This was because the configuration information and inspection result history for each element of the information system, such as each product, component, and software, were managed by each player in the supply chain. Specifically, there was no mechanism for accessing inspection results conducted by equipment manufacturers during the development phase of the equipment during the operation phase. Therefore, when a user company acquired alert information for a given device in the information system, the alert information and log information alone were insufficient to determine the security risk, etc., of the target device. Therefore, for the user company, information on each element of the information system prior to the operation phase was unclear, resulting in the above-mentioned supply chain risk. Furthermore, because it took time for the user company to acquire and check the inspection result history before the start of operation, it was difficult to quickly determine the urgency and priority of the response. Therefore, this embodiment is designed to solve such problems.

[0032] The second embodiment is a specific example of the first embodiment described above. FIG. 3 is a block diagram showing the overall configuration of an information management system 1000 according to the second embodiment. The information management system 1000 manages, in a shared database 200, associations between configuration information, status information, and evaluation information partially registered by each business operator in a supply chain related to the construction of an information system 400, and relationships between each piece of configuration information. The information management system 1000 includes terminals 100-1 to 100-6, a shared database 200, an information management device 300, and an information system 400. The terminals 100-1 to 100-6, the shared database 200, the information management device 300, and the information system 400 are each connected via a network N. Here, the network N is a wired or wireless communication line or communication network. The network N does not matter what type of communication protocol is used.

[0033] The information system 400 is a management target of the information management system 1000. The information system 400 includes, for example, a NW (Network) device 41 and servers 42 and 43. However, the configuration of the information system 400 is not limited to this. The NW device 41 is a communication device that mediates communication between the network N and the servers 42 and 43. The NW device 41 may also form a LAN (Local Area Network) between the servers 42 and 43. The NW device 41 includes hardware 411 and software 412. The software 412 is a computer program installed on the hardware 411. The servers 42 and 43 are a group of computer servers that perform processing to provide services in the information system 400. The server 42 includes hardware 421 and software 422, and the server 43 includes hardware 431 and software 432. The software 422 is a computer program installed on the hardware 421. The software 432 is a computer program installed on the hardware 431. Furthermore, the hardware 411, 421, and 431, and the software 412, 422, and 432 are examples of "elements" that make up the information system 400. Therefore, the information system 400 may consist of at least one NW device 41. In this case, there are multiple elements, namely, the hardware 411 and the software 412, and there is a relationship between the elements in which the hardware 411 includes the software 412. Note that the hardware 411, etc. and the software 412, etc. may each include one or more hardware components or software components as components.

[0034] The shared database 200 is a database that associates multiple pieces of configuration information corresponding to each of the multiple elements that make up the information system 400 based on the relationships between the elements, and manages specific configuration information by associating it with status information and evaluation information for that configuration information.

[0035] The information management device 300 is an example of the information management device 1 described above. The information management device 300 receives configuration information, status information, evaluation information, relationships between elements, and the like from the terminals 100-1 to 100-6 via the network N, associates the information as appropriate, and registers the information in the shared database 200. Furthermore, when the information management device 300 receives a display request from the terminals 100-1 to 100-6 via the network N, it reads various information related to the information system 400 from the shared database 200 and generates display information in which the configuration information is connected in a connection form based on the relationships between the elements. Furthermore, the information management device 300 reads the configuration information, status information, and evaluation information associated in the shared database 200 in accordance with the display information, and generates display information in which the configuration information is connected in a connection form based on the association. The information management device 300 returns the generated display information to the requesting terminal and displays it on the screen of the terminal. Furthermore, the information management device 300 may be redundantly configured with multiple servers, and each functional block may be implemented by multiple computers. The detailed configuration of the information management device 300 will be described later.

[0036] Terminals 100-1 to 100-6 are information processing devices that access shared database 200 via information management device 300. For example, terminal 100-1 is operated by parts manufacturer P1, terminal 100-2 by equipment manufacturer P2, and terminal 100-3 by software vendor P3. Also, terminal 100-4 is operated by inspection company P4, terminal 100-5 by system integrator P5, and terminal 100-6 by user company P6. Terminals 100-1 to 100-6 are merely examples, and parts manufacturer P1, etc. may have two or more terminals.

[0037] 4 is a diagram for explaining the concept of information sharing in the information system according to the present embodiment 2. A parts manufacturer P1, an equipment manufacturer P2, a software vendor P3, an inspection company P4, a system integrator P5, and a user company P6 are examples of players in the supply chain in the information system 400.

[0038] The parts manufacturer P1 is a business that develops and manufactures some of the hardware components of the NW device 41, the server 42, or 43. The device manufacturer P2 is a business that develops and manufactures at least one of the products (devices) of the NW device 41, the server 42, or 43. The device manufacturer P2 may develop the hardware and software of the devices. The software vendor P3 is a business that develops the software of at least one of the NW device 41, the server 42, or 43.

[0039] For example, during the development stage of parts, equipment, and software, part manufacturer P1, device manufacturer P2, and software vendor P3 use terminal 100-1 or the like to generate configuration information 21 for parts, equipment, and software, and register it in shared database 200. During the development stage, part manufacturer P1 or the like may also generate status information and evaluation information (inspection information, etc.) for the relevant parts, etc., as needed, and register it in shared database 200. At this time, information management device 300 associates configuration information 21 for parts, etc. with status information 22 and evaluation information 23, and registers them in shared database 200. During the development stage, different businesses may develop multiple types of parts, equipment, and software.

[0040] The inspection business operator P4 is a business operator that inspects (tests) parts, equipment, software, or the entire information system 400. The inspection business operator P4 may perform inspections in response to requests from other businesses in the supply chain. In the inspection stage, the inspection business operator P4 uses the terminal 100-4 to generate status information and evaluation information (inspection information and security risk information) of the relevant parts, etc., and registers them in the shared database 200. At this time, the information management device 300 associates configuration information 21 of the parts, etc. with status information 22 and evaluation information 23, and registers them in the shared database 200.

[0041] The system integrator P5 is a business operator who constructs the information system 400 by developing application programs as needed and integrating various settings of the network devices 41, servers 42, and 43. In the integration stage, the system integrator P5 uses the terminal 100-5 to generate configuration information for the information system 400, specify relationships between elements, and register the information in the shared database 200. At this time, the information management device 300 associates each piece of configuration information 21 based on the relationships between the elements and registers it in the shared database 200. Note that in the development stage, the system integrator P5 may also generate status information and evaluation information (such as inspection information) for the information system 400 as needed and register it in the shared database 200. At this time, the information management device 300 associates the configuration information 21 with the status information 22 and evaluation information 23 of the information system 400 and registers them in the shared database 200.

[0042] User company P6 is a company that performs a final evaluation of the constructed information system 400 and performs operation and maintenance. In the evaluation stage, user company P6 uses terminal 100-6 to generate status information and evaluation information (security risk information) of the information system 400 and registers it in the shared database 200. At this time, the information management device 300 associates configuration information 21 of the information system 400 with status information 22 and evaluation information 23, and registers them in the shared database 200.

[0043] Thereafter, in the operation stage, the NW device 41, the server 42, and the server 43 each register their own log information and alert information in the shared database 200. At this time, the information management device 300 associates the corresponding configuration information 21 and status information 22 with each other and registers them in the shared database 200.

[0044] As a result, any of the parts manufacturer P1 to user business operator P6 can thereafter make a display request via terminal 100-1 or the like to view the display information of each configuration information, status information, and evaluation information of information system 400 registered in shared database 200. In other words, information that has been partially registered by multiple businesses at different times can be shared on the shared platform.

[0045] The present embodiment has the following application example. For example, in the development stage of a device, when a specific device manufacturer develops (produces) the device, it generates device configuration information that represents the configuration of the hardware and software of the device, and at the same time, adds "evaluation information" to the device configuration information as a self-evaluation of the device and shares it. After sharing this information, the device manufacturer then ships the device and distributes it to the market.

[0046] Furthermore, prior to the development stage of the device, in the development stage of components (individual components such as hardware components and software components) required for the development of the device, component manufacturers generate and share configuration information (and self-assessment evaluation information) corresponding to the components. Then, after sharing the component configuration information, the component manufacturers ship the components and distribute them to the market.

[0047] Furthermore, after developing (producing) a product or part, the equipment manufacturer or part manufacturer may request a third-party organization (inspection business operator) to evaluate the product or part. In this case, at the inspection stage (evaluation stage) of the product, the inspection business operator adds "evaluation information," which is the evaluation result of the product, to the "composition information" of the product, and shares it. This allows the equipment manufacturer or part manufacturer to refer to the evaluation information associated with the composition information of the product, etc., to confirm the reliability of the product, etc., before shipping the product or part or distributing it to the market.

[0048] Furthermore, during the development stage of equipment, when the equipment manufacturer procures a part manufactured by a parts manufacturer, the manufacturer can refer to the configuration information of the part (and the associated "evaluation information") to confirm the reliability of the part and then determine whether or not the part can be used.

[0049] Furthermore, in the development stage of another device, another device manufacturer procures the above device as a base device, adds (modifies) functions, and when re-shipping the device, generates and shares "configuration information" that updates the configuration details, etc. Then, the other device manufacturer ships or distributes the device after the functions have been added to the market.

[0050] Furthermore, during the system development and integration stages, the user company that procured the above equipment will make configuration changes to the equipment and incorporate it into their own facilities. At that time, the user company will reflect (update) the configuration changes equivalent to the setting changes in the "configuration information" of the equipment and share them. The user company will then begin operating the target equipment.

[0051] Furthermore, in the operation stage, when the user company incorporates new equipment into its own facilities as described above, the user company specifies the relationship between the equipment and the configuration information representing the "system" corresponding to the equipment, thereby associating the equipment configuration information with the system configuration information, updating and sharing the information.The user company then starts or continues operation of the target system.

[0052] Furthermore, during the operation phase, the user company acquires "status information" from the system and its constituent devices, which indicates various operational conditions during operation. The user company then continues to update and share this information, in addition to the configuration information of the system and its constituent devices, during operation.

[0053] Furthermore, in the operation stage of the above-mentioned system, the user company performs an evaluation (for example, vulnerability testing or risk evaluation) based on the "configuration information," "evaluation information," and "status information" contained in the configuration information of the system. The user company then adds or updates new "evaluation information" to the configuration information, and updates and shares the configuration information of the system.

[0054] FIG. 5 is a diagram showing an example of a configuration information table in a shared database according to the second embodiment. The system configuration table 210 manages configuration information related to an information system. The system configuration table 210 includes, in one record, a system ID 211, content information 212, device ID 2131, . . . 213n (n is a natural number equal to or greater than 1). The system ID 211 is identification information for the information system 400. The content information 212 is text information or the like indicating the content of the information system 400, such as the name, purpose, overview, specifications, etc. of the system. The device ID 2131, etc. are identification information for multiple devices that make up the information system 400.

[0055] The device configuration table 220 manages configuration information related to the devices that make up the information system 400. The device configuration table 220 includes device configuration records 221 to 22n. The device configuration record 221 is configuration information for a specific device and includes a device ID 2211, content information 2212, and model ID 2213. The device ID 2211 is identification information for the device, such as the product serial number. The content information 2212 is text information indicating the content of the device, such as the name, overview, and specifications of the device. The model ID 2213 is identification information for the model of the device. Similarly, the device configuration record 22n thereafter includes a device ID 22n1, content information 22n2, and model ID 22n3. Here, the device ID 2131 in the system configuration table 210 is the same as the device ID 2211 in the device configuration record 221, and the device ID 213n in the system configuration table 210 is the same as the device ID 22n1 in the device configuration record 221. In other words, the system configuration table 210 and the device configuration table 220 are associated one-to-many.

[0056] The model configuration table 230 manages configuration information related to models that can be used in devices. The model configuration table 230 includes model configuration records 231-23i (i is a natural number equal to or greater than 1). The model configuration record 231 is configuration information for a specific model, and includes a model ID 2311, content information 2312, and software IDs 23131-2313m (m is a natural number equal to or greater than 1). The model ID 2311 is identification information for the model, such as the model number of the device. The content information 2312 is text information indicating the content of the model, such as the model name, overview, and specifications. The software ID 23131 is identification information for software installed in the device corresponding to the model. Similarly, the model configuration record 23i includes a model ID 23i1, content information 23i2, and software IDs 23i31-23i3j (j is a natural number equal to or greater than 1). In this example, the model ID 2213 of the device configuration record 221 and the model ID 22n3 of the device configuration record 22n are the same as the model ID 2311 of the model configuration record 231. In other words, the device configuration record and the model configuration record are associated many-to-one. For example, this applies to the case where the devices, ie, servers 42 and 43, are the same model. It is sufficient that the device configuration record and the model configuration record are associated at least one-to-one. Furthermore, the device configuration table 220 and the model configuration table 230 may be a single table. For example, the device configuration content information may include model configuration information.

[0057] The software configuration table 240 manages configuration information related to software installed in a device. The software configuration table 240 includes software configuration records 241 to 24m. The software configuration table 240 also includes configuration information for software installed in models other than the model configuration record 231, but this information is not shown in the figure. The software configuration record 241 is configuration information for specific software and includes a software ID 2411 and content information 2412. The software ID 2411 is software identification information. The content information 2412 is text information indicating the content of the software, such as the software name, type, overview, specifications, etc. The software type may be, for example, a module, library, driver, firmware, etc., but is not limited to these.

[0058] Note that the system configuration table 210 does not necessarily need to store the device ID 2131, etc., and a separate table may be used that associates the system ID 211 with the device IDs 2131 to 213n. Alternatively, instead of storing the device ID 2131, etc., in the system configuration table 210, the system ID 211 may be stored in each of the device configuration records 221 to 22n. Alternatively, the system configuration information and the device configuration information may be associated with each other by other means.

[0059] Similarly, the device configuration records 221 etc. of the device configuration table 220 do not necessarily need to store the model ID 2213 etc., and a separate table may be used that associates the device ID 2211 etc. with the model ID 2311 etc. Alternatively, the device configuration information and the model configuration information may be associated by other means.

[0060] Similarly, the model configuration record 231 etc. of the model configuration table 230 does not necessarily have to store the software ID 23131 etc., and a separate table that associates the model ID 2311 etc. with the software ID 2411 etc. may be used. Alternatively, the model configuration information and the software configuration information may be associated by other means. For example, each piece of configuration information may be linked by a list structure of IDs.

[0061] FIG. 5 illustrates an example in which multiple pieces of configuration information, including a system configuration, a device configuration, a model configuration, and a software configuration, are linked in a hierarchical structure. However, the relationships between the multiple pieces of configuration information are not limited to this. For example, as described above, elements can include hardware and software components. Therefore, the configuration information may include configuration information for multiple hardware components that make up a certain device. For example, device configuration information or model configuration information may be associated with configuration information for multiple hardware components. Furthermore, the configuration information may include configuration information for multiple software components that make up a certain piece of software. For example, software configuration information may be associated with configuration information for multiple software components. Software components include the above-mentioned modules, libraries, drivers, firmware, etc. Furthermore, hardware and software components may be developed, manufactured, and evaluated separately by different manufacturers from the hardware and software products that combine them. Therefore, for example, status information and evaluation information may be associated with the configuration information for hardware and software components. Furthermore, hardware and software components are not necessarily used for a single type of device, model, or software. Furthermore, multiple hardware and software components may be combined to form other components. Therefore, the configuration information of a hardware component may be associated with multiple pieces of device configuration information, model configuration information, and hardware component configuration information. Similarly, the configuration information of a software component may be associated with multiple pieces of software configuration information and software component configuration information.

[0062] 6 is a diagram showing examples of a status information table and an evaluation information table in the shared database according to the second embodiment. The status information table 250 manages status information. In the status information table 250, a system ID, a device ID, a model ID, or a software ID is associated with status information. Here, the status information includes log information, alert information, and the amount of resource usage such as the CPU and memory.

[0063] The evaluation information table 260 manages evaluation information. The evaluation information table 260 associates a system ID, a device ID, a model ID, or a software ID with evaluation information. Here, the evaluation information includes inspection results, security risk information, etc.

[0064] For example, status information table 250 includes multiple records in which system ID 251 is associated with status information 271, system ID 252 is associated with status information 272, etc. Furthermore, evaluation information table 260 includes multiple records in which system ID 261 is associated with evaluation information 281, system ID 262 is associated with evaluation information 282, etc. Here, system IDs 251, 252, 261, and 262 are the same as system ID 211 in system configuration table 210 described above. In other words, system configuration table 210 and status information table 250 are associated one-to-many, and system configuration table 210 and evaluation information table 260 are associated one-to-many.

[0065] Furthermore, the status information table 250 includes multiple records in which a device ID 253 is associated with status information 273, a device ID 254 is associated with status information 274, and so on. Furthermore, the evaluation information table 260 includes multiple records in which a device ID 263 is associated with evaluation information 283, a device ID 264 is associated with evaluation information 284, and so on. Here, it does not matter whether the device IDs 253, 254, 263, and 264 are the same or not. In other words, the device configuration table 220 and the status information table 250 are associated one-to-many, and the device configuration table 220 and the evaluation information table 260 are associated one-to-many.

[0066] Furthermore, the status information table 250 includes a plurality of records in which a model ID 255 and status information 275, a model ID 256 and status information 276, etc. are associated. Furthermore, the evaluation information table 260 includes a plurality of records in which a model ID 265 and evaluation information 285, a model ID 266 and evaluation information 286, etc. are associated. Here, it does not matter whether the model IDs 255, 256, 265, and 266 are the same or not. In other words, the model configuration table 230 and the status information table 250 are associated one-to-many, and the model configuration table 230 and the evaluation information table 260 are associated one-to-many.

[0067] Furthermore, the state information table 250 includes multiple records in which software ID 257 and state information 277, software ID 258 and state information 278, etc. are associated. Furthermore, the evaluation information table 260 includes multiple records in which software ID 267 and evaluation information 287, software ID 268 and evaluation information 288, etc. Here, it does not matter whether the software IDs 257, 258, 267, and 268 are the same or not. In other words, the software configuration table 240 and the state information table 250 are associated one-to-many, and the software configuration table 240 and the evaluation information table 260 are associated one-to-many.

[0068] Note that some of the system configuration information, device information, model information, and software configuration information may not necessarily be associated with status information or evaluation information. In other words, some of the configuration information may not have status information or evaluation information registered.

[0069] 7 is a block diagram showing the configuration of an information management device 300 according to the second embodiment. The information management device 300 includes a storage unit 310, a memory 320, a communication unit 330, and a control unit 340. The storage unit 310 is an example of a storage device such as a hard disk or a flash memory. The storage unit 310 stores a program 311. The program 311 is a computer program that implements the acquisition process, registration process, display process, and the like according to the second embodiment.

[0070] The memory 320 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily storing information during operation of the control unit 340. The communication unit 330 is a communication interface with the network N.

[0071] The control unit 340 is a processor, i.e., a control device, that controls each component of the information management device 300. The control unit 340 loads the program 311 from the storage unit 310 into the memory 320 and executes the program 311. In this way, the control unit 340 realizes the functions of the acquisition unit 341, the registration unit 342, and the display unit 343. The combined configuration of the acquisition unit 341 and the registration unit 342 is an example of the first registration unit 11, the second registration unit 12, and the third registration unit described above. The display unit 343 is an example of the display unit 13 described above.

[0072] The acquisition unit 341 acquires configuration information corresponding to a predetermined element at multiple stages from the development stage of the component to the operation stage of the information system 400. The acquisition unit 341 also acquires status information and evaluation information indicating the status of the element at any stage. Alternatively, the acquisition unit 341 acquires evaluation information evaluated based on the configuration information and status information at any stage. The acquisition unit 341 also acquires relationships between multiple elements.

[0073] The registration unit 342 associates configuration information with status information and registers them in the shared database 200. The registration unit 342 also associates configuration information with evaluation information and registers them in the shared database 200. The registration unit 342 also associates configuration information based on the relationship between elements and registers it in the shared database 200. For example, when the registration unit 342 receives a first relationship between a first element and a second element, the registration unit 342 associates the first configuration information with the second configuration information based on the first relationship and registers it in the shared database 200.

[0074] In response to a display request, the display unit 343 generates display information that displays a plurality of pieces of configuration information corresponding to each of a plurality of elements in a connection form based on the relationships between the elements. In particular, the display unit 343 generates display information that displays the first configuration information and the second configuration information in a connection form based on the association in the shared database 200. In addition, in response to a display request, the display unit 343 generates display information that displays the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the shared database 200. Then, the display unit 343 transmits the generated display information to the requesting terminal and displays it on the screen of the terminal.

[0075] 8 and 9 are sequence diagrams showing the flow of the information management method according to the second embodiment. An equipment manufacturer P21 develops equipment and software (S201). For example, the equipment manufacturer P21 develops hardware 411 and software 412 of a NW equipment 41. At this time, the equipment manufacturer P21 generates configuration information A1 (equipment configuration information, model configuration information, software configuration information) of the NW equipment 41 using a terminal (not shown).

[0076] Then, the device manufacturer P21 evaluates the developed device (and software) (S202). Specifically, the device manufacturer P21 inspects whether the hardware 411 and software 412 of the NW device 41, which is the manufactured product, meets shipping standards, and generates evaluation information E1 including the inspection results using a terminal.

[0077] Then, the device manufacturer P21 uses a terminal to transmit the configuration information A1, the evaluation information E1, and the relationship to the information management device 300 via the network N (S203). Here, the relationship indicates, for example, that the device configuration information of the NW device 41 includes the model configuration information, and the model configuration information includes the software configuration information. Alternatively, the relationship may indicate that the device configuration information and the model configuration information correspond to the hardware 411 of the NW device 41, and the software configuration information corresponds to the software installed on the hardware 411. The relationship may also include the correspondence between the configuration information A1 and the evaluation information E1.

[0078] Thereafter, the information management device 300 receives the configuration information A1, the evaluation information E1, and the relationships from the terminal of the device manufacturer P21 via the network N. Then, the information management device 300 associates the configuration information A1 with the evaluation information E1 based on the received relationships and registers them in the shared database 200 (S204). Additionally, the information management device 300 associates the device configuration information and the model configuration information of the configuration information A1 based on the received relationships, and associates the model configuration information and the software configuration information and registers them in the shared database 200. Steps S201 to S204 are the development stage.

[0079] Separately from steps S201 to S204, the device manufacturer P22 develops devices and software (S205). For example, the device manufacturer P22 develops hardware 421 and software 422 of the server 42. At this time, the device manufacturer P22 generates configuration information A2 (device configuration information, model configuration information, software configuration information) of the server 42 using a terminal (not shown).

[0080] Then, the device manufacturer P22 evaluates the developed device (and software) (S206). Specifically, the device manufacturer P22 inspects the hardware 421 and software 422 of the server 42, which is the manufactured product, to determine whether they satisfy shipping standards, and generates evaluation information E2 including the inspection results using a terminal.

[0081] Then, the device manufacturer P22 uses a terminal to transmit the configuration information A2, the evaluation information E2, and the relationships to the information management device 300 via the network N (S207). Thereafter, the information management device 300 receives the configuration information A2, the evaluation information E2, and the relationships from the terminal of the device manufacturer P22 via the network N. Then, the information management device 300 associates the configuration information A2 with the evaluation information E2 based on the received relationships and registers them in the shared database 200 (S208). At the same time, the information management device 300 associates the device configuration information and the model configuration information of the configuration information A2 based on the received relationships, and associates the model configuration information and the software configuration information and registers them in the shared database 200. Steps S205 to S208 are the development stage.

[0082] Thereafter, the system integrator P5 uses the terminal 100-5 to acquire the configuration information A1, A2, etc. from the shared database 200 via the network N (S209). Then, the system integrator P5 performs system integration for the configuration information A1, A2, etc. (S210). For example, the system integrator P5 develops necessary application programs for the NW device 41 and the servers 42 and 43, and integrates the systems to build the information system 400. At this time, the system integrator P5 generates the configuration information A0 for the information system 400 using the terminal 100-5.

[0083] Then, the system integrator P5 evaluates the information system 400 (S211). Specifically, the system integrator P5 inspects the information system 400 to determine whether it satisfies the shipping standards, and generates evaluation information E0 including the inspection results using a terminal.

[0084] Then, the system integrator P5 uses the terminal 100-5 to transmit the configuration information A0, A1, and A2, the evaluation information E0, and the relationship to the information management device 300 via the network N (S212). Here, the relationship includes, for example, that the system configuration information of the information system 400 includes the device configuration information of the NW device 41 and the servers 42 and 43. The relationship may also include the correspondence between the configuration information A0 and the evaluation information E0.

[0085] Thereafter, the information management device 300 receives the configuration information A0, A1, and A2, the evaluation information E0, and the relationships from the terminal 100-5 via the network N. Then, the information management device 300 associates the configuration information A0 with A1 and A2 based on the received relationships and registers them in the shared database 200 (S213). At the same time, the information management device 300 associates the configuration information A0 with the evaluation information E2 based on the received relationships and registers them in the shared database 200 (S214). Steps S209 to S214 are the integration stage.

[0086] Thereafter, in the operation phase of the information system 400, the NW device 41 outputs the status information L1 and the device ID (A1) to the information management device 300 via the network N. That is, the information management device 300 acquires the status information L1 and the device ID (A1) of the NW device 41 (S215). Then, the information management device 300 identifies the configuration information A1 of the NW device 41 from the device ID, associates the configuration information A1 with the status information L1, and registers them in the shared database 200 (S216). As a result, the evaluation information E1 acquired in the development phase and the status information L1 acquired in the operation phase are associated with the configuration information A1 of the NW device 41.

[0087] Thereafter, the user operator P6 uses the terminal 100-6 to transmit a display request specifying the system ID (A0) to the information management device 300 via the network N (S217). The information management device 300 receives the display request from the terminal 100-6 via the network N. The information management device 300 then searches the shared database 200 by specifying the system ID included in the display request (S218). The information management device 300 then acquires information associated with the system ID from the shared database 200 via the network N (S219). Specifically, the information management device 300 acquires configuration information A0, and configuration information A1 and A2 (associated with configuration information A0). The information management device 300 also acquires status information L1 (associated with configuration information A1), evaluation information E0, evaluation information E1 (associated with configuration information A1), and evaluation information E2 (associated with configuration information A2).

[0088] The information management device 300 then associates the multiple pieces of configuration information and generates display information for a connection topology in which the configuration information, status information, and evaluation information are associated (S220). Specifically, the information management device 300 generates display information for a connection topology in which the configuration information A0, A1, and A2 are associated. The information management device 300 also generates display information for a connection topology in which the configuration information A0 is associated with evaluation information E0. The information management device 300 also generates display information for a connection topology in which the configuration information A1, status information L1, and evaluation information E1 are associated. The information management device 300 also generates display information for a connection topology in which the configuration information A2 is associated with evaluation information E2. The information management device 300 then transmits the generated display information to the terminal 100-6 via the network N (S221). The terminal 100-6 (user operator P6) then receives the display information from the information management device 300 via the network N and displays the received display information on a screen (S222).

[0089] FIG. 10 is a diagram showing an example of the connection topology of configuration information, status information, and evaluation information of the information system according to the second embodiment. Display information 5 displays configuration information of multiple elements constituting the information system 400 in a connection topology based on the relationships between the elements, and associates each piece of configuration information with status information and evaluation information. Display information 5 is an example of displaying the connection topology in a tree structure. Connection topology 51 is an example in which system configuration information 511 is connected to device configuration information 521, 522, etc. as child nodes, device configuration information 521 is connected to model configuration information 531 as a child node, and model configuration information 531 is connected to software configuration information 541, 542, etc. as child nodes. In other words, connection topology 51 is a display example in which multiple pieces of configuration information are connected based on the parent-child relationship between elements. Connection topology 52 is an example in which system configuration information 511 is connected to status information 5111, etc., and evaluation information 5112, etc., as child nodes. In other words, connection configuration 52 is a display example in which configuration information, status information, and evaluation information are associated and connected. Similarly, device configuration information 521 is a connection example in which status information 5211... and evaluation information 5212... are connected as child nodes, and model configuration information 531 is a connection example in which status information 5311... and evaluation information 5312... are connected as child nodes. Furthermore, connection configuration 53 is an example in which software configuration information 5411... and evaluation information 5412... are connected as child nodes. Similarly, software configuration information 542 is a connection example in which status information 5421... and evaluation information 5422... are connected as child nodes.

[0090] FIG. 11 is a diagram showing an example of display information of a plurality of pieces of configuration information, status information, and evaluation information according to the second embodiment. Display information 6 is a specific example of each piece of configuration information, status information, and evaluation information. System configuration information 611 is a root node, and NW device configuration information 621, server device configuration information 622 and 623, system integrated inspection result 6112-1, and system security risk information 6112-2 are connected as child nodes. The system configuration information 611 is configuration information corresponding to the entire information system 400. The NW device configuration information 621 and the server device configuration information 622 and 623 are, for example, configuration information corresponding to the NW device 41 and the servers 42 and 43, respectively. The system integrated inspection result 6112-1 and the system security risk information 6112-2 are specific examples of the evaluation information 5112 in FIG. 10 described above. The NW device configuration information 621 is an example in which NW model configuration information 631, a NW device log 6211, and a NW device inspection result 6212-1 are connected as child nodes. The NW model configuration information 631 is configuration information of the model of the NW device 41, the NW device log 6211 is log information (status information) acquired from the NW device 41, and the NW device inspection result 6212-1 is evaluation information for the NW device 41. Similarly, the server device configuration information 623 is an example in which server model configuration information 633, a server log 6231, and a server inspection result 6232-1 are connected as child nodes. The server model configuration information 633 is configuration information of the model of the server 43, the server log 6231 is log information (status information) acquired from the server 43, and the server inspection result 6232-1 is evaluation information for the server 43. Note that the model configuration information, server log, and server inspection result associated with the server device configuration information 622 are omitted from the illustration. For example, the server device configuration information 622 may be associated with the server model configuration information 633, which is the same as the server device configuration information 623, as a child node.

[0091] The NW model configuration information 631 is an example in which software configuration information 641, 642... and NW model security risk information 6312-2... are connected as child nodes. The software configuration information 641, 642... is configuration information for the software 412... installed in the NW device 41. The NW model security risk information 6312-2 is evaluation information for the model of the NW device 41.

[0092] The software configuration information 641 is an example in which SW logs 6411..., SW inspection results 6412-1..., and SW security risk information 6412-2 are connected as child nodes. The SW logs 6411... are log information (status information) acquired from the software 412. The SW security risk information 6412-2 is evaluation information for the software 412.

[0093] Similarly, the software configuration information 642 is an example in which SW logs 6421..., SW inspection results 6422-1..., and SW security risk information 6422-2 are connected as child nodes. The SW logs 6421... are log information (status information) acquired from other software in the NW device 41. The SW security risk information 6422-2 is evaluation information for other software.

[0094] Although the display information 6 shows an example in which the system configuration information 611 is not associated with the status information and the NW model configuration information 631 is not associated with the status information, these may be associated. In addition, the display information 6 does not necessarily have to associate the status information or evaluation information with each piece of configuration information as appropriate.

[0095] In this manner, in this embodiment, the relationships between the configuration information of the information system 400 and the relationships between the configuration information and the status information and evaluation information can be shared among the players in the supply chain. In particular, information registered individually by each player from the development stage to the operation stage can be visualized collectively in a connection form according to the relationships between elements and the associations between the configuration information and the status information and evaluation information. In particular, status information and inspection results for the same component can be registered by different players at different times, and a link structure (display information) associating the component, status information, and evaluation information can be displayed to a certain player. In other words, data visualizing the security operation status from the supply chain of the information system to the operation phase can be shared, realizing an environment in which trust can be constantly verified throughout the entire information system (ensuring security transparency). This also enhances shared knowledge.

[0096] As a result, user businesses can operate their information systems with an understanding of what kind of inspections have been performed within the supply chain and what the configuration is, and can respond quickly when log or alert information is received.In addition, by using data that visualizes the security operation status as a measure of reliability for network devices, etc., better operations (such as conducting necessary inspections and determining the urgency when an abnormality is detected) can be achieved, thereby reducing supply chain risks.

[0097] For example, user businesses can easily and comprehensively check not only the device configuration information of the network equipment they are checking, but also the inspection result history from component and equipment manufacturers. Therefore, if user businesses determine that the software and equipment manufacturers have not conducted sufficient inspections of the network equipment, they can conduct additional inspections as needed. Furthermore, user businesses can increase the urgency level when an alert is raised during monitoring for equipment whose inspection results are below the standard. Alternatively, user businesses can adjust the monitoring level by performing all necessary inspections on all equipment, and then lowering the urgency level when an alert is raised for network equipment whose inspection results are not of concern.

[0098] In other words, by ensuring transparency starting from security inspections of network equipment, etc., security can be maintained at all times. In particular, the security status of telecommunications equipment will be visualized through security inspection technologies (inspection of backdoors, spoofing, and alterations) as well as monitoring and analysis technologies throughout the entire supply chain and operation of telecommunications equipment. Furthermore, the technical specifications for visualized (digitized) data on security status and processing tools can be shared through the consortium.

[0099] <Embodiment 3> The third embodiment is an improved example of the software configuration information of the second embodiment described above. In managing the configuration information, hardware can be uniquely identified by a fingerprint, and software by a binary hash. Here, changes to hardware configurations by device manufacturers are relatively rare during the operational stage. On the other hand, software manufacturers may frequently upgrade software for security measures, feature additions, and other reasons. Therefore, every time the software is updated, the binary hash also changes. Therefore, if inspection results (evaluation information) are associated with software configuration information, the link to the inspection results becomes invalid due to a change in the binary hash. In other words, there was a problem in that after software was updated, it was not possible to trace the history of inspection results for the software before the update.

[0100] Therefore, when the first element is updated, the second registration unit according to the third embodiment acquires third evaluation information for the updated first element. Then, while maintaining the association between the first configuration information and the first evaluation information, the second registration unit further associates the third evaluation information with the first configuration information and registers the third evaluation information in the database.

[0101] Fig. 12 is a block diagram showing the configuration of an information management device 300a according to the third embodiment. The information management device 300a differs from the information management device shown in Fig. 7 above in that the program 311a is changed and a calculation unit 344 and a history management unit 345 are added to the control unit 340. The calculation unit 344 and the history management unit 345 are included in the second registration unit. The configuration of the information management system 1000 is otherwise the same as that of the second embodiment above, and therefore, overlapping content will not be illustrated or described as appropriate.

[0102] The program 311a is the program 311 described above to which hash value calculation processing, processing for associating data hash values ​​with inspection result hash values, and the like have been added.

[0103] The calculation unit 344 calculates a data hash value from the binary data of the software. The calculation unit 344 may also calculate an inspection result hash value from inspection result data.

[0104] The history management unit 345 maintains the association between the data hash value of the software before the update and the inspection result hash value. For example, when the software is updated, the history management unit 345 saves the data hash value before the update (first hash value) to the history area of ​​the first configuration information while maintaining the association with the inspection result hash value (second hash value).

[0105] The registration unit 342 associates the data hash value with the inspection result hash value and registers them in the shared database 200. Furthermore, when software is updated, the registration unit 342 associates the data hash value calculated from the updated software with the inspection result hash value calculated from the inspection result of the updated software and registers them in the shared database 200.

[0106] Hereinafter, specific examples 3-1 and 3-2 of the present embodiment 3 will be described. What is common to both examples is that the data hash value and the inspection result hash value are associated with each other. <Example 3-1> In Example 3-1, software configuration information includes a latest hash value area for storing the latest value of the data hash value, as well as a history area for the data hash value. Every time the software is updated, the data hash value is saved from the latest hash value area to the history area. At this time, a link between the data hash value saved in the history area and the inspection result hash value before the update is maintained. Therefore, even if the updated data hash value is stored (overwritten) in the latest hash value area, the history of the inspection results can be traced by the link between the original data hash value held in the history area and the inspection result hash value before the update.

[0107] FIG. 13 is a diagram showing the relationship between software configuration information and software inspection result information according to Example 3-1 of the third embodiment. The software configuration table 240a includes software configuration records 241a.... The software configuration record 241a includes a software ID 2411, version information 24121, function information 24122, target data storage destination 24123, latest hash value area 2413, and history area 24141...2414k (k is a natural number equal to or greater than 1). The version information 24121 is information indicating the version of the software. The function information 24122 is information explaining the function of the software. The function information 24122 may include software specifications. The target data storage destination 24123 is information indicating the storage destination of binary data (target data) of the software. The version information 24121, function information 24122, and target data storage destination 24123 are examples of the content information 2412 described above.

[0108] The latest hash value area 2413 is an area for storing the latest hash value calculated from binary data stored in the target data storage destination 24123. The history area 24141 and the like are areas for storing the history of data hash values ​​for each version. For example, the history area 24141 stores a set of version information 24151 and a data hash value 24152. Note that the history area 24141 and the like may store function information 24122 and the target data storage destination 24123 in addition to the version information.

[0109] The evaluation information table 260a includes SW inspection result information 291, 292, etc. The SW inspection result information 291 includes a software ID 2911, an inspection result storage destination 2912, and an inspection result hash value 2913. The software ID 2911 is identification information for the software that is the object of inspection. The inspection result storage destination 2912 is information indicating the storage destination for data of the inspection results (evaluation information) for the software that is the object of inspection. The inspection result hash value 2913 is a hash value calculated from the inspection results stored in the inspection result storage destination 2912.

[0110] The SW inspection result information 292 is inspection result information for the software after the update, that is, after the SW inspection result information 291. The SW inspection result information 292 includes a software ID 2921, an inspection result storage destination 2922, and an inspection result hash value 2923.

[0111] The inspection result storage destination 2922 is information indicating the storage destination of the data of the inspection result (evaluation information) for the updated software. The inspection result hash value 2923 is a hash value calculated from the inspection result stored in the inspection result storage destination 2922.

[0112] Here, the software ID 2411 of the software configuration record 241a, the software ID 2911 of the SW inspection result information 291, and the software ID 2921 of the SW inspection result information 292 are the same. In other words, the software configuration table 240a and the evaluation information table 260a are associated one-to-many.

[0113] 14 is a flowchart showing the flow of update processing according to Example 3-1 of Embodiment 3. It is assumed that specific software constituting the information system 400 is before an update, and that the data hash value 24131 of the software configuration record 241a is associated with the inspection result hash value 2913 of the SW inspection result information 291. Furthermore, at this point, it is assumed that there is no need for saved data in the history area 24141, and that the SW inspection result information 292 has not been registered.

[0114] Here, it is assumed that software vendor P3 has upgraded, i.e., updated, a specific piece of software. As a result, the binary data of the software is updated. Then, for example, terminal 100-3 of software vendor P3 transmits a software update notification to information management device 300a via network N.

[0115] In response, the information management device 300a receives a software update notification from the terminal 100-3 via the network N (S31). The information management device 300a then identifies the software configuration record 241a in the software configuration table 240a from the software ID included in the update notification. The information management device 300a then saves the most recent data hash value 24131 stored in the latest hash value area 2413 to the history area 24141 (S32). Specifically, the information management device 300a copies the set of version information 24121 and data hash value 24131 from the software configuration record 241a and stores it in the history area 24141 as a set of version information 24151 and data hash value 24152. At this time, since the data hash value 24152 in the history area 24141 is the same as the data hash value 24131 in the latest hash value area 2413, the association with the inspection result hash value 2913 in the SW inspection result information 291 is maintained. Alternatively, the information management device 300a may newly associate the data hash value 24152 with the inspection result hash value 2913 and register them in the shared database 200.

[0116] The information management device 300a then calculates a data hash value from the binary data of the updated software (S33). For example, if the pre-update software is overwritten with the updated software, the updated software will be stored in the target data storage destination 24123. Therefore, the information management device 300a reads out the binary data stored in the target data storage destination 24123 and calculates a hash value. The information management device 300a then stores the calculated data hash value in the latest hash value area 2413 (S34). That is, the data hash value 24131 in the latest hash value area 2413 is updated to the hash value of the updated software. Therefore, the association between the data hash value 24131 and the inspection result hash value 2913 becomes invalid. However, as described above, the association between the data hash value 24152 in the history area 24141 and the inspection result hash value 2913 before the update is maintained.

[0117] Furthermore, after updating the software, the software vendor P3 or the testing business operator P4 tests the updated software and calculates a test result hash value from the test results. Then, the software vendor P3 or the like uses the terminal 100-3 or the like to transmit software test result information, including the test result storage destination and the test result hash value, to the information management device 300a via the network N. Therefore, the information management device 300a acquires the software test result information (test result hash value) (S35). The information management device 300a then associates the SW test result information 292 with the software configuration record 241a and registers it in the shared database 200 (S36). Specifically, the information management device 300a matches the software ID 2921 of the SW test result information 292 with the software ID 2411 of the software configuration record 241a, and registers the received test result storage destination 2922 and test result hash value 2923 together in the shared database 200.

[0118] Next, the information management device 300a associates the data hash value 24131 in the latest hash value area 2413 with the additionally registered inspection result hash value 2923 and registers them in the shared database 200 (S37).

[0119] 9, user operator P6 then uses terminal 100-6 to send a display request to information management device 300a, receives display information related to information system 400, and displays it on the screen. At this point, it is assumed that software configuration information 641 in FIG. 11 has been updated. Display information 6 displays two SW inspection results connected to software configuration information 641. The two SW inspection results are SW inspection result information 291 for the software before the update and SW inspection result information 292 for the software after the update. The connection between software configuration information 641 and SW inspection result information 291 is maintained because the association between data hash value 24152 in history area 24141 of software configuration record 241a and inspection result hash value 2913 in SW inspection result information 291 is maintained. In addition, the connection between the software configuration information 641 and the SW inspection result information 292 is due to the additional registration of an association between the data hash value 24131 in the latest hash value area 2413 of the software configuration record 241a and the inspection result hash value 2923 of the SW inspection result information 292.

[0120] Therefore, the user company P6 can easily trace the history of inspection results for the software before the update as well as the latest inspection results for the updated software. This allows the user company P6 to appropriately determine the priority of the response when an alert for the software occurs. For example, in the case of a minor update, the priority can be lowered by placing more importance on the software inspection result information 291 before the update. Alternatively, in the case of a minor update, the inspection results before the update can be reused.

[0121] <Example 3-2> In Example 3-2, version information and data hash values ​​are elements that are connected and displayed separately as configuration information, separate from the software configuration information. Therefore, data hash values ​​are not stored in the software configuration table, and a separate hash history table is provided to hold the data hash values ​​for each version.

[0122] FIG. 15 is a diagram showing the relationship between software configuration information, hash value history, and software inspection result information according to Example 3-2 of the third embodiment. The software configuration record 241b includes a software ID 2411, version information 24121, function information 24122, and target data storage destination 24123. The hash history table 240c is a table for storing data hash values ​​of software for each version. The hash history table 240c includes history records 242, 243, and so on. The history record 242 is a history of hash values ​​of software before an update. The history record 242 includes a software ID 2421, version information 2422, and a data hash value 2423. The data hash value 2423 is a hash value calculated from the software before the update. The history record 243 is a history of hash values ​​of software after the update. The history record 243 includes a software ID 2431, version information 2432, and a data hash value 2433. The data hash value 2433 is a hash value calculated from the updated software. Here, the set of software ID 2411 and version information 24121 in the software configuration record 241b is the same as the set of software ID 2421 and version information 2422 in the history record 242, and the set of software ID 2431 and version information 2432 in the history record 243. In other words, the software configuration table 240b and the hash history table 240c are associated one-to-many.

[0123] The evaluation information table 260b includes SW inspection result information 291b, 292b, etc. The SW inspection result information 291b is inspection result information of software before an update, and includes a software ID 2911, an inspection result storage destination 2912, an inspection result hash value 2913, and in addition, version information 2914. The inspection result hash value 2913 is associated with the data hash value 2423 before the update.

[0124] Furthermore, SW inspection result information 292b is inspection result information of updated software, and includes version information 2924 in addition to a software ID 2921, an inspection result storage destination 2922, and an inspection result hash value 2923. The inspection result hash value 2923 is associated with the updated data hash value 2433.

[0125] Here, the set of software ID 2411 and version information 24121 in software configuration record 241b is the same as the set of software ID 2911 and version information 2914 in SW inspection result information 291b and the set of software ID 2921 and version information 2924 in SW inspection result information 292b. In other words, the software configuration table 240b and the evaluation information table 260b are associated one-to-many.

[0126] 16 is a flowchart showing the flow of update processing according to Example 3-2 of Embodiment 3. It is assumed that specific software constituting the information system 400 is in the pre-update state. Furthermore, it is assumed that a history record 242 has been registered in the hash history table 240c but a history record 243 has not been registered, and that SW inspection result information 291b has been registered in the evaluation information table 260b but SW inspection result information 292b has not been registered. Furthermore, it is assumed that the data hash value 2423 of the history record 242 and the inspection result hash value 2913 of the SW inspection result information 291b are associated with each other.

[0127] 14, the information management device 300a receives a software update notification from the terminal 100-3 via the network N (S31). Then, the information management device 300a calculates a data hash value from the binary data of the updated software (S33).

[0128] Next, the information management device 300a stores the calculated data hash value in the hash history table 240c (S34a). Specifically, the information management device 300a generates a history record 243 that includes the same set of software ID 2431 and version information 2432 as in the software configuration record 241b, and the data hash value 2433 calculated in step S33. The information management device 300a then registers the history record 243 in the hash history table 240c.

[0129] 14, the information management device 300a then acquires software inspection result information (inspection result hash value) (S35). Then, the information management device 300a associates the SW inspection result information 292b with the software configuration record 241b and additionally registers it in the shared database 200 (S36a). Specifically, the information management device 300a generates SW inspection result information 292b that includes the same set of software ID 2921 and version information 2924 as in the software configuration record 241b, as well as the acquired inspection result storage destination 2922 and inspection result hash value 2923. Then, the information management device 300a registers the SW inspection result information 292b in the evaluation information table 260b.

[0130] Next, the information management device 300a associates the data hash value 2433 of the history record 243 with the additionally registered inspection result hash value 2923 and registers them in the shared database 200 (S37a).

[0131] Thereafter, as in step S217 of FIG. 9 described above, the user operator P6 uses the terminal 100-6 to transmit a display request to the information management device 300a, receives display information related to the information system 400, and displays it on the screen.

[0132] FIG. 17 is a diagram showing an example of display information of a plurality of pieces of configuration information, status information, and evaluation information according to Example 3-2 of the third embodiment. Display information 6b shows nodes subsequent to software configuration information 640 connected to the network model configuration information 631 shown in FIG. 11 described above. The software configuration information 640 is an example in which version information 651, 652, and SW security risk information 653 are connected as child nodes. The version information 651 is an example in which a data hash value 6511, a SW log 6512, and a SW inspection result 6513 are connected as child nodes. Here, the version information 651 indicates the version of the software before the update. The data hash value 6511 indicates a hash value calculated from the software before the update. The SW log 6512 indicates log information acquired from the software before the update. The SW inspection result 6513 indicates the inspection result for the software before the update. The SW inspection result 6513 is an example in which an inspection result hash value 65131 is connected as a child node. Here, the data hash value 6511 and the inspection result hash value 65131 are connected based on the association.

[0133] Version information 652 is an example in which a data hash value 6521, a software log 6522, and a software inspection result 6523 are connected as child nodes. Here, version information 652 indicates the updated version of the software in question. Data hash value 6521 indicates a hash value calculated from the updated software. SW log 6522 indicates log information acquired from the updated software. SW inspection result 6523 indicates the inspection result of the updated software. SW inspection result 6523 is an example in which inspection result hash value 65231 is connected as a child node. Here, data hash value 6521 and inspection result hash value 65231 are connected based on an association.

[0134] The SW security risk information 653 indicates the security risk value in the software configuration information 640. The SW security risk information 653 may also store a history for each version.

[0135] In this way, in the display information 6b, for software corresponding to the software configuration information 640, the data hash value, log, inspection result, and inspection result hash value are associated and connected for each version. In particular, the data hash value and the inspection result hash value are linked within the same version. Therefore, even if a version is upgraded, the inspection results of previous versions can be easily traced. Therefore, the same effects as those of the above-mentioned Example 3-1 can be achieved.

[0136] In the display information 6b, the inspection result hash value may be included as configuration information within the inspection result.

[0137] <Embodiment 4> The fourth embodiment is an improved example of the second or third embodiment described above. The evaluation of each element constituting the information system 400 may be performed by the manufacturer of each element or a system integrator P5, but may also be performed by an external inspection company P4. In addition to the inspection stage described above, the inspection company P4 may also perform inspection (evaluation) using an evaluation server during the operation stage at the request of a user company P6 or the like. The evaluation server then associates the inspection results (evaluation information) with the configuration information and registers them in the shared database 200 via the information management device 300.

[0138] That is, the second registration unit transmits an evaluation request including the first configuration information and the first status information to the evaluation server and obtains second evaluation information for the first element from the evaluation server. Then, while maintaining the association between the first configuration information and the first evaluation information, the second registration unit further associates the second evaluation information with the first configuration information and registers it in the shared database 200. That is, while retaining the first evaluation information performed by the manufacturer or the like for the first element corresponding to the first configuration information, the second evaluation information performed by a third-party software vendor P3 for the first element is additionally registered. This allows the user business P6 to verify the validity of the evaluation by the manufacturer or the like and trace the evaluation history. Furthermore, by checking the third-party evaluation, the manufacturer or the like can use it as a reference when upgrading their own products. The information management device 300 may additionally register evaluation information but not delete or change existing evaluation information. This is to ensure the reliability of the evaluation information and the shared database 200.

[0139] Furthermore, the information management device 300 may be provided with a notification unit that notifies users to whom information is to be disclosed when it is registered in the shared database 200. This makes it easier for users to recognize newly registered information, from the parts manufacturer P1 to the user business operator P6, who are users to whom information is to be disclosed, and further promotes information sharing. It may also be possible to share registered information in real time.

[0140] <Other embodiments> Although the above-described embodiment has been described as a hardware configuration, the present disclosure is not limited to this. Any processing in the present disclosure can also be realized by causing a CPU to execute a computer program.

[0141] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0142] The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit and scope of the present disclosure. In addition, the present disclosure may be implemented by appropriately combining the respective embodiments.

[0143] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Appendix A1) a first registration means for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system, at a first stage from a development stage of the first element to an operation stage of the information system, and for associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration means for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and for registering the first configuration information and the first status information in the database in association with each other; a display means for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; An information management device comprising: (Appendix A2) a third registration means for, when a first relationship between the first element and a second element of the plurality of elements is received, associating the first configuration information with second configuration information corresponding to the second element based on the first relationship and registering the association in the database; The display means displays the first configuration information and the second configuration information in a connection form based on the association in the database. 10. The information management device according to claim 1. (Appendix A3) the first stage is subsequent to the second stage, The second registration means acquires the first evaluation information evaluated based on the first configuration information and the first status information associated with the first configuration information in the second stage. 10. The information management device according to claim 1, wherein the information management device is a device for managing information on a network. (Appendix A4) The second registration means transmitting an evaluation request including the first configuration information and the first status information to an evaluation server; acquiring second evaluation information for the first element from the evaluation server; The second evaluation information is further associated with the first configuration information and registered in the database. 10. The information management device according to claim A3. (Appendix A5) The database further includes a notification unit for notifying a user to whom information is to be disclosed when the information is registered in the database. An information management device according to any one of appendices A1 to A4. (Appendix A6) The second registration means When the first element is updated, third evaluation information for the updated first element is acquired; The third evaluation information is further associated with the first configuration information and registered in the database. An information management device according to any one of appendices A1 to A5. (Appendix A7) the first element is software; the first configuration information includes a latest hash value area in which a first hash value calculated by the software is stored, and a hash value history area; the first evaluation information includes a first inspection result of the software and a second hash value calculated from the first inspection result; The second registration means registering the first hash value and the second hash value in the database in association with each other; When the software is updated, the first hash value is saved to a history area of ​​the first configuration information while maintaining the association with the second hash value; calculating a third hash value from the updated software; storing the third hash value in the latest hash value area; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; The third evaluation information is further associated with the first configuration information, and the third hash value and the fourth hash value are associated with each other and registered in the database. 10. The information management device according to claim A6. (Appendix A8) the first element is software; a third piece of configuration information among the plurality of pieces of configuration information is a first hash value calculated from the software; the first evaluation information is a first inspection result of the software, and is associated with fourth configuration information that is a second hash value calculated from the first inspection result; The second registration means registering the third configuration information and the fourth configuration information in the database in association with each other; When the software is updated, a third hash value is calculated from the updated software and set as fifth configuration information; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; While maintaining the association between the third configuration information and the fourth configuration information, the fifth configuration information and the third evaluation information are further associated with the first configuration information and registered in the database. 10. The information management device according to claim A6. (Appendix A9) The plurality of elements includes hardware and software installed on the hardware. An information management device according to any one of appendices A1 to A8. (Appendix B1) a database in which first configuration information corresponding to at least a first element among a plurality of elements constituting an information system is registered; an information management device connected to the database; Equipped with The information management device At a first stage from a development stage of the first element to an operation stage of the information system, first evaluation information for the first element is acquired, and the first configuration information and the first evaluation information are associated with each other and registered in the database; acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and registering the first configuration information and the first status information in the database in association with each other; In response to a display request, a plurality of pieces of configuration information corresponding to the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database. Information management system. (Appendix B2) The information management device when a first relationship between the first element and a second element among the plurality of elements is received, associate the first configuration information with second configuration information corresponding to the second element based on the first relationship and register the association in the database; The first configuration information and the second configuration information are displayed in a connection form based on the association in the database. The information management system described in Appendix B1. (Appendix C1) The computer acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at a first stage from a development stage of the first element to an operation stage of the information system; registering first configuration information corresponding to the first element and the first evaluation information in a database in association with each other; acquiring first status information indicating a status of the first element in a second stage other than the first stage from the development stage to the operation stage; registering the first configuration information and the first status information in the database in association with each other; In response to a display request, a plurality of pieces of configuration information corresponding to the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database. Information management method. (Appendix D1) a first registration process for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at any one of a development stage and an operation stage of the information system, and associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration process for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and associating the first configuration information with the first status information and registering them in the database; a display process for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; A non-transitory computer-readable medium storing a program that causes a computer to execute the program.

[0144] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. [Explanation of symbols]

[0145] 1 Information management device 11 First Registration Section 12 Second Registration Section 13 Display section 1000 Information Management System N Network 100, 100-1 to 100-6 terminals P1 Parts manufacturer P2 Equipment Manufacturer P21 Equipment Manufacturer P22 Equipment Manufacturer P3 Software Vendor P4 Inspection company P5 System Integrator P6 User business 200 shared databases 300 Information management device 400 Information Systems 41 NW equipment 411 Hardware 412 Software 42 servers 421 Hardware 422 Software 43 Server 431 Hardware 432 Software 21 Configuration Information 22 Status Information 23 Evaluation Information 210 System Configuration Table 211 System ID 212 Content Information 2131 Device ID 213n Device ID 220 Equipment Configuration Table 221 Equipment Configuration Record 2211 Device ID 2212 Content Information 2213 Model ID 22n Equipment Configuration Record 22n1 Device ID 22n2 Content Information 22n3 Model ID 230 Model Configuration Table 231 Model Configuration Record 2311 Model ID 2312 Content Information 23131 Software ID 2313m Software ID 23i Model Configuration Record 23i1 Model ID 23i2 Content information 23i31 Software ID 23i3j Software ID 240 Software Configuration Table 241 Software Configuration Records 2411 Software ID 2412 Content Information 24m Software Configuration Record 24m1 Software ID 24m2 Content information 250 Status Information Table 251 System ID 252 System ID 253 Equipment ID 254 Device ID 255 Model ID 256 Model ID 257 Software ID 258 Software ID 271~278 Status information 260 Evaluation Information Table 261 System ID 262 System ID 2653 Equipment ID 264 Device ID 265 Model ID 266 Model ID 267 Software ID 268 Software ID 281~288 Rating Information 300 Information management device 300a Information management device 310 Storage section 311 Program 311a Program 320 memory 330 Communications Department 340 Control Unit 341 Acquisition Department 342 Registration Department 343 Display section 344 Calculation Unit 345 History Management Department 5 Display information 51 Connection type 52 Connection type 53 Connection type 511 System configuration information 5111 Status Information 5112 Evaluation Information 521 Device configuration information 5211 Status Information 5212 Evaluation Information 522 Device configuration information 531 Model Configuration Information 5311 Status Information 5312 Evaluation Information 541 Software Configuration Information 5411 Status Information 5412 Evaluation Information 542 Software configuration information 5421 Status Information 5422 Evaluation Information 6 Display information 611 System Configuration Information 6112-1 System Integration Inspection Results 6112-2 System Security Risk Information 621 NW device configuration information 6211 Network device log 6212-1 Network equipment inspection results 622 Server device configuration information 623 Server device configuration information 6231 Server Log 6232-1 Server inspection results 631 Network model configuration information 633 Server model configuration information 6312-2 Network model security risk information 641 Software Configuration Information 6411 SW Log 6412-1 SW inspection results 6412-2 Software Security Risk Information 642 Software Configuration Information 6421 SW Log 6422-1 SW inspection results 6422-2 Software Security Risk Information 240a Software Configuration Table 241a Software Configuration Record 24121 Version Information 24122 Feature Information 24123 Target data storage destination 2413 Latest Hash Value Area 24131 data hash value 24141 History Area 24151 Version Information 24152 data hash value 2414k history area 260a Evaluation Information Table 291 SW inspection result information 2911 Software ID 2912 Test result storage destination 2913 Inspection result hash value 292 SW inspection result information 2921 Software ID 2922 Test result storage destination 2923 Inspection result hash value 240b Software Configuration Table 241b Software Configuration Record 240c Hash History Table 242 History Records 2421 Software ID 2422 Version Information 2423 Data Hash Value 243 History Records 2431 Software ID 2432 Version Information 2433 Data Hash Value 260b Evaluation information table 291b SW test result information 2914 Version Information 292b SW test result information 2924 Version Information 6b Display information 640 Software Configuration Information 651 Version Information 6511 data hash value 6512 SW Log 6513 SW inspection results 65131 Inspection result hash value 652 Version Information 6521 data hash value 6522 SW Log 6523 SW inspection results 65231 Inspection result hash value 653 SW Security Risk Information

Claims

1. a first registration means for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system, at a first stage from a development stage of the first element to an operation stage of the information system, and for associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration means for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and for registering the first configuration information and the first status information in the database in association with each other; a display means for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; Equipped with The second registration means When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; the first configuration information includes a latest hash value area in which a first hash value calculated by the software is stored, and a hash value history area; the first evaluation information includes a first inspection result of the software and a second hash value calculated from the first inspection result; The second registration means registering the first hash value and the second hash value in the database in association with each other; When the software is updated, the first hash value is saved to a history area of ​​the first configuration information while maintaining the association with the second hash value; calculating a third hash value from the updated software; storing the third hash value in the latest hash value area; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; The third evaluation information is further associated with the first configuration information, and the third hash value and the fourth hash value are associated with each other and registered in the database. Information management device.

2. A first registration means for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at any one of the first stages from the development stage of the first element to the operation stage of the information system, and associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration means for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and for registering the first configuration information and the first status information in the database in association with each other; a display means for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; Equipped with The second registration means When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; a third piece of configuration information among the plurality of pieces of configuration information is a first hash value calculated from the software; the first evaluation information is a first inspection result of the software, and is associated with fourth configuration information that is a second hash value calculated from the first inspection result; The second registration means registering the third configuration information and the fourth configuration information in the database in association with each other; When the software is updated, a third hash value is calculated from the updated software and set as fifth configuration information; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; While maintaining the association between the third configuration information and the fourth configuration information, the fifth configuration information and the third evaluation information are further associated with the first configuration information and registered in the database. Information management device.

3. a third registration means for, when a first relationship between the first element and a second element among the plurality of elements is received, associating the first configuration information with second configuration information corresponding to the second element based on the first relationship and registering the association information in the database; The display means displays the first configuration information and the second configuration information in a connection form based on the association in the database.

3. The information management device according to claim 1 or 2.

4. the first stage is subsequent to the second stage; The first registration means acquires the first evaluation information evaluated based on the first configuration information and the first status information associated with the first configuration information in the second stage. The information management device according to any one of claims 1 to 3.

5. The second registration means sending an evaluation request including the first configuration information and the first status information to an evaluation server; acquiring second evaluation information for the first element from the evaluation server; The second evaluation information is further associated with the first configuration information and registered in the database. The information management device according to claim 4.

6. The database further includes a notification unit for notifying a user to whom information is to be disclosed when the information is registered in the database. The information management device according to any one of claims 1 to 5.

7. The plurality of elements includes hardware and software installed on the hardware. The information management device according to any one of claims 1 to 6.

8. a database in which first configuration information corresponding to at least a first element among a plurality of elements constituting an information system is registered; an information management device connected to the database; Equipped with The information management device At a first stage from a development stage of the first element to an operation stage of the information system, first evaluation information for the first element is acquired, and the first configuration information and the first evaluation information are associated with each other and registered in the database, thereby performing a first registration; In a second stage other than the first stage among the development stage and the operation stage, first status information indicating a status of the first element is acquired, and a second registration is performed in which the first configuration information and the first status information are associated with each other and registered in the database; In response to a display request, display a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on a relationship between the elements, and display the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; In the second registration, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; the first configuration information includes a latest hash value area in which a first hash value calculated by the software is stored, and a hash value history area; the first evaluation information includes a first inspection result of the software and a second hash value calculated from the first inspection result; In the second registration, registering the first hash value and the second hash value in the database in association with each other; When the software is updated, the first hash value is saved to a history area of ​​the first configuration information while maintaining the association with the second hash value; calculating a third hash value from the updated software; storing the third hash value in the latest hash value area; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; The third evaluation information is further associated with the first configuration information, and the third hash value and the fourth hash value are associated with each other and registered in the database. Information management system.

9. A database in which first configuration information corresponding to at least a first element among a plurality of elements constituting an information system is registered; an information management device connected to the database; Equipped with The information management device At a first stage from a development stage of the first element to an operation stage of the information system, first evaluation information for the first element is acquired, and the first configuration information and the first evaluation information are associated with each other and registered in the database, thereby performing a first registration; In a second stage other than the first stage among the development stage and the operation stage, first status information indicating a status of the first element is acquired, and a second registration is performed in which the first configuration information and the first status information are associated with each other and registered in the database; In response to a display request, display a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on a relationship between the elements, and display the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; In the second registration, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; a third piece of configuration information among the plurality of pieces of configuration information is a first hash value calculated from the software; the first evaluation information is a first inspection result of the software, and is associated with fourth configuration information that is a second hash value calculated from the first inspection result; In the second registration, registering the third configuration information and the fourth configuration information in the database in association with each other; When the software is updated, a third hash value is calculated from the updated software and set as fifth configuration information; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; While maintaining the association between the third configuration information and the fourth configuration information, the fifth configuration information and the third evaluation information are further associated with the first configuration information and registered in the database. Information management system.

10. The information management device when a first relationship between the first element and a second element among the plurality of elements is accepted, a third registration is performed in which the first configuration information and second configuration information corresponding to the second element are associated with each other based on the first relationship and registered in the database; The first configuration information and the second configuration information are displayed in a connection form based on the association in the database.

10. The information management system according to claim 8 or 9.

11. The computer At a first stage from a development stage of at least a first element of a plurality of elements constituting an information system to an operation stage of the information system, first evaluation information for the first element is acquired, and first configuration information corresponding to the first element and the first evaluation information are associated with each other and registered in a database; In a second stage other than the first stage among the development stage and the operation stage, first status information indicating a status of the first element is acquired, and a second registration is performed in which the first configuration information and the first status information are associated with each other and registered in the database; In response to a display request, a plurality of pieces of configuration information corresponding to the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database; In the second registration, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; the first configuration information includes a latest hash value area in which a first hash value calculated by the software is stored, and a hash value history area; the first evaluation information includes a first inspection result of the software and a second hash value calculated from the first inspection result; In the second registration, registering the first hash value and the second hash value in the database in association with each other; When the software is updated, the first hash value is saved to a history area of ​​the first configuration information while maintaining the association with the second hash value; calculating a third hash value from the updated software; storing the third hash value in the latest hash value area; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; The third evaluation information is further associated with the first configuration information, and the third hash value and the fourth hash value are associated with each other and registered in the database. Information management method.

12. A computer comprising: At a first stage from a development stage of at least a first element of a plurality of elements constituting an information system to an operation stage of the information system, first evaluation information for the first element is acquired, and first configuration information corresponding to the first element and the first evaluation information are associated with each other and registered in a database; In a second stage other than the first stage among the development stage and the operation stage, first status information indicating a status of the first element is acquired, and a second registration is performed in which the first configuration information and the first status information are associated with each other and registered in the database; In response to a display request, a plurality of pieces of configuration information corresponding to the plurality of elements are displayed in a connection form based on the relationship between the elements, and the first configuration information, the first status information, and the first evaluation information are displayed in a connection form based on the association in the database; In the second registration, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; a third piece of configuration information among the plurality of pieces of configuration information is a first hash value calculated from the software; the first evaluation information is a first inspection result of the software, and is associated with fourth configuration information that is a second hash value calculated from the first inspection result; In the second registration, registering the third configuration information and the fourth configuration information in the database in association with each other; When the software is updated, a third hash value is calculated from the updated software and set as fifth configuration information; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; While maintaining the association between the third configuration information and the fourth configuration information, the fifth configuration information and the third evaluation information are further associated with the first configuration information and registered in the database. Information management method.

13. a first registration process for acquiring first evaluation information for at least a first element among a plurality of elements constituting an information system at a first stage from a development stage to an operation stage of the information system, and associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration process for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and associating the first configuration information with the first status information and registering them in the database; a display process that displays, in response to a display request, a plurality of pieces of configuration information corresponding to each of the plurality of elements in a connection form based on a relationship between the elements, and displays the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database, In the second registration process, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; the first configuration information includes a latest hash value area in which a first hash value calculated by the software is stored, and a hash value history area; the first evaluation information includes a first inspection result of the software and a second hash value calculated from the first inspection result; In the second registration process, registering the first hash value and the second hash value in the database in association with each other; When the software is updated, the first hash value is saved to a history area of ​​the first configuration information while maintaining the association with the second hash value; calculating a third hash value from the updated software; storing the third hash value in the latest hash value area; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; The third evaluation information is further associated with the first configuration information, and the third hash value and the fourth hash value are associated with each other and registered in the database. program.

14. A first registration process for obtaining first evaluation information for at least a first element among a plurality of elements constituting an information system at any one of the first stages from the development stage of the information system to the operation stage of the information system, and associating first configuration information corresponding to the first element with the first evaluation information and registering the first evaluation information in a database; a second registration process for acquiring first status information indicating a status of the first element in a second stage other than the first stage among the development stage and the operation stage, and associating the first configuration information with the first status information and registering them in the database; a display process for displaying, in response to a display request, a plurality of pieces of configuration information corresponding to the plurality of elements in a connection form based on the relationship between the elements, and displaying the first configuration information, the first status information, and the first evaluation information in a connection form based on the association in the database; on the computer, In the second registration process, When the first element is updated, third evaluation information for the updated first element is acquired; registering the third evaluation information in the database in further association with the first configuration information; the first element is software; a third piece of configuration information among the plurality of pieces of configuration information is a first hash value calculated from the software; the first evaluation information is a first inspection result of the software, and is associated with fourth configuration information that is a second hash value calculated from the first inspection result; In the second registration process, registering the third configuration information and the fourth configuration information in the database in association with each other; When the software is updated, a third hash value is calculated from the updated software and set as fifth configuration information; acquiring the third evaluation information including a second inspection result of the updated software and a fourth hash value calculated from the second inspection result; While maintaining the association between the third configuration information and the fourth configuration information, the fifth configuration information and the third evaluation information are further associated with the first configuration information and registered in the database. program.

Images