JP7760354B2 - Information integration system and information provision method - Google Patents

Description

The present invention relates to an information integration system and an information provision method.

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

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 capacity) 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). Implementing security measures without conducting an appropriate availability analysis can result in erroneous risk assessment results without considering the impact on availability. In this state, the negative 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.

When attempting to collect the information needed to perform availability analysis from distributed information, it was necessary to collect the information needed for analysis separately for each security analysis process. Furthermore, to properly perform availability analysis, the collected information had to be cross-referenced with other related information. This complexity created a significant resource burden when collecting the information needed for availability analysis, which in turn increased the cost of performing availability analysis.

As background technology to the present invention, the following Patent Document 1 discloses a configuration that can match test results using test case IDs when executing distributed test cases. Patent Document 2 discloses a configuration that takes into account risk and downtime (availability) when conducting risk analysis.

International Publication No. 2018/0276109 International Publication No. 2018/0136921

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 or changed identifiers. Patent Document 2 can prioritize countermeasures based on an assessment of risk and their impact on availability, but cannot evaluate or predict the impact of countermeasures on actual business systems and subsequent business processes.

In other words, while both Patent Documents 1 and 2 allow for security analysis, they do not provide a clear direction for ensuring the availability of the target business system, and do not collect the information necessary to determine availability. This results in the aforementioned issue of being unable to determine the necessity or relevance of information for availability analysis, and placing a heavy burden on resources when collecting the information necessary for availability analysis.

In light of this, the present invention aims 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.

The information integration system and information provision method of the present invention are a system that provides availability analysis information used in the availability analysis of a business system that has multiple terminals, each of which executes a specific process to achieve a specific business flow. The system includes a terminal information DB that stores terminal information related to the status of each terminal collected from the multiple terminals in 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 multiple pieces of test scenario information related to the setting states of the terminals when performing the availability analysis 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. The information integrated by the information integration unit for each piece of test scenario information is provided as the availability analysis information.

It is possible to provide an information integration system and information provision method that can reduce the resource burden when collecting information required for availability analysis and support efficient security measures.

Software configuration of a security analysis system according to an embodiment of the present invention 1 is a hardware configuration example of a security analysis system according to an embodiment of the present invention. Test scenario information data table example Process flow example Process Information Data Table Example of terminal information data table Example of performing an availability analysis Example of a data table combining collected data used to perform availability analysis 1 is a main flow diagram of information integration used to perform availability analysis according to an embodiment of the present invention. Process information collection subflow Terminal information collection subflow Test scenario data collection subflow Collected data combination subflow Collected data combination subflow Related Station ID Selection Example Availability analysis execution subflow Device setting change subflow

Embodiments of the present invention will be described below with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some details have been omitted or simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

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

(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.

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 to that process. 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.

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 type of technology is known as 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 rendered 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.

In this way, the impact on availability is understood through analysis, and security controls (security measures) relevant to the target business system are introduced to reduce the security risk of the system. At the same time, the availability of components related to critical business processes is guaranteed, preventing unplanned downtime that could result in economic loss or physical damage.

(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.

The test scenario information DB5a, process graph information DB5b, and terminal information DB5c 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 in Figures 3, 5, and 6. For convenience of illustration, the test scenario information unit 7, process graph information unit 8, and terminal 9 are shown as one each, but they are actually made up 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.

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 stores this information in the test scenario information DB 5a, process graph information DB 5b, and terminal information DB 5c, respectively, thereby updating each database.

Test scenario information refers to the case materials used by the management system to verify security risks against business systems. Process information refers to the business flow processes of the business systems.

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

In the security platform, the availability analysis unit 6 obtains the information necessary for availability analysis from the information integration unit 4 and performs availability analysis. The availability analysis unit 6 returns the analysis results to the information integration system 1.

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.

(Figure 2)
In an example of the hardware configuration of the information integration system of the present invention, a CPU 10, a volatile memory 20, a non-volatile 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 non-volatile memory 30 with the CPU 10.

In other words, the test scenario information DB 5a, process graph information DB 5b, and terminal information DB 5c in Figure 1 are realized by non-volatile memory 30, and the information integration unit 4 is realized by the CPU 10 using volatile memory 20 as a work area to execute a predetermined program. However, the hardware configuration of the information integration system 1 is not limited to this; for example, the information integration system 1 can also be realized using a virtual computer, cloud server, etc.

(Figure 3)
The test scenario information DB 5a stores test scenario information collected from the test scenario information unit 7 in the data structure shown in Fig. 3. The test scenario information stored in the test scenario information DB 5a is as follows: Each item in the test scenario information DB 5a is explained below.

Each record (row) represents an individual test scenario. Collection time represents the collection time for 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 being performed at the station at the collection time. Test parameters represent variables used when creating test variations. Parameter constraints represent the type of parameter constraints on test parameters.

(Figures 4 and 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 the 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.

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.

Process information collected from the process graph information unit 8 is stored in the process graph information DB5b in the data structure shown in Figure 5, for example. 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 Figure 4, and indicates the ID of the process or terminal to which the station belongs, the ID of the station, and the IDs of the stations located before and after the station in the process flow 8a. The process graph information DB5b combines this information to show the process flow 8a between stations.

(Figure 6)
The terminal information DB 5c stores terminal information collected from the terminals 9 in the data structure shown in Fig. 6, for example. 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 displayed is, for example, the utilization rate of the CPU 10, and in this case, the status parameter value displayed is, for example, (CPU 10 utilization rate) 60%.

(Figure 7)
7 shows an example of information required for availability analysis in the availability analysis unit 6. In FIG. 7, the information required for availability analysis is shown using the 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 (device name Y) with terminal ID 2141 at a certain time X, it is necessary to apply test case 41 of test scenario 13 to station ID 12315 with process ID 25, and confirm that the response to data sent to network port 8312 is received within two minutes and has parameter restrictions set to include substring S.

When using this method of acquiring the information necessary for availability analysis, as mentioned above, the information necessary for analysis must be acquired at every station, resulting in a large amount of resource usage and high costs each time an availability analysis is performed. The purpose of this 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.

(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.

Note that Test 13-2141-1 is an example of terminal information and process information organized by test scenario information, and below it are listed multiple pieces of information necessary for availability analysis, such as Test 13-2141-2, Test 13-2141-3, etc.

(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.

(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.

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 represent the process flow within a single terminal. This process information includes, for example, multiple stations, input and output data, parameters such as operation over time, etc.

In step S104, the process information collected in step S103 is written to the process graph information DB 5b along 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 Figure 5).

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.

(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).

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

(Figure 12)
A series of sub-flows relating 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 utilizing test scenario data according to the present invention, which has not been performed conventionally.

In step S301, the information update unit 2 starts the 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, test case ID, associated station ID, test type, test parameters, and parameter limits (see Figure 3).

In step S305, it is determined whether test scenario data information can be obtained from another test scenario information unit 7. If so, 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.

(Figure 13A)
A series of subflows in step S400 in Fig. 9 related to the combination of data collected in Fig. 10 to 12 will be described. 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 Fig. 10 to 12, it is possible to reduce the resources required for availability analysis.

In step S401, the information integration unit 4 starts a subflow for combining collected data. In step S402, a terminal ID relevant to availability analysis is selected from information detectable 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 relevant terminal ID refers to an ID related to vulnerabilities from the terminal information, process information, and test scenario information collected in Figures 10 to 12.

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 use the previous station ID but are different from the related terminal ID are selected (station IDs that use the related terminal ID among the previous station IDs are not selected).

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

In step S406, an empty list (associated candidate station ID list) is created for associated candidate station IDs to be used in the flow described below. In step S407, an empty list (completed station ID list) is created for completed station IDs to be used in the flow described below.

In step S408, all station IDs for 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.

Specifically, first, from each record of process information stored in the process graph information DB5b, records that have the same terminal ID as the related terminal ID are provisionally extracted. Next, a search is made for records that have the same station ID value as the next station ID value in each provisionally extracted record. If the terminal ID of that record differs from the related terminal ID, the station ID of that record is added to the related candidate station ID list. Station IDs that use this related terminal ID include not only the next station ID of the same terminal, but also next stations within a different terminal ID.

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.

(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.

In step S412, it is determined whether the station ID selected in step S410 is in the completed station ID list. If so, 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.

Specifically, from each record of 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.

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.

In step S414, it is checked whether there are any other related candidate station IDs. If there are, the process proceeds to step S415; if not, the process proceeds to step S416. In step S415, another station ID is selected from the related candidate station ID list, and the process repeats from step S411.

In step S416, the station IDs associated with all test cases collected so far are selected, and then process information that uses the same station ID as the selected station ID is uniquely collected.

In step S417, the terminal IDs associated with all collected test cases are selected, and then the terminal information for which the same terminal ID is used is uniquely collected, completing the subflow sequence of step S400.

As described above, the flow shown in Figures 10 to 13 allows you to combine (integrate) the collected data (see Figure 8), and by extracting the information necessary for system availability analysis, you can reduce resources.

(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 from which information necessary for availability analysis is collected and stations from which information is not collected. In process flow 8b, each shaded station, including station 81a, represents a station from which information necessary for availability analysis is collected. On the other hand, in process flow 8b, each unshaded station, including station 81b, represents a station from which information necessary for availability analysis is not collected.

By extracting the information necessary for availability analysis through the subflow processing described in Figures 13A and 13B, each station in process flow 8b is classified in this way. This shows that the amount of resources required for availability analysis can be reduced.

(Figure 15)
This is a series of subflows of step S500 in Fig. 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 Fig. 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.

(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.

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

In step S606, another terminal ID is selected from the terminal setting change information. Once step S606 is completed, the flow is repeated from step S604.

In this way, by performing the information integration required for availability analysis on 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, for example, to evaluate the impact on availability when those countermeasures are applied and propose appropriate countermeasures.

The embodiment of the present invention described above provides the following advantages.

(1) The information integration system 1 is a system that 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 pieces of 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, for each piece of test scenario information, terminal information and process information related to availability analysis from the terminal information DB 5c and the process graph information DB 5b. The information integration unit 4 provides the integrated information for each piece of test scenario information as availability analysis information. This configuration reduces the resource load when collecting information required for availability analysis, providing an information integration system 1 that can support efficient security measures.

(2) The information integration unit 4 transmits the availability analysis information to an external party. 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.

(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 the availability analysis.

(4) An information provision method for providing availability analysis information used in the availability analysis of a business system that has multiple terminals 9, each of which performs a specific process to achieve a specific business flow. This information provision 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 terminal setting status 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 provision method is realized that reduces the resource load when collecting information required for availability analysis and supports efficient security measures.

The present invention is not limited to the above-described embodiments, and various modifications and other configurations can be combined without departing from the spirit of the invention. Furthermore, the present invention is not limited to those that include all of the configurations described in the above embodiments, and also includes those in which some of the configurations are omitted.

REFERENCE SIGNS LIST 1 Information integration system 2 Information update unit 3 Terminal setting change unit 4 Information integration unit 4a Example of combined data of collected data 5a Test scenario information database 5b Process graph information database 5c Terminal information database 6 Availability analysis unit 7 Test scenario information unit 8 Process graph information unit 81 Process station 81a Process station necessary for availability analysis 81b Process station not necessary for availability analysis 8a, 8b Process flow 9 Terminal 10 CPU
20 Volatile memory 30 Non-volatile memory 40 Network interface 50 Peripheral device

Claims (4)

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,
an information integration system that integrates each piece of extracted test scenario information with the terminal information and the process information that respectively correspond to the terminal ID and the process station ID included in each piece of test scenario information; 2. The information integration system according to claim 1,
The information integration unit transmits the availability analysis information to an external device. 2. The information integration system according to claim 1,
and an information integration system that changes settings of the terminal based on a result of the availability analysis based on the availability analysis information. A method for providing availability analysis information used in analyzing the availability of a business system , the business system including a plurality of terminals, each of which 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.