Information integration system and information provision method

Abstract

To provide an information integration system and an information provision method than can support efficient security measures by reducing a resource load in collecting information required for availability analysis.SOLUTION: A system for providing availability analysis information of a business system includes: a terminal information DB that stores terminal information on a state of each terminal; a process graph information DB that stores process information; a test scenario information DB that stores a plurality of pieces of test scenario information; and an information integration unit that extracts and integrates the terminal information and the process information related to the availability analysis for the test scenario information. The information integration unit provides information integrated for the test scenario information as the availability analysis information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information integration system and an information providing method. [Background technology]

[0002] In the OT (Operational Technology) / IoT (Internet of Things) fields, for example, security analysis in security platforms is carried out using methods such as assessing risk based on the business systems that are the targets of security measures and their vulnerability information, or determining risk over time and prioritizing and scheduling security patches (programs to resolve vulnerabilities and problems).

[0003] One type of security analysis is availability analysis, which analyzes the availability of a business system (the degree to which the system can continue to operate and its capabilities) when security measures are implemented. To perform an availability analysis, the information required for the analysis must be collected from the business system. This information is often distributed across system processes and not unified (collected). Therefore, if security measures are implemented without conducting an appropriate availability analysis, there is a risk of generating erroneous risk assessment results without considering the impact on availability. In this state, the adverse impact on the business system can be significant, and there is a risk of causing economic and physical damage despite the implementation of security measures.

[0004] When trying to collect the information necessary for performing availability analysis from distributed information, it was necessary to collect the information required for analysis separately for each security analysis process. Furthermore, to properly perform availability analysis, the collected information had to be collated with other related information. This complexity created a large resource burden when collecting the information necessary for availability analysis, which in turn increased the cost of performing availability analysis.

[0005] As background art of the present invention, Patent Document 1 below discloses a configuration that can match test results by test case ID when executing distributed test cases. Patent Document 2 discloses a configuration that takes into account risk and downtime (availability) when performing risk analysis. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] International Publication No. 2018 / 0276109 [Patent Document 2] International Publication No. 2018 / 0136921 Summary of the Invention [Problem to be solved by the invention]

[0007] Patent Document 1 can only match the execution and results of related test cases based on test case identifiers, but cannot match test cases with other information (such as process graphs) using multiple identifiers or changed identifiers. Patent Document 2 can prioritize measures based on an assessment of risk and impact on availability, but cannot evaluate or predict the measures applied to an actual business system and the subsequent impact on business processes.

[0008] In other words, in both Patent Documents 1 and 2, security analysis can be performed, but no direction is seen for ensuring the availability of the target business system, and the information necessary for determining availability is not collected. This leads to the aforementioned problem that it is not possible to determine the necessity and relevance of information for availability analysis, and collecting the information necessary for availability analysis places a heavy burden on resources.

[0009] In view of this, an object of the present invention is to provide an information integration system and an information providing method that can reduce the resource load when collecting information necessary for availability analysis and support efficient security measures. [Means for solving the problem]

[0010] The information integration system and information providing method of the present invention are a system that provides availability analysis information used for analyzing the availability of a business system that has a plurality of terminals, each of which performs a predetermined process to realize a predetermined business flow, and that includes a terminal information DB that stores terminal information related to the status of each terminal collected from the plurality of terminals of the business system, a process graph information DB that stores process information related to the flow of the processes in the business flow, a test scenario information DB that stores a plurality of pieces of test scenario information related to the setting states of the terminals when the availability analysis is performed on the business system, and an information integration unit that extracts and integrates the terminal information and process information related to the availability analysis from the terminal information DB and the process graph information DB, respectively, for each piece of test scenario information, and provides the information integrated for each piece of test scenario information as the availability analysis information. [Effects of the Invention]

[0011] It is possible to provide an information integration system and information provision method that can reduce the resource load when collecting information required for availability analysis and support efficient security measures. [Brief explanation of the drawings]

[0012] [Figure 1] Software configuration of a security analysis system according to an embodiment of the present invention [Figure 2] 1 is a hardware configuration example of a security analysis system according to an embodiment of the present invention. [Figure 3] Test scenario information data table example [Figure 4] Process flow example [Figure 5] Process Information Data Table [Figure 6] Example of terminal information data table [Figure 7] Example of performing an availability analysis [Figure 8] Example of a data table combining collected data used to perform availability analysis [Figure 9] 1 is a main flow diagram of information integration used to perform availability analysis according to an embodiment of the present invention. [Figure 10] Process information collection subflow [Figure 11] Terminal information collection subflow [Figure 12] Test scenario data collection subflow [Figure 13A] Collected data combination subflow [Figure 13B] Collected data combination subflow [Figure 14] Related Station ID Selection Example [Figure 15] Availability analysis execution subflow [Figure 16] Device setting change subflow

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0014] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0015] (Availability analysis according to the present invention) This embodiment describes an information integration system that uses a management system to collect various information for a business system that executes a certain business flow, and by integrating the collected information, can generate the information necessary for availability analysis when a security platform is applied.

[0016] Availability analysis when applying a security platform is, for example, an analysis to determine whether the continuous operation and processing performance of a process required for a certain business flow are sufficient to execute the business flow when the security platform is applied. The continuous operation and processing performance of this process are verified using test scenarios created for verification during the development and construction of the business system, or multiple test cases contained in those test scenarios.

[0017] For example, by recreating the parts of the business system being analyzed that you want to check, such as components or terminals, and making configuration changes, you can check availability using test cases related to those changes. This technology is called a security digital twin. More specifically, if a security patch for a certain security measure is introduced into a business system, and it is discovered that the patch has made a function necessary for the business flow unusable or caused processing performance to become insufficient, the impact of the security measure on availability can be determined, and the overall impact of security controls on availability can be grasped.

[0018] By analyzing the impact on availability in this way, security controls (security measures) related to the target business system can be implemented to mitigate security risks to the system, while at the same time ensuring the availability of components related to critical business processes and preventing unplanned downtime that could result in financial losses or physical damage.

[0019] (One embodiment of the present invention and overall configuration) (Figure 1) The information integration system 1 includes a test scenario information DB 5a, a process graph information DB 5b, and a terminal information DB 5c as databases according to an embodiment of the present invention. The information integration system 1 also includes an information update unit 2, a terminal setting change unit 3, and an information integration unit 4.

[0020] The test scenario information DB 5a, process graph information DB 5b, and terminal information DB 5c store information collected from the test scenario information unit 7, process graph information unit 8, and terminal 9, respectively, on the business system to which the security platform is applied. This information will be described later with reference to Figures 3, 5, and 6. Although the test scenario information unit 7, process graph information unit 8, and terminal 9 are shown as one each for convenience of illustration, they are actually composed of multiple components and terminals. The test scenario information unit 7 and process graph information unit 8 are, for example, information units on the management system of the business system, and the terminal 9 is a device that executes processes on that business system.

[0021] The information update unit 2 collects test scenario information, process information, and terminal information from the test scenario information unit 7, process graph information unit 8, and terminal 9, respectively, and updates each database by storing this information in the test scenario information DB 5a, process graph information DB 5b, and terminal information DB 5c, respectively.

[0022] The test scenario information is a case material for the management system to verify security risks against the business system, and the process information indicates the business flow process of the business system.

[0023] The information integration unit 4 combines the information stored in the test scenario information DB 5a, the process graph information DB 5b, and the terminal information DB 5c to obtain information necessary for analyzing the availability of the target business system. Details will be explained later in the flowchart.

[0024] In the security platform, the availability analysis unit 6 acquires information necessary for availability analysis from the information integration unit 4 and executes the availability analysis. The availability analysis unit 6 returns the analysis result to the information integration system 1.

[0025] The terminal setting change unit 3 changes the settings of the terminal 9 based on the analysis results of the availability analysis unit 6 returned to the information integration system 1 .

[0026] (Figure 2) In an embodiment of the hardware configuration of the information integration system of the present invention, a CPU 10, a volatile memory 20, a nonvolatile memory 30, and a peripheral device 50 are connected to one another. These are also connected to one another and to a network interface 40, thereby realizing IoT. The information integration system 1 shown in FIG. 1 is realized by integrating test scenario information, process information, and terminal information stored in the nonvolatile memory 30 with the CPU 10.

[0027] 1 are realized by the non-volatile memory 30, and the information integration unit 4 is realized by the CPU 10 executing a predetermined program using the volatile memory 20 as a work area. However, the hardware configuration of the information integration system 1 is not limited to this, and it is also possible to realize the information integration system 1 using, for example, a virtual computer, a cloud server, or the like.

[0028] (Figure 3) The test scenario information DB 5a stores test scenario information collected from the test scenario information unit 7, for example, in the data structure shown in Fig. 3. This is the test scenario information stored in the test scenario information DB 5a. Each item in the test scenario information DB 5a is explained below.

[0029] Each record (row) represents an individual test scenario. Collection time represents the collection time of the test scenario (test case) in each record. Note that the collection time value is omitted. Test scenario ID represents the number of one of multiple test scenarios. Test case ID represents the number of one of multiple test cases. Terminal ID represents the number of one of multiple devices. Process station ID (hereinafter referred to as station ID) represents the number of a process station (hereinafter referred to as station). Note that a station is the part where control calculations are performed. Test type represents the type of test type being performed at the station at that collection time. Test parameters represent variables used when creating test variations. Parameter constraints represent the type of parameter constraints on test parameters.

[0030] (Fig. 4, Fig. 5) Process flow 8a is an example of a business process flow (series of flows) of a business system represented by process information collected from process graph information unit 8. In Fig. 4, three terminal IDs, terminal ID 2105, terminal ID 2141, and terminal ID 4134, are displayed as IDs representing the respective terminals constituting the business system. Each terminal ID indicates the ID of the business process executed by that terminal: process ID 24 for terminal ID 2105, process IDs 25 and 26 for terminal ID 2141, and process ID 512 for terminal ID 4134. Each process ID indicates the ID of a process station 81 (hereinafter referred to as station 81) included in the process, which is the part that represents the execution unit of the process of the system in the target business.

[0031] Process ID 24 indicates station ID 12000, process ID 25 indicates station IDs 12314, 12315, 12316, and 12317, process ID 26 indicates station ID 24151, and process ID 512 indicates station ID 53534. Note that the arrow branching from station ID 12315 to station ID 12316 and station ID 12317 is, for example, an IF branch.

[0032] The process graph information DB5b stores process information collected from the process graph information unit 8 in, for example, the data structure shown in FIG. 5. Note that values ​​for the collection time, parameters, and output data items are omitted. Each record in the process graph information DB5b corresponds to each station 81 in the process flow 8a in FIG. 4, and indicates the ID of the process or terminal to which the station belongs, the ID of the station, and the ID of the station before and after the station in the process flow 8a. The process graph information DB5b combines this information to indicate the process flow 8a between stations.

[0033] (Figure 6) The terminal information DB 5c stores terminal information collected from the terminal 9 in, for example, the data structure shown in Fig. 6. The terminal information DB 5c displays items such as collection time of the terminal information, device ID, status parameter, and status parameter value. The status parameter displays, for example, the utilization rate of the CPU 10, and in this case, the status parameter value displays, for example, (CPU 10 utilization rate) 60%.

[0034] (Figure 7) FIG. 7 shows an example of information required to perform availability analysis in the availability analysis unit 6. In FIG. 7, the information required for availability analysis is shown using process flow 8a in FIG. 4. As shown in FIG. 7, for example, in order to analyze the state (network address is Z...) of terminal 9 with terminal ID 2141 at a certain time X, test case 41 of test scenario 13 must be applied to station ID 12315 with process ID 25, and it must be confirmed that the response to data sent to network port 8312 is received within two minutes and that parameter restrictions including substring S are set.

[0035] When using this method of acquiring the information necessary for availability analysis, as described above, the information necessary for analysis must be acquired at every station, resulting in the use of a large amount of resources each time an availability analysis is performed, resulting in high costs.The purpose of the present invention is to reduce costs and promote the efficiency of availability analysis by acquiring only the necessary information related to availability analysis during this process.

[0036] (Figure 8) 8 shows an example of an output data structure using collected data combination data when the present invention is implemented. In the information integration system 1 of this embodiment, for example, combination data 4a of FIG. 8 is output from the information integration unit 4 as information necessary for availability analysis of a business system that executes the business flow shown in process flow 8a of FIG. 4. The availability analysis unit 6 can perform efficient availability analysis by using combination data 4a that represents terminal information and process information organized for each test scenario information related to availability analysis.

[0037] Note that Test 13-2141-1 is an example of terminal information and process information organized by test scenario information, and multiple pieces of information related to availability analysis are listed below, such as Test 13-2141-2, Test 13-2141-3, and so on.

[0038] (Figure 9) This is the main flow of the information integration system 1. In step S100, a process information collection subflow is called. In step S200, a terminal information collection subflow is called. In step S300, a test scenario data collection subflow is called. In step S400, a collection data combination subflow is called. In step S500, an external availability analysis execution subflow is called. In step S600, a terminal setting change subflow is called. Each subflow of this main flow will be explained using Figures 10 to 16.

[0039] (Figure 10) 9, which is related to process information collection, will be described. In step S101, the process information collection subflow of the information update unit 2 is started, and in step S102, one of the multiple process graph information units 8 connected to the information integration system 1 is selected. In step S103, the information update unit 2 collects process information from the process graph information unit 8 selected in step S102.

[0040] The collected process information includes, for example, directed graph data describing the system process flow, followed by multiple sub-process information data. The directed graph data and sub-process information data each describe the process flow within a single terminal. This process information includes, for example, multiple stations, input and output data, and parameters such as operation over time.

[0041] In step S104, the process information collected in step S103 is written to the process graph information DB 5b together with the collection time. This process information includes, for each collection time, the associated process ID, associated terminal ID, associated station ID, previous and next stations, associated parameters, and output data (see FIG. 5).

[0042] In step S105, it is determined whether further process information can be acquired from another process graph information unit 8. If so, in step S106 another process graph information unit 8 is selected, and the flow from step S103 is repeated to collect process information. If not, the subflow of step S100 is terminated.

[0043] (Figure 11) A series of subflows in step S200 of FIG. 9 relating to terminal information collection will be described. In step S201, the information update unit 2 starts the subflow for collecting terminal information. In step S202, a terminal 9 is selected, and in step S203, the information update unit 2 collects terminal information from the selected terminal 9. This terminal information includes, for example, a terminal ID and state parameters of the terminal 9. In step S204, the information update unit 2 writes the terminal information collected in step S203 and the time of collection thereof into the terminal information DB 5c. This terminal information includes the terminal ID, state parameters, and state parameter values ​​(see FIG. 6).

[0044] In step S205, it is determined whether further terminal information can be acquired from another terminal 9. If so, another terminal 9 is selected in step S206, and the flow from step S103 is repeated to acquire further terminal information. If not, the subflow of step S200 is terminated.

[0045] (Figure 12) A series of sub-flows related to test scenario data collection in step S300 in Fig. 9 will be described. Note that the sub-flow in Fig. 12 is an information collection process that utilizes test scenario data according to the present invention, which has not been implemented conventionally.

[0046] In step S301, the information update unit 2 starts a test scenario data collection subflow. In step S302, the test scenario information unit 7 is selected. In step S303, the information update unit collects a test scenario from the test scenario information unit 7. This test scenario includes, for example, multiple test cases. In step S304, the test scenario collected in step S303 and its collection time are written to the test scenario information DB 5a. This test scenario information includes, for example, a test scenario ID, a test case ID, a related station ID, a test type, test parameters, and parameter limits (see FIG. 3).

[0047] In step S305, it is determined whether test scenario data information can be acquired from another test scenario information unit 7. If it can be acquired, in step S306 another test scenario information unit 7 is selected, and the flow from step S303 is repeated to collect test scenario data. If not, the subflow of step S300 is terminated.

[0048] (Figure 13A) A series of subflows in step S400 in Fig. 9 relating to the combination of collected data will be described below with reference to Figs. 10 to 12. This subflow is a subflow according to the present invention, and by extracting and combining only the information necessary for availability analysis based on the information collected in Figs. 10 to 12, it is possible to reduce the resources required for availability analysis.

[0049] In step S401, the information integration unit 4 starts a subflow for combining collected data. In step S402, a terminal ID related to availability analysis is selected from information that can be detected by the management system of the target business system. For example, if the asset management system has implemented security that detects vulnerabilities in the business system it manages, the related terminal ID means an ID related to vulnerabilities from the terminal information, process information, and test scenario information collected in Figures 10 to 12.

[0050] In step S403, all test scenario information (test cases) that use the same terminal ID as the related terminal ID selected in step S402 are extracted and collected from the test scenario information stored in the test scenario information DB 5a. In step S404, station IDs that use the related terminal ID selected in step S402 and that are different from the related terminal IDs used by the previous station IDs are selected (station IDs that use the related terminal IDs among the previous station IDs are not selected).

[0051] In step S405, all test cases that use the same station ID as the previous station ID selected in step S404 are collected.

[0052] In step S406, an empty list for associated candidate station IDs (associated candidate station ID list) to be used in a flow described later is created. In step S407, an empty list for completed station IDs (completed station ID list) to be used in a flow described later is created.

[0053] In step S408, all station IDs in which the associated terminal ID selected in step S402 is used and the next station ID is a terminal ID different from the associated terminal ID are added to the associated candidate station ID list.

[0054] Specifically, first, from each record of the process information stored in the process graph information DB 5b, records having the same terminal ID as the related terminal ID are provisionally extracted. Next, a search is made for records having the same station ID value as the next station ID value in each provisionally extracted record. If the terminal ID of that record is different from the related terminal ID, the station ID of that record is added to the related candidate station ID list. The station IDs using this related terminal ID include not only the next station ID of the same terminal, but also next stations within a different terminal ID.

[0055] In step S409, all test cases that use the same station ID as any station ID in the associated candidate station ID list (added in step S408) are collected. Any station ID for which a test case has been collected is added to the completed station ID list.

[0056] (Figure 13B) In step S410, a station ID is selected from the associated candidate station ID list, and in step S411, the station ID selected in step S410 is deleted from the associated candidate station ID list.

[0057] In step S412, it is determined whether the station ID selected in step S410 is in the completed station ID list. If it is, proceed to step S414. If not, proceed to step S413. In step S413, the next station ID from among the station IDs selected in step S410 is added to the associated candidate station ID list.

[0058] Specifically, from each record of the process information stored in the process graph information DB5b, records having the same station ID as the station ID selected in step S410 are extracted, and the value of the next station ID in each extracted record is added to the related candidate station ID list.

[0059] Furthermore, all test cases that use the same station ID as this added next station ID are collected (similar to step S409). After all test cases have been collected for the station ID next to the station ID selected from the related candidate station ID list, the used next station ID is added to the completed station ID list.

[0060] In step S414, it is checked whether there are other associated candidate station IDs, and if there are, the process proceeds to step S415, otherwise, the process proceeds to step S416. In step S415, another station ID in the associated candidate station ID list is selected, and the flow from step S411 is repeated.

[0061] In step S416, the station IDs relating to all test cases collected up to this point are selected, and further, process information in which the same station ID as the selected station ID is used is uniquely collected.

[0062] In step S417, the terminal IDs relating to all collected test cases are selected, and further, the terminal information in which the same terminal ID as the terminal ID is used is uniquely collected, and the series of sub-flows in step S400 is terminated.

[0063] As described above, the flows shown in FIGS. 10 to 13 allow the collected data to be combined (integrated) (see FIG. 8), and the information required for analyzing the system's availability can be extracted, thereby reducing resources.

[0064] (Figure 14) Process flow 8b in Figure 14 is an example of a process flow different from process flow 8a in Figure 4, in which each station in the process flow is divided into stations that collect information necessary for availability analysis and stations that are not. In process flow 8b, each shaded station, including station 81a, represents a station that collects information necessary for availability analysis. On the other hand, in process flow 8b, each unshaded station, including station 81b, represents a station that is not a station that collects information necessary for availability analysis.

[0065] 13A and 13B, extracting the information necessary for availability analysis classifies each station in process flow 8b in this way. This shows that the amount of resources required for availability analysis can be reduced.

[0066] (Figure 15) This is a series of subflows of step S500 in Figure 9 related to the execution of availability analysis. In step S501, the information integration unit 4 starts the subflow of executing availability analysis. In step S502, the combined data (see Figure 8) of the data collected in steps S100 to S400 is sent to the availability analysis unit 6 outside the information integration system 1. In step S503, the information integration system 1 receives the analysis results from the availability analysis unit 6, and the subflow of step S500 ends.

[0067] (Figure 16) 9, which is related to changing terminal settings. In step S601, the terminal setting change subflow is started in the terminal setting change unit 3. In step S602, terminal setting change information is extracted from the analysis results received from the availability analysis unit 6.

[0068] In step S603, a terminal ID is selected from the terminal setting change information. In step S604, the terminal setting change is executed on the terminal 9 using the terminal ID selected in step S603. In step S605, it is determined whether there are other terminal IDs for which the terminal setting change has not been performed. If there are, the process proceeds to step S606; if not, the subflow of step S600 is terminated.

[0069] In step S606, another terminal ID is selected from the terminal setting change information. After step S606 is completed, the flow from step S604 is repeated again.

[0070] In this way, by performing the information integration required for availability analysis in a system that is further implemented in the target business system, it is possible to provide a mechanism that goes beyond conventional vulnerability diagnosis, attack simulation, and countermeasure planning, and evaluates the impact on availability when the countermeasure is applied, and proposes appropriate countermeasures.

[0071] According to the embodiment of the present invention described above, the following advantageous effects are achieved.

[0072] (1) The information integration system 1 provides availability analysis information used to analyze the availability of a business system that includes multiple terminals 9, each of which executes a specific process to realize a specific business flow. The information integration system 1 includes a terminal information DB 5c that stores terminal information related to the status of each terminal 9 collected from the multiple terminals 9 included in the business system; a process graph information DB 5b that stores process information related to the flow of business processes; a test scenario information DB 5a that stores multiple test scenario information related to the setting states of terminals when performing availability analysis on the business system; and an information integration unit 4 that extracts and integrates terminal information and process information related to availability analysis from the terminal information DB 5c and the process graph information DB 5b for each test scenario information. The information integration unit 4 provides the integrated information for each test scenario information as availability analysis information. This configuration reduces the resource load when collecting information required for availability analysis, thereby providing an information integration system 1 that can support efficient security measures.

[0073] (2) The information integration unit 4 transmits the availability analysis information to an external device. In this way, the information necessary for availability analysis collected by the information integration unit 4 can be analyzed by the availability analysis unit 6.

[0074] (3) The information integration system 1 changes the settings of the terminal 9 based on the results of availability analysis based on the availability analysis information. In this way, security analysis can be performed that reflects the results of availability analysis.

[0075] (4) An information providing method for providing availability analysis information used in the availability analysis of a business system that has multiple terminals 9 and realizes a specified business flow by each terminal 9 performing a specified process. This information providing method collects process information related to the process flow of the business flow, collects terminal information related to the status of each terminal 9 from the multiple terminals 9 included in the business system, collects multiple pieces of test scenario information related to the setting status of the terminals when performing availability analysis on the business system, and extracts and integrates terminal information and process information related to availability analysis for each piece of test scenario information from the collected terminal information and process information. This integrated information for each piece of test scenario information is provided as availability analysis information. In this way, an information providing method is realized that reduces the resource load when collecting information necessary for availability analysis and supports efficient security measures.

[0076] The present invention is not limited to the above-described embodiments, and various modifications and combinations of other configurations are possible without departing from the spirit of the present invention. Furthermore, the present invention is not limited to those having all of the configurations described in the above-described embodiments, and includes those in which some of the configurations are omitted. [Explanation of symbols]

[0077] 1. Information Integration System 2 Information update department 3. Terminal setting change section 4. Information Integration Department 4a Example of combined data collection 5a Test scenario information database 5b Process graph information database 5c Device Information Database 6 Availability Analysis Department 7 Test scenario information section 8 Process Graph Information Section 81 Process Station 81a Process Stations Required for Availability Analysis 81b Process stations not required for availability analysis 8a, 8b Process Flow 9 Terminals 10 CPU 20 Volatile Memory 30 Non-volatile memory 40 network interfaces 50 Peripherals

Claims

1. A system for providing availability analysis information used for analyzing the availability of a business system that has a plurality of terminals and realizes a predetermined business flow by each terminal performing a predetermined process, comprising: a terminal information DB for storing terminal information relating to the status of each terminal collected from each of the plurality of terminals included in the business system; a process graph information DB that stores process information related to the process flow of the business flow; a test scenario information DB storing a plurality of pieces of test scenario information, each having a terminal ID unique to one of the plurality of terminals and a process station ID unique to a process station representing an execution unit of the process on the terminal, regarding the setting state of the terminal when the availability analysis is performed on the business system; an information integration unit that extracts and integrates the terminal information, the process information, and the test scenario information related to the availability analysis from the terminal information DB, the process graph information DB, and the test scenario information DB, respectively, and provides the integrated information as information to be used in the availability analysis, each of the plurality of terminals includes at least one of the process stations; the information integration unit selects a relevant terminal related to the availability analysis from the plurality of terminals; From the test scenario information DB, the test scenario information having the terminal ID of the associated terminal; extracting the test scenario information having the process station ID of the process station that is executed on the terminal corresponding to the terminal ID and that is executed before the process station that is executed on the related terminal in the process information; extracting test scenario information if there is test scenario information having the process station ID of a process station that is executed next to the process station executed on the associated terminal, the process station having the terminal ID different from the associated terminal and that is executed on the terminal corresponding to the terminal ID; and if there is no test scenario information having the test scenario information, extracting test scenario information having the process station IDs of all process stations that are next to the process station that is executed next to the process station executed on the associated terminal, Each piece of extracted test scenario information is integrated with the terminal information and the process information corresponding to the terminal ID and the process station ID included in each piece of test scenario information, respectively. Information integration system.

2. 2. The information integration system according to claim 1, The information integration unit transmits the availability analysis information to an external device. Information integration system.

3. 2. The information integration system according to claim 1, Changing the settings of the terminal based on the results of the availability analysis based on the availability analysis information. Information integration system.

4. A method for providing availability analysis information used in analyzing the availability of a business system in which a system has a plurality of terminals and each terminal performs a predetermined process to realize a predetermined business flow, comprising: the terminal has at least one process station for performing the predetermined process; The system selects relevant terminals from the plurality of terminals that are relevant to the availability analysis; the system extracts, from test scenario information relating to the setting state of the terminal when performing the availability analysis on the business system, the test scenario information having the terminal ID of the related terminal, and the test scenario information having the terminal ID different from the related terminal and having the process station ID of the process station executed on the terminal corresponding to the terminal ID, the process station being executed before the process station executed on the related terminal in process information relating to the process flow of the business flow; The system further extracts test scenario information when there is test scenario information having the process station ID of the process station that has the terminal ID different from that of the related terminal and is executed on the terminal corresponding to the terminal ID, and that is executed next to the process station that is executed on the related terminal in the process information; If there is no such test scenario information, extract the test scenario information having the process station IDs of all the process stations subsequent to the process station executed next to the process station executed on the related terminal in the process information; The system integrates each extracted test scenario information with the terminal information and the process information corresponding to the terminal ID and the process station ID included in each test scenario information, The system provides the integrated information as information to be used in the availability analysis. Information provision method.

Images