Information output device, information output method, and recording medium

The information output device collects and evaluates device information from manufacturing to operation, addressing the challenge of detecting device risks by providing a systematic risk assessment and alerting mechanism, thereby improving device reliability and security.

WO2024247106A1PCT designated stage expired Publication Date: 2024-12-05NEC CORP
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/020092
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-30
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing systems fail to effectively detect risks in managed devices by solely relying on recorded information, lacking a comprehensive method to assess and alert managers to potential security and reliability issues.

Method used

An information output device and method that collects various types of device information from the manufacturing stage to operation, along with external data, to evaluate and output risk information, enabling administrators to identify and address potential security risks.

Benefits of technology

Facilitates early detection and awareness of device risks, enhancing the reliability and security of managed equipment by providing a systematic approach to risk assessment and alerting administrators to potential threats.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023020092_05122024_PF_FP_ABST
    Figure JP2023020092_05122024_PF_FP_ABST
Patent Text Reader

Abstract

An information output device according to the present disclosure comprises: an information collection means that collects at least apparatus information of different types from external information relating to managed apparatuses and to tracing of the apparatuses from manufacturing time to operation time; and an output means that, on the basis of the apparatus information, causes a combination of risk information used in risk evaluation for the apparatuses to be outputted.
Need to check novelty before this filing date? Find Prior Art

Description

Information output device, information output method, and recording medium

[0001] The present disclosure relates to an information output device, an information output method, and a recording medium.

[0002] To guarantee the quality of a product, various information about the manufacturing process of the product is used, such as records of each inspection performed during the manufacturing process of the product and records of audits conducted to verify the manufacturing process.

[0003] For example, Patent Document 1 discloses a data management system that records and manages operation logs, behavior logs, and environment logs in the processes of manufacturing, transporting, storing, and the like of an item as processing records.

[0004] Japanese Patent Application Laid-Open No. 2021-140288

[0005] However, the invention described in the above-mentioned Patent Document 1 is simply intended to record information as soon as it is generated. However, there is a need to find risks to managed devices and the like based on the recorded information. However, it is difficult to find risks to devices by simply displaying the recorded information.

[0006] An example of an object of the present disclosure is to provide an information output device that can make an administrator aware of risks to equipment.

[0007] An information output device in one aspect of the present disclosure includes an information collection means for collecting at least different types of equipment information from evidence of the equipment being managed from the time of manufacture to the time of operation and external information related to the equipment, and an output means for outputting a combination of risk information to be used for risk assessment of the equipment based on the equipment information.

[0008] An information output method in one aspect of the present disclosure involves a computer collecting at least different types of equipment information from evidence of the equipment it manages from the time it is manufactured to the time it is put into operation and from external information related to the equipment, and outputting multiple pieces of risk information to be used for risk assessment of the equipment based on the equipment information.

[0009] In one aspect of the present disclosure, a recording medium stores a program that causes a computer to collect at least different types of equipment information from evidence from the time of manufacture to the time of operation of the equipment being managed and from external information related to the equipment, and output multiple types of risk information to be used for risk assessment of the equipment based on the equipment information.

[0010] An example of an effect of the present disclosure is that it is possible to provide an information output device that can make an administrator aware of risks to equipment.

[0011] FIG. 1 is a block diagram showing the configuration of an information output device according to the present disclosure. FIG. 2 is a diagram showing the configuration of a customer's internal network including an information output device according to the present disclosure. FIG. 3 is a diagram showing a hardware configuration in which the information output device according to the present disclosure is realized by a computer device and its peripheral devices. FIG. 4 is a flowchart showing the operation of information output according to the present disclosure. FIG. 5 is a block diagram showing the configuration of an information output device according to the present disclosure. FIG. 6 is a diagram for explaining the collection of device information and the output of risk information in a specific example 1. FIG. 7 is a diagram for explaining the collection of device information and the output of risk information in a specific example 2. FIG. 8 is a diagram for explaining the collection of device information and the output of risk information in a specific example 3. FIG. 9 is a diagram for explaining the collection of device information and the output of risk information in a specific example 4. FIG. 10 is a diagram for explaining the collection of device information and the output of risk information in a specific example 5. FIG. 11 is a diagram for explaining the collection of device information and the output of risk information in a specific example 6. FIG. 12 is a diagram for explaining the collection of device information and the output of risk information in a specific example 7. FIG. 13 is a block diagram showing the configuration of an information output device according to the present disclosure. FIG. 14 is a diagram for explaining the collection of device information and the output of risk information in a specific example 8. FIG. 15 is a flowchart showing the operation of outputting information in the present disclosure.

[0012] Next, an embodiment will be described in detail with reference to the drawings.

[0013] First Embodiment Fig. 1 is a block diagram showing the configuration of an information output device 100 according to the present disclosure. As shown in Fig. 1, the information output device 100 includes an information collection unit 101 and an output unit 102. The information output device 100 displays information about devices purchased by customers from suppliers, and makes the device administrator or the like aware of the need to address security reliability risks of the devices. In this embodiment, the devices are, for example, network devices for relaying and transferring data on a network system.

[0014] 2 is a diagram showing the configuration of a customer's internal network including the information output device 100 according to the present disclosure. As shown in FIG. 2, the information output device 100 is connected to devices purchased by the customer from suppliers within the internal network. The information output device 100 is also connected to a server device owned by the supplier via an external network.

[0015] 3 is a diagram showing an example of a hardware configuration in which the information output device 100 of the present disclosure is realized by a computer device 500 including a processor. As shown in Fig. 3, the information output device 100 includes a CPU (Central Processing Unit) 501, memories such as a ROM (Read Only Memory) 502 and a RAM (Random Access Memory) 503, a storage device 505 such as a hard disk for storing a program 504, a communication interface 508 for network connection, and an input / output interface 511 for inputting and outputting data.

[0016] The CPU 501 runs an operating system to control the information output device 100 according to the present disclosure. The CPU 501 also reads programs and data into memory from a recording medium 506 attached to a drive device 507, for example. The CPU 501 also functions as each component of the information output device 100 or as a part of these components, and executes processing or commands in the flowchart shown in FIG. 4, which will be described later, based on the program.

[0017] The recording medium 506 is, for example, an optical disk, a flexible disk, a magneto-optical disk, an external hard disk, or a semiconductor memory. A part of the recording medium in the storage device is a non-volatile storage device, and the program is recorded therein. The program may also be downloaded from an external computer (not shown) connected to a communication network.

[0018] The input device 509 is realized by, for example, a mouse, a keyboard, built-in key buttons, etc., and is used for input operations. The input device 509 is not limited to a mouse, a keyboard, or built-in key buttons, and may be, for example, a touch panel. The output device 510 is realized by, for example, a display, and is used to check output.

[0019] As described above, the first embodiment shown in Fig. 1 is realized by the computer hardware shown in Fig. 3. However, the means for realizing each component of the information output device 100 in Fig. 1 is not limited to the configuration described above. Furthermore, the information output device 100 may be realized by a single physically coupled device, or may be realized by two or more physically separate devices connected by wire or wirelessly. For example, the input device 509 and the output device 510 may be connected to the computer device 500 via a network.

[0020] The information collection unit 101 is a means for collecting at least different types of device information from evidence of the managed devices from their manufacture to their operation and from external information related to the devices. In this embodiment, the evidence refers to information that serves as objective evidence of the device configuration, logs, and inspection history spanning the system lifecycle from their manufacture to their operation. Specific examples of evidence include verification information for the authenticity of the device, hardware configuration information or software configuration information written inside the device, hardware or software configuration change history, operation logs such as setting changes during device operation, or operation logs such as reboots.

[0021] The information collection unit 101 collects, for example, evidence of the manufacturing of the managed equipment from a server device owned by a supplier. The information collection unit 101 also collects, for example, evidence of the operation of the managed equipment from equipment connected to an in-house network.

[0022] The information collection unit 101 may have a function of remotely collecting operational trails from target devices via a management network. In this case, the information collection unit 101 accesses the management function of the device to collect operational trails. The information collection unit 101 may also collect operational trails by receiving log information, etc., issued by the device.

[0023] In this embodiment, authenticity refers to the fact that the device has not been unintentionally altered from its manufacturing state, and that it has not been spoofed, replaced, or tampered with. An example of hardware substitution is the act of switching between a genuine product and a counterfeit product during transportation. Furthermore, the authenticity of hardware may be verified by comparing information stored as data within the device with a serial number printed on a label on the device itself or a component. However, verification results based on comparison of a serial number printed on a label are less reliable than verification results based on a digital signature. The information collection unit 101 may collect information regarding the reliability of the authenticity verification results.

[0024] The information collecting unit 101 may also collect, as device information, information on whether or not countermeasures against substitution or tampering have been taken. The information collecting unit 101 collects information on countermeasures against substitution or tampering from, for example, a server device owned by a device supplier. One example of countermeasures against substitution or tampering is sealing with tape to prevent the installation of an illegal chip.

[0025] The authenticity of software is verified, for example, by using secure boot to verify the integrity of the software based on a digital signature and its publisher. Here, the condition for verifying the authenticity of software may include the completion of hardware authenticity verification. Even if the authenticity of the hardware cannot be verified, the process of verifying the authenticity of software can be performed. However, if the authenticity of the hardware is not verified, the possibility of the software authenticity verification result being counterfeited increases. Furthermore, the information collecting unit 101 may also collect, as device information, the presence or absence of measures to prevent spoofing or tampering during software execution. The information collecting unit 101 collects information on measures to prevent spoofing or tampering from, for example, a server device owned by a supplier. Measures to prevent spoofing or tampering during software execution include, for example, a function to prevent memory tampering by exploiting vulnerabilities in the software while it is running.

[0026] The hardware configuration information includes at least a product ID such as a unique serial number and model number of the device itself or components incorporated into the device, such as a CPU, a power supply, and an SFP (Small Form Factor Pluggable).

[0027] The software configuration information includes an operating system (OS) that processes the hardware, software names such as libraries or applications, version information of the software, hash values, etc. The information collection unit 101 may collect software configuration information from a software bill of materials (SBOM).

[0028] Furthermore, the information collection unit 101 collects external information such as vulnerability information or equipment maintenance work schedules stored in the equipment management system. The information collection unit 101 may acquire vulnerability information that is publicly available on the Internet, or may acquire undisclosed vulnerability information as confidential information. The information collection unit 101 may also acquire vulnerability information that is publicly available via an API (Application Programming Interface) or other means. Examples of vulnerability information include configuration information of software in which a vulnerability has been discovered or examples of exploitation of the vulnerability.

[0029] The information collection unit 101 may collect device information, for example, when an operation to collect device information is performed on the device management screen, or may collect device information at predetermined intervals.

[0030] The output unit 102 is a means for outputting a combination of risk information used for risk assessment of a device based on the device information. The risk information is information used by an administrator to determine the reliability of a device, and is information obtained from the device information, such as whether the device is authentic, whether the device configuration has been changed, whether there are software vulnerabilities, whether there are cases of vulnerability exploitation, a device maintenance plan, or device history information. The output unit 102 outputs the combination of risk information to the output device 510 or the like. The output unit 102 may also provide the risk information to another program via an API.

[0031] The output unit 102 may display the same risk information in chronological order. For example, the output unit 102 may display authenticity information of a device at the time of shipment and during operation in chronological order. The output unit 102 may also display the device's evidence and external information side by side. The output unit 102 may also display the quantity of devices at risk and the change in quantity over time in addition to displaying risk information for each device. The output unit 102 may also display the quantity of devices at risk and, when that quantity is selected on the screen, display the risk information for each device. The output unit 102 may display the risk information for each device in descending order of risk. When displaying risk information for each device, the output unit 102 may also simultaneously display the evidence supporting the information. The output unit 102 may simultaneously display the quantity of risks detected in a specified period and the total amount of currently existing risks. The display unit for the risk quantity may be configured to allow an administrator to change the display unit, for example, to one unit for every 10 cases. Furthermore, the output unit 102 may hide the display of risk information for each device when an operation is performed on the screen, thereby excluding risk information that has already been addressed or that is known not to require any action, and narrowing down the risk information that needs to be addressed.

[0032] The operation of the information output device 100 configured as above will be described with reference to the flowchart of FIG.

[0033] 4 is a flowchart showing an outline of the operation of the information output device 100 according to the first embodiment. The processing according to this flowchart may be executed based on program control by the processor described above.

[0034] 4, first, the information collection unit 101 collects at least different types of device information from evidence of the managed devices from the time of manufacture to the time of operation and external information related to the devices (step S101). Next, the output unit 102 outputs a combination of risk information to be used for risk assessment of the devices based on the device information (step S102). The information output device 100 periodically repeats steps S101 to S102. This completes the operation of the information output device 100.

[0035] In the information output device 100 disclosed herein, the information collection unit 101 collects at least different types of device information from evidence of the managed devices from the time of manufacture to the time of operation and external information related to the devices, and the output unit 102 outputs a combination of risk information to be used for risk assessment of the devices based on the device information. This configuration makes it easier to find risks to the reliability of the devices that would not be apparent from a single piece of device information, and makes it possible to make the administrator aware of risks to the devices.

[0036] [Variation of the First Embodiment] Fig. 5 is a block diagram showing the configuration of an information output device 110 according to the present disclosure. The information output device 110 shown in Fig. 5 is also realized by the computer hardware shown in Fig. 3. As shown in Fig. 5, the information output device 110 includes an information collection unit 111, a storage unit 112, an output unit 113, and a warning unit 114. The information collection unit 111 and the output unit 113 are the same as the corresponding components in the first embodiment. This variation is based on the premise that there are multiple devices to be managed.

[0037] The storage unit 112 is a means for storing, for each device, the device information collected by the information collection unit 111. For example, if there are four devices (devices 1 to 4) to be managed, the storage unit 112 stores the device information for each of devices 1 to 4 in the storage device 505. The storage unit 112 may store the device information in a storage area such as a blockchain where information cannot be tampered with.

[0038] The warning unit 114 is a means for issuing a warning when the risk information satisfies a predetermined condition. The predetermined condition is, for example, a condition that is predetermined as a possible security risk to the device. The warning unit 114 outputs an alert signal when the risk information satisfies the predetermined condition. The warning unit 114 may display an alert on the output device 510 of the information output device 110 or output the alert as sound. The warning unit 114 may also provide the alert signal to another program via an API. In addition to the above-mentioned alert, the warning unit 114 may also highlight the combination of risk information that is the basis for outputting the alert signal.

[0039] Next, specific examples of the collection of equipment information and the output of a combination of risk information by the information output device 100 or information output device 110 of the present disclosure will be explained using drawings, but the specific examples described in this specification are merely examples and are not limited to these examples.

[0040] [Specific Example 1] Fig. 6 is a diagram for explaining the collection of device information and the output of risk information in specific example 1. In Fig. 6, L represents a process in the system life cycle from device manufacture to operation, and shows examples of processes such as shipping inspection, delivery, construction, operation, maintenance, and operation, but the process examples are not limited to these. Also, A1 in Fig. 6 represents an example of device information on managed devices 1 to 4 collected by the information collection unit 111, and B1 in Fig. 6 represents an example of a combination of risk information output by the output unit 113.

[0041] In specific example 1, the information collection unit 111 collects configuration information at different times during operation of the equipment and information verifying the authenticity of the configuration information. The output unit 113 outputs whether or not the configuration has been changed during operation of the equipment and whether or not the authenticity is confirmed. Specifically, in the example of Fig. 6, the information collection unit 111 collects, as equipment information, hardware configuration information and authenticity verification information at the time of system construction on X month Y day and at the time of maintenance on Z month W day. "CCC" and the like shown in the configuration information field of A1 indicates the hardware serial number, and "◯" shown in the "authenticity" field of A1 indicates that the authenticity of the hardware has been verified, and "X" indicates that the authenticity of the hardware has not been verified.

[0042] The reliability of hardware configuration information depends on the authenticity of the hardware. In other words, if the authenticity of the hardware cannot be verified, the hardware configuration information cannot be trusted. Therefore, in specific example 1, the information collection unit 111 collects hardware configuration information obtained during system construction and subsequent maintenance, as well as hardware authenticity verification information. Then, as shown in FIG. 6 , the output unit 113 outputs the presence or absence of hardware configuration changes and authenticity verification information for each device. This allows the administrator to recognize devices for which risks such as hardware substitution need to be addressed. In other words, the administrator can recognize that there is no risk for device 1 because there has been no change in its hardware configuration and the authenticity of the hardware has been verified. On the other hand, the administrator can recognize that devices 2 to 4 fall into at least one of the cases where the hardware configuration has been changed or the authenticity of the hardware has not been verified, and therefore need to address risks such as substitution.

[0043] [Specific Example 2] FIG. 7 is a diagram illustrating the collection of device information and the output of risk information in Specific Example 2. Specific Example 2 will be described using FIG. 7 , focusing on differences from Specific Example 1. In Specific Example 2, the information collection unit 111 collects configuration information at different times during device operation, verification information for the authenticity of the configuration information, and verification information for the authenticity of the configuration information at the time of device shipment. The output unit 113 outputs whether the device was authentic at the time of shipment, whether the configuration was changed during operation, and whether the authenticity was confirmed during operation. Specifically, in the example of FIG. 7 , the information collection unit 111 collects, as device information, the device information collected in Specific Example 1 (A22), as well as verification information (A21) for the authenticity of the hardware of the device at the time of shipment. The output unit 113 outputs, for each device, a combination of whether the hardware was authentic at the time of shipment, whether the configuration was changed during operation, and whether the hardware was authentic during operation (B2). As in Example 2, by using verification information of the authenticity of the hardware at the time of shipment in addition to the authenticity of the hardware during operation, the administrator can confirm whether the authenticity of the hardware was guaranteed at the time of shipment. It can be recognized that the authenticity of the hardware of device 3 in Fig. 7 had not been verified at the time of shipment, whereas the authenticity of the hardware of device 4 had been verified at the time of shipment.

[0044] Furthermore, in specific examples 1 and 2, the warning unit 114 may warn that the risk to the reliability of the hardware has increased if the device falls under any of the following (1) to (3): (1) when the authenticity of the hardware cannot be verified. In this case, the hardware configuration is unreliable. (2) when a hardware component is changed to a component with no shipping history, regardless of whether the hardware is authentic. In this case, the component may be unreliable. (3) when the hardware configuration is changed after the system is built, regardless of whether the hardware is authentic. In this case, the administrator is prompted to check whether any unintended configuration changes have been made.

[0045] The warning unit 114 may also issue a warning if the software configuration and authenticity fall under any of the following (4) to (6): (4) A version of software that has no shipping history is running. This is because unreliable software may be running. (5) The authenticity of the hardware cannot be verified. This is because the software configuration information is unreliable. (6) Software configuration information can be listed by component, but the component is not in the shipping history. This is because a component such as a library may have been replaced with an unauthorized version.

[0046] [Specific Example 3] FIG. 8 is a diagram illustrating the collection of device information and the output of risk information in specific example 3. In the example of FIG. 8, the information collection unit 111 collects, as device information, verification information (A31) of the authenticity of the device at the time of shipment and verification information (A32) of the authenticity of the device during operation. The output unit 113 outputs a combination of the authenticity status at the time of shipment and the authenticity status during operation for each device (B3). If the identification information, such as the device's serial number, is not authentic, there is a possibility that the device has been swapped. In the example of FIG. 8, the authenticity of all of devices 1 to 4 was verified at the time of shipment, but the authenticity of device 4 could not be verified during maintenance work on Z month W day after system construction. Therefore, the administrator can be made aware that device 4 may have been swapped between the time of system construction on X month Y day and Z month W day.

[0047] [Specific Example 4] FIG. 9 is a diagram illustrating the collection of device information and the output of risk information in specific example 4. In the example of FIG. 9 , the information collection unit 111 collects, as device information, configuration information (A41) of software in which a vulnerability has been discovered, software configuration information during device operation, and device configuration change information (A42). The output unit 113 outputs, for each device, whether the software has a vulnerability and whether any configuration changes have been made (B4). If any configuration changes are made to a device in which software with a reported vulnerability is installed, it is possible that the configuration changes were made due to exploitation of the vulnerability. In the example of FIG. 9 , both device 2 and device 4 have had their configuration changes made, but while no vulnerability has been reported in the software of device 2, a vulnerability has been reported in the software of device 4. This allows the administrator to recognize that the configuration change of device 2 was made with legitimate authority and that the configuration change of device 4 may have been made due to exploitation of a vulnerability.

[0048] Specific Example 5 FIG. 10 is a diagram illustrating the collection of device information and the output of risk information in Specific Example 5. In the example of FIG. 10 , the information collection unit 111 collects, as device information, information on scheduled maintenance work for the device (A51), a login history for the device (A52), and device setting change information (A53). The output unit 113 outputs, for each device, whether or not a setting change has occurred and whether or not an unplanned login has occurred (B5). If an unplanned login occurs after a setting change has been made, the setting change may have been the installation of a backdoor that allows logins by persons other than the administrator. In the example of FIG. 10 , device 1 was logged in on a maintenance work day (X-month Y and Z-month W), and no setting changes were made. Device 2 was logged in unplanned on a day that was not a maintenance work day (U-month V), but no setting changes were made. Device 3 was logged in on a maintenance work day (X-month Y), and the setting change was made as planned. Device 4 was logged in on a day that was not a scheduled work day (U-month V), and the setting change was made. Therefore, the administrator can recognize that a backdoor may have been installed in the device 4 through an unauthorized setting change.

[0049] [Specific Example 6] FIG. 11 is a diagram illustrating the collection of device information and the output of risk information in Specific Example 6. In Specific Example 6, the information collection unit 111 collects configuration information of software in which a vulnerability has been discovered, cases of exploitation of the vulnerability, and configuration information of the software of the device. Specifically, as shown in FIG. 11 , the information collection unit 111 collects, as device information, a vulnerability number identifying the vulnerability information, configuration information of the corresponding software, cases of exploitation of the vulnerability (A61), and configuration information of the software of the device (A62). The output unit 113 outputs, for each device, whether or not the software has a vulnerability and whether or not there has been an exploitation of the vulnerability (B6). Among vulnerable software, devices incorporating software for which exploitation cases have been reported require administrators to prioritize their response. In the example of FIG. 10 , the vulnerability number "CVE-yyy" corresponding to the configuration of software incorporated in device 1 has been reported as an exploit. Therefore, the administrator can recognize that device 1 requires priority response.

[0050] [Specific Example 7] FIG. 12 is a diagram illustrating the collection of device information and the output of risk information in specific example 7. In specific example 7, the information collection unit 111 collects, as device information, the time of device restart, the reason for restart, and history information. Specifically, as shown in FIG. 12, the information collection unit 111 collects, as device information, the time of restart and reason for restart for each device (A71), configuration change information for each device (A72), and login history for devices 1 to 4 (A73). The output unit 113 outputs, for each device, the reason for the restart and history information such as configuration changes or logins before and after the restart (B7). When malicious software is installed, a restart may be performed to enable the operation of the malicious software. Therefore, by outputting the fact that frequent logins or setting changes occurred before and after the restart, rather than as part of maintenance work, as in the case of device 4, the administrator can be made aware of the presence of malicious software.

[0051] [Specific Example 8] Fig. 13 is a block diagram showing the configuration of an information output device 120 according to the present disclosure. The information output device 120 shown in Fig. 13 is also realized by the computer hardware shown in Fig. 3. As shown in Fig. 13, the information output device 120 includes an information collection unit 121, a storage unit 122, a comparison unit 123, an output unit 124, and a warning unit 125.

[0052] In the information output device 120 in specific example 8, the information collection unit 121 collects patterns of external attacks made against managed devices and countermeasures for those attacks, as well as history information of the managed devices. The attack patterns are, for example, history information related to the methods used in past external attacks on managed devices or devices incorporated in other systems, and may be history information spanning multiple devices. The history information includes operation logs such as logins or setting changes, and operation logs such as reboots, as well as software vulnerability information and CWEs (Common Weaknesses).

[0053] The storage unit 122 stores history information of the devices it manages. The matching unit 123 matches the recorded attack patterns with the device history information. When the matching unit 123 matches the recorded attack pattern with the device history information, it outputs information about the matched attack pattern to the output unit 124. The output unit 124 then outputs the attack pattern and a countermeasure.

[0054] FIG. 14 is a diagram illustrating the collection of device information and the output of risk information in Example 8. In Example 8, past external attack patterns and their corresponding countermeasures are stored, and if a similar attack pattern is confirmed against a managed device, the attack pattern and the corresponding countermeasure are output. In the example of FIG. 14, the information collection unit 111 collects attack patterns and countermeasures (A81), vulnerability information (A82), login history (A83) for devices 1 to 4, setting change information (A84), and software configuration information (A85) for devices 1 to 4. If the output unit 124 can match the attack pattern with the history information of the managed device, it outputs the external attack pattern and the corresponding countermeasure. In this case, the warning unit 125 may output an alert signal. This allows the administrator to be notified of countermeasures if there is a possibility that an attack similar to a past external attack has been detected.

[0055] The operation of the information output device 120 configured as above will be described with reference to the flowchart of FIG.

[0056] 15 is a flowchart showing an outline of the operation of the information output device 120 of the present disclosure. Note that the processing according to this flowchart may be executed based on program control by the processor described above.

[0057] As shown in FIG. 15 , first, the information collection unit 121 collects external attack patterns and countermeasures against the managed devices, as well as device history information (step S121). Next, the storage unit 122 stores the history information of the managed devices (step S122). Next, the matching unit 123 matches the attack pattern with the history information of the managed devices (step S123). If the attack pattern can be matched with the history information (S124; YES), the output unit 124 outputs the attack pattern and countermeasures (step S125). On the other hand, if the attack pattern cannot be matched with the history information of the managed devices (S124; NO), the flow ends. This completes the operation of the information output device 120.

[0058] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above-described embodiments. 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.

[0059] For example, although multiple operations are described in a sequence in the form of a flowchart, the sequence does not limit the order in which the multiple operations are performed. Therefore, when implementing each embodiment, the sequence of the multiple operations can be changed within the scope that does not affect the content.

[0060] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes.

[0061] (Supplementary Note 1) An information output device comprising: an information collection means for collecting at least different types of equipment information from evidence of managed equipment from the time of manufacture to the time of operation and external information related to the equipment; and an output means for outputting a combination of risk information to be used for risk assessment of the equipment based on the equipment information.

[0062] (Supplementary Note 2) The information output device according to Supplementary Note 1, further comprising a storage unit that stores the device information for each device.

[0063] (Supplementary Note 3) The information output device according to Supplementary Note 1 or Supplementary Note 2, further comprising a warning unit that issues a warning when the risk information satisfies a predetermined condition.

[0064] (Appendix 4) The information output device described in Appendix 3, wherein the warning means issues a warning when at least one of the following occurs: the authenticity of the hardware of the device cannot be verified; a hardware component is changed to a component with no shipping history; or the configuration of the device is changed after the system is built.

[0065] (Supplementary Note 5) An information output device according to any one of Supplementary Notes 1 to 4, wherein the information collection means collects configuration information at different times during operation of the device and verification information for the authenticity of the configuration information, and the output means outputs whether or not a configuration change has occurred during operation of the device and whether or not the authenticity has been confirmed.

[0066] (Supplementary Note 6) The information collection means further collects verification information for the authenticity of the configuration information at the time of shipment of the device, and the output means outputs whether the device was authentic at the time of shipment, whether the configuration was changed during operation, and whether the device was authentic during operation, in the information output device described in Supplementary Note 5.

[0067] (Supplementary Note 7) The information output device described in any of Supplementary Notes 1 to 3, wherein the information collection means collects verification information of authenticity of the device at the time of shipment and verification information of authenticity of the device when it is in operation, and the output means outputs whether the device is authentic at the time of shipment and whether it is authentic when it is in operation.

[0068] (Supplementary Note 8) The information output device described in any of Supplementary Notes 1 to 3, wherein the information collection means collects configuration information of software in which a vulnerability has been discovered, configuration information of the software of the device, and setting change information of the device, and the output means outputs whether or not the software of the device has a vulnerability and whether or not a setting change has been made.

[0069] (Supplementary Note 9) The information output device according to any one of Supplementary Notes 1 to 3, wherein the information collection means collects information on work scheduled for the device, login history, and setting change information, and the output means outputs whether or not settings on the device have been changed and whether or not there has been an unplanned login.

[0070] (Supplementary Note 10) The information output device according to any one of Supplementary Notes 1 to 3, wherein the information collection means collects configuration information of software in which a vulnerability has been discovered, cases of exploitation of the vulnerability, and configuration information of the software of the device, and the output means outputs whether or not the software of the device has a vulnerability and whether or not there is an exploitation of the vulnerability.

[0071] (Supplementary Note 11) The information output device according to any one of Supplementary Notes 1 to 3, wherein the information collection means collects the time of restart of the device, the reason for the restart, and history information, and the output means outputs the reason for the restart and history information before and after the restart.

[0072] (Supplementary Note 12) An information output device according to any one of Supplementary Notes 1 to 3, further comprising a matching means for matching an external attack pattern made against a device with history information of the device, wherein the information collection means collects the attack pattern and countermeasures, and the history information of the device, and the output means outputs the attack pattern and the countermeasures when the attack pattern can be matched with the history information.

[0073] (Supplementary Note 13) An information output method in which a computer collects at least different types of equipment information from evidence of the equipment it manages from the time of its manufacture to the time of its operation and from external information related to the equipment, and outputs multiple pieces of risk information to be used in risk assessment of the equipment based on the equipment information.

[0074] (Supplementary Note 14) A recording medium storing a program that causes a computer to execute the following: collect at least different types of device information from evidence of managed devices from the time of manufacture to the time of operation and external information related to the devices; and output multiple pieces of risk information to be used for risk assessment of the devices based on the device information.

[0075] 100, 110, 120 Information output device 101, 111, 121 Information collection unit 102, 113, 124 Output unit 112, 122 Accumulation unit 114, 125 Warning unit 123 Collation unit 500 Computer device 501 CPU 502 ROM 503 RAM 504 Program 505 Storage device 506 Recording medium 507 Drive device 508 Communication interface 509 Input device 510 Output device 511 Input / output interface 512 Bus

Claims

1. An information output device comprising: an information collection means for collecting at least different types of equipment information from evidence of the equipment being managed from the time of manufacture to the time of operation and from external information related to the equipment; and an output means for outputting a combination of risk information to be used for risk assessment of the equipment based on the equipment information.

2. The information output device according to claim 1, further comprising a storage means for storing said device information for each device.

3. The information output device according to claim 1 or 2, further comprising a warning means for issuing a warning when the risk information satisfies a predetermined condition.

4. The information output device according to claim 3, wherein the warning means issues a warning when at least one of the following occurs: the authenticity of the hardware of the device cannot be verified, a hardware component has been changed to a component with no shipping history, or the configuration of the device has been changed after the system has been constructed.

5. An information output device as described in any one of claims 1 to 4, wherein the information collection means collects configuration information at different times during operation of the equipment and verification information of the authenticity of the configuration information, and the output means outputs whether or not a configuration change has occurred during operation of the equipment and whether or not the authenticity has been confirmed.

6. The information output device of claim 5, wherein the information collection means further collects verification information regarding the authenticity of the configuration information at the time of shipment of the device, and the output means outputs whether or not the authenticity was present at the time of shipment of the device, whether or not the configuration was changed during operation, and whether or not the authenticity was present during operation.

7. An information output device as described in any one of claims 1 to 3, wherein the information collection means collects verification information on the authenticity of the device at the time of shipment and verification information on the authenticity of the device when it is in operation, and the output means outputs whether the device is authentic at the time of shipment and whether it is authentic when it is in operation.

8. An information output device as described in any one of claims 1 to 3, wherein the information collection means collects configuration information of the software in which a vulnerability has been discovered, configuration information of the software of the device, and setting change information of the device, and the output means outputs whether or not the software of the device has a vulnerability and whether or not the setting has been changed.

9. An information output device as described in any one of claims 1 to 3, wherein the information collection means collects information on work planned for the equipment, login history, and setting change information, and the output means outputs whether or not settings of the equipment have been changed and whether or not there have been unplanned logins.

10. An information output device as described in any one of claims 1 to 3, wherein the information collection means collects configuration information of software in which a vulnerability has been discovered, cases of exploitation of the vulnerability, and configuration information of the software of the equipment, and the output means outputs the presence or absence of a vulnerability in the software of the equipment, and the presence or absence of cases of exploitation of the vulnerability.

11. An information output device as described in any one of claims 1 to 3, wherein the information collection means collects the time of restart of the device, the reason for the restart, and history information, and the output means outputs the reason for the restart and the history information before and after the restart.

12. An information output device as described in any one of claims 1 to 3, further comprising a comparison means for comparing an external attack pattern made against the equipment with historical information of the equipment, wherein the information collection means collects the attack pattern and countermeasures, and the historical information of the equipment, and the output means outputs the attack pattern and the countermeasures when the attack pattern can be compared with the historical information.

13. An information output method in which a computer collects at least different types of equipment information from evidence of the equipment it manages from the time of its manufacture to the time of its operation and from external information related to the equipment, and outputs multiple pieces of risk information to be used in risk assessment of the equipment based on the equipment information.

14. A recording medium storing a program that causes a computer to execute the following: Collect at least different types of equipment information from evidence from the manufacture to operation of managed equipment and external information related to said equipment, and output multiple pieces of risk information to be used for risk assessment of said equipment based on said equipment information.

Citation Information

Patent Citations

  • Measurement device and change history acquisition method using the same

    JP2006221538A

  • Remote access controller

    JP2008117007A

  • Method and program for unit configuration management

    JP2008152416A

  • Management device, management method, and management program

    JP2014191513A

  • Malfunction detection method based on diagnostic history

    JP2014532913A