ATTACK SCENARIO GENERATION DEVICE AND ATTACK SCENARIO GENERATION METHOD
The attack scenario generation device addresses the limitations of conventional scenarios by generating tailored, diverse, and accurate attack paths based on specific system conditions, enhancing cyber defense planning with high-evaluation techniques.
Patent Information
- Application Number
- JP2021086749
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-05-24
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2041-05-24
AI Technical Summary
Conventional cyber attack scenarios lack specificity and variation, limiting their effectiveness in generating meaningful countermeasures for specific systems, and existing methods primarily reproduce past cases without adequately covering potential threats.
An attack scenario generation device that simulates cyber attack behavior by inputting generation conditions, evaluating attack techniques, and generating scenarios based on region, industry, and attack technology, allowing for the creation of diverse and accurate attack paths tailored to specific systems.
The device generates highly rated attack scenarios that consider countermeasures beyond past cases, enabling flexible and accurate planning for cyber defense by prioritizing high-evaluation attack techniques and incorporating them into system-specific scenarios.
Smart Images

Figure 0007578541000001 
Figure 0007578541000002 
Figure 0007578541000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an attack scenario generating device and an attack scenario generating method. [Background technology]
[0002] Currently, cyber attacks (such as unauthorized access to confidential information assets) against computer systems (hereafter abbreviated as "systems") have become a serious problem, and measures against cyber attacks are essential for the safe operation of systems. Therefore, it is useful to plan countermeasures based on cyber attack scenarios (also abbreviated as "attack scenarios" or "scenarios") that simulate the actions of cyber attackers (people or programs, etc.) because it is possible to identify the content of countermeasures and prioritize them.
[0003] In order to plan countermeasures based on this cyber attack scenario at the level of specific countermeasure technologies, an attack scenario is required that specifies the detailed actions of the attacker, such as the "attack techniques" that the attacker will use. Here, an attack technique is a specific technique for achieving the purpose of the attack (using email to infiltrate a system, via USB memory, etc.). Therefore, an attack technique corresponds to the goal of the attack, and attack tactics are a categorization of attack techniques. Attack tactics are roughly the same as the purpose of the attack (infiltrating a system, stealing information, etc.). And attack tactics include one or more attack techniques.
[0004] An attack scenario determines the execution order of attack techniques. A detailed attack scenario enables a countermeasure planner (hereinafter, "user") to plan countermeasures at the level of specific countermeasure techniques corresponding to attack tactics and attack techniques. Therefore, a method and device for generating an attack scenario that specifies attack tactics and attack techniques that will realize actual threats has been required.
[0005] Regarding a method for generating the above attack scenario, a technique disclosed in Patent Document 1 is known. Patent Document 1 discloses a technique for carrying out processes in the following order: receipt of an incident report, extraction of keywords, shallow machine learning technology, deep machine learning technology, simulation, and output. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] JP 2019-145091 A Summary of the Invention [Problem to be solved by the invention]
[0007] However, conventional cyber attack scenarios that simulate the actions of attackers are highly abstract and do not lead to the development of technical security measures. In other words, they only create attack scenarios for general targets, and it is difficult to create attack scenarios that can be used to develop meaningful measures for specific systems.
[0008] In addition, the technology disclosed in Patent Document 1 reproduces past cyber-attack cases in a separate system. However, the method disclosed in Patent Document 1 only reproduces past cases on the system targeted by the attack, and the attack scenarios that can be generated are limited in variation and accuracy, making it impossible to fully cover countermeasure planning.
[0009] The present invention has been made in view of the above circumstances, and has an object to generate attack scenarios that are not limited to reproducing past attack cases. [Means for solving the problem]
[0010] The attack scenario generation device according to the present invention generates attack scenarios that simulate the behavior of cyber attacks. At least the generation conditions including region, industry and attack technology,Acquire information on cyber-attack cases, attack tactics that stipulate the actions taken by cyber-attacks, and attack techniques that realize the attack tactics, By referring to an attack case storage unit in which attack cases are stored and an attack tactic and attack technique storage unit in which specific attack techniques capable of realizing attack tactics indicating actions to be taken by a cyber attack are stored together with the attack tactics, a generation condition for an attack scenario is satisfied. An attack technology evaluation unit that evaluates attack technologies for each attack case, and based on at least one of system information of a computer system including an attack target of a cyber attack and security measure information of components of the computer system and the evaluation results of the attack technologies, An attack path is generated that specifies the order of attacks on the components of a computer system, and a combination of attack techniques is generated for each component based on the evaluation results of the attack techniques. Attacks against computer systems, including at least one attack technique At least one Attack scenario The attack scenario includes an attack technique that is input as a generation condition and has a higher evaluation than other attack techniques, and the attack scenario is directed to an area and an industry in which a computer system to be attacked is located. an attack scenario generation unit that generates an attack scenario; Depending on the evaluation results of the attack techniques and an attack scenario output unit that outputs an attack scenario. Effect of the Invention
[0011] According to the present invention, by inputting conditions for generating an attack scenario, an attack scenario including highly evaluated attack techniques is generated, making it possible to consider countermeasures against cyber attacks without being limited to reproducing past attack cases. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]
[0012] [Figure 1] 1 is a functional block diagram showing an example of the functional configuration of an attack scenario generation system according to a first embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of a system configuration of an attack scenario generation system according to a first embodiment of the present invention. [Diagram 3] 4 is a diagram showing an example of attack case information stored in an attack case storage unit according to the first embodiment of the present invention; FIG. [Figure 4] 3 is a diagram showing an example of offensive tactics / technique information stored in an offensive tactics / technique storage unit according to the first embodiment of the present invention; FIG. [Diagram 5] FIG. 2 is a diagram showing an example of a display of an attack scenario condition input screen according to the first embodiment of the present invention. [Figure 6]FIG. 2 is a diagram showing an example of the configuration of an evaluation result list according to the first embodiment of the present invention. [Figure 7] 1 is a diagram showing an example of a system configuration of a system inputted into a system information input unit according to a first embodiment of the present invention; [Figure 8] 3 is a diagram showing an example of the configuration of system configuration information according to the first embodiment of the present invention; FIG. [Figure 9] FIG. 2 is a diagram showing a display example of a system information input screen according to the first embodiment of the present invention. [Figure 10] 1 is a flowchart showing an example of a process in which an attack scenario generation unit according to the first embodiment of the present invention generates a scenario. [Figure 11] 3 shows a list of attack scenarios according to the first embodiment of the present invention. [Figure 12] FIG. 2 is a diagram showing an example of a scenario output screen according to the first embodiment of the present invention. [Figure 13] FIG. 11 is a functional block diagram showing an example of the functional configuration of an attack scenario generation system according to a second embodiment of the present invention. [Figure 14] FIG. 11 is a diagram showing a display example of a case information input screen according to the second embodiment of the present invention. [Figure 15] FIG. 11 is a diagram showing a display example of a confirmation and editing screen according to the second embodiment of the present invention. [Figure 16] FIG. 11 is a diagram illustrating an example of attack case information to which information on new attack cases has been added according to the second embodiment of the present invention. [Figure 17] FIG. 13 is a functional block diagram showing an example of the functional configuration of an attack scenario generation system according to a third embodiment of the present invention. [Figure 18] FIG. 13 is a diagram showing an example of measure content information according to the third embodiment of the present invention. [Figure 19] FIG. 13 is a diagram showing an example of a correspondence relationship between attack techniques and countermeasures according to the third embodiment of the present invention. [Figure 20] FIG. 13 is a diagram showing a display example of a countermeasure screen according to the third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functions or configurations are designated by the same reference numerals, and redundant description will be omitted.
[0014] [First embodiment] FIG. 1 is a functional block diagram showing an example of a functional configuration of an attack scenario generation system 1 according to the first embodiment. The attack scenario generation system 1 according to the first embodiment includes an attack scenario generation condition input unit 101, a system information input unit 102, an attack example storage unit 105, an attack tactic / technique storage unit 106, and an attack scenario generation device 20.
[0015] The attack scenario generation device 20 is a device that generates an attack scenario of a cyber attack against a computer system 710 (hereinafter abbreviated as "system 710") to which components such as those shown in Fig. 7, which will be described later, are connected. Note that an example of the components of the system 710 is a notebook PC 702 shown in Fig. 7. The specific system configuration of the system 710 will be described later.
[0016] The attack scenario generation condition input unit 101 inputs conditions for generating an attack scenario to the attack technique evaluation unit 103 . The system information input unit 102 inputs system information consisting of a system configuration 700 of a system 710 for which a scenario is to be generated, and system configuration information 800. Here, the system configuration 700 indicates the connection status of each device, and the system configuration information 800 indicates device information of each device.
[0017] The attack example storage unit 105 stores attack example information 300 as information on a number of attack examples that have taken place in the past. The attack tactics / technique memory unit 106 (an example of an attack tactics and attack technique memory unit) stores attack tactics / technique information 400 as information regarding attack tactics indicating the actions taken by a cyber attack, and specific attack techniques that can realize the attack tactics.
[0018] Below, we will explain an example of the configuration and operation of each block (functional unit) of the attack scenario generation device 20. This attack scenario generation device 20 includes an attack technique evaluation unit 103, an attack scenario generation unit 104, and an attack scenario output unit 107.
[0019] The attack technique evaluation unit 103 acquires the generation conditions of an attack scenario simulating the behavior of a cyber attack, information on the attack cases of the cyber attacks, the attack tactics that define the behavior of the cyber attack, and the attack techniques that realize the attack tactics, and evaluates the attack techniques for each attack case. At this time, the attack technique evaluation unit 103 evaluates the attack techniques based on the generation conditions of the attack scenario by referring to the attack case storage unit 105 and the attack tactics / technique storage unit 106. For example, the attack technique evaluation unit 103 reads the attack case information 300 from the attack case storage unit 105, and reads the attack tactics / technique information 400 including the tactics and techniques of the cyber attacks from the attack tactics / technique storage unit 106. Then, the attack technique evaluation unit 103 evaluates the suitability of each attack technique for use in scenario generation based on the generation conditions of the attack scenario input from the attack scenario generation condition input unit 101, the attack case information 300, and the attack tactics / technique information 400, and outputs the evaluation result to the attack scenario generation unit 104. In this specification, the term "evaluation" is used to refer to attack techniques, but any term such as evaluation points, evaluation values, evaluation indices, etc. may be used as long as it is an index of evaluation.
[0020] The attack scenario generation unit 104 generates an attack scenario for the system 710 including at least one attack technique highly evaluated based on at least one of the system information of the system 710 (see FIG. 7) including the target of the cyber attack and the security countermeasure information of the components of the system 710 and the evaluation result of the attack technique. For example, the attack scenario generation unit 104 generates an attack scenario using the evaluation result of each attack technique evaluated by the attack technique evaluation unit 103, the system configuration 700 input from the system information input unit 102, and the system configuration information 800. At this time, the attack scenario generation unit 104 generates an attack path that specifies the order of attacks on the components of the system 710, and generates an attack scenario consisting of a combination of attack techniques for each component based on the evaluation result of the attack technique. Then, the attack scenario generation unit 104 generates at least one attack scenario.
[0021] The attack scenario output unit 107 outputs the attack scenario that has been generated by the attack scenario generation unit 104. Then, the attack scenario output unit 107 outputs multiple attack scenarios according to the evaluation results of the attack techniques. The attack scenarios output by the attack scenario output unit 107 are displayed on a display device external to the attack scenario generation device 20, such as terminal devices 26-1 and 26-2 shown in FIG. 2. Each memory unit and calculation unit configured in the attack scenario generation system 1 may be configured as a CPU (Central Processing Unit) or a PC (Personal Computer) itself.
[0022] FIG. 2 is a block diagram showing an example of a system configuration of the attack scenario generation system 1. The attack scenario generation system 1 is composed of an attack scenario generation device 20, a storage device 24, and input sections of terminal devices 26-1 and 26-2, and the functions of these devices are realized by a computer. The attack scenario generation device 20 is connected to the terminal devices 26-1 and 26-2.
[0023] The attack scenario generation device 20 is composed of a processing unit 21, a memory 22, and an input / output I / F 23, whose functions are realized by a CPU, which are connected to each other via a bus or the like.
[0024] The processing unit 21 includes an attack technique evaluation unit 103, an attack scenario generation unit 104, a case information analysis unit 1302, an analysis result confirmation and editing unit 1303, an attack scenario output unit 107, a countermeasure review unit 1702, and a recommended countermeasure output unit 1703. Here, the case information analysis unit 1302 and the analysis result confirmation and editing unit 1303 are functional units included in the processing unit 21 according to the second embodiment, and the countermeasure review unit 1702 and the recommended countermeasure output unit 1703 are functional units included in the processing unit 21 according to the third embodiment. Each functional unit included in the processing unit 21 can be realized by a program executed by a CPU constituting the attack scenario generation device 20. In other words, each function according to each embodiment is realized by expanding the program in the memory 22 and executing each of these functions and calculations in the processing unit 21.
[0025] The attack scenario generation device 20 is connected to the storage device 24 via the input / output I / F 23 . The storage device 24 stores attack example information 300, attack tactic / technique information 400, and countermeasure content information 1800. In addition to the attack example storage unit 105 and attack tactic / technique storage unit 106 shown in Fig. 1, the storage device 24 also includes a countermeasure content storage unit 1701 that stores countermeasure content information 1800. The functions of the countermeasure content information 1800 and the countermeasure content storage unit 1701 are used by the processing unit 21 according to the third embodiment. In addition, the storage device 24 may be provided inside the attack scenario generation device 20. The storage device 24 is an example of a computer-readable non-transitory storage medium that stores a program executed by the attack scenario generation device 20.
[0026] The case information analysis unit 1302 and the analysis result confirmation and editing unit 1303 shown in FIG. 2 are used in the second embodiment described later, and do not need to be used in the first embodiment. Moreover, the countermeasure examining unit 1702 and the recommended countermeasure output unit 1703 are used in the third embodiment, and therefore may not be used in the first embodiment. Moreover, the countermeasure content information 1800 and the countermeasure content storage unit 1701 are information used in the third embodiment, and therefore may not be stored in the storage device 24 in the first embodiment.
[0027] The attack scenario generation device 20 is connected to various terminal devices 26-1 and 26-2 via the input / output I / F 23. The terminal devices 26-1 and 26-2 are each realized by a computer such as a PC, and have the function of accepting input from a user of the attack scenario generation device 20 and displaying the processing results of the attack scenario generation device 20. In other words, the terminal devices 26-1 and 26-2 function as the attack scenario generation condition input unit 101 and the system information input unit 102 in FIG. 1, and the case information input unit 1301 in FIG. 13. The terminal device 26-1 is directly connected to the attack scenario generation device 20. The terminal device 26-2 is connected to the attack scenario generation device 20 via the network 25.
[0028] The terminal devices 26-1, 26-2 may be configured as one unit with the attack scenario generation device 20. In other words, the attack scenario generation device 20 may be provided with a display device and an input / output device. When the terminal devices 26-1, 26-2 are configured as components of the attack scenario generation system 1, it is preferable to provide the functions of the attack scenario generation device 20 to a desktop PC 701, a notebook PC 702, a control server 703, and a controller 704 shown in FIG. 7, which will be described later.
[0029] In addition, the attack scenario generation device 20 can also connect to the Internet 27 and acquire information from outside the attack scenario generation system 1. For example, the attack scenario generation device 20 may receive attack case information 300 from a system to be verified that is connected via the Internet 27.
[0030] FIG. 3 is a diagram showing an example of attack example information 300 stored in the attack example storage unit 105. As shown in FIG. The attack case information 300 includes various information related to cyber-attack cases that are the results of analyzing the attack cases. The attack case information 300 is configured by associating information on each of the following items for each attack case: case number 310, time period 320, industry 330, region 340, system configuration characteristics 350, attack target 360, attack purpose 370, and attack technique 380. Each item of the attack case information 300 will be described below.
[0031] The case number 310 stores a case number that uniquely represents an attack case. The time when an attack case occurred is stored in the time 320. In the example of Fig. 3, the year when an attack case occurred, such as "2000", "2020", "2018", or "2010", is stored as the time. The name of the industry to which the system targeted by the attack belongs is stored in the industry 330. In the example of Fig. 3, industries such as railroads, automobile manufacturing, and electricity are included.
[0032] Region 340 stores region names as physical locations where systems targeted by attacks exist. In the example of Fig. 3, region names such as North America, Europe, and Asia are stored in region 340. Region 340 also includes other region names such as Africa and South America. Also, country names may be stored in region 340 instead of region names. The characteristics of the configuration of the system targeted by the attack are stored in the system configuration characteristics 350. In the example of Fig. 3, the characteristics include the use of a remote desktop, a cloud connection, and the use of a VPN (Virtual Private Network).
[0033] Attack target 360 stores the name of the system component (also called a "system component") that is the ultimate target of the attack within the system that is the subject of the attack. In the example of Figure 3, system components include a desktop PC, a controller, and a control server.
[0034] The purpose of the attack is stored in the attack purpose 370. In the example of Fig. 3, the purpose of the attack may be data theft, data tampering, system shutdown, etc. In addition, there may be data destruction, purpose unknown, etc. The attack technique used in each attack case is stored in the attack technique 380. In the example of Fig. 3, the attack techniques include phishing emails, command line usage, remote file copying, API (Application Programming Interface) usage, physical device connection, and abuse of remote connection services.
[0035] In FIG. 3, information is summarized for each case in the attack case information 300, but the results of statistical processing of attack cases may be added to the attack case information 300.
[0036] FIG. 4 is a diagram showing an example of offensive tactics / technique information 400 stored in the offensive tactics / technique storage unit 106. As shown in FIG.
[0037] The attack tactic / technique information 400 is information having the following items: attack tactic identification number 410 , attack tactic name 420 , attack technique identification number 430 , and attack technique name 440 . The attack tactic identification number 410 stores an attack tactic identification number for identifying the tactic of the assumed attack tactic. The attack tactic name 420 stores the name of a supposed attack tactic. In the example of Fig. 4, there are initial intrusion, execution of attack code, and transfer to other assets. An asset is, for example, each component device of the system 710 shown in Fig. 7. In addition, the attack tactic name 420 may store attack tactic names such as privilege escalation, authentication information access, information collection, and data exfiltration. An attack technique identification number for uniquely identifying an attack technique is stored in the attack technique identification number 430. In the example shown in Fig. 4, a number obtained by adding a subnumber to the attack tactic identification number is used as the attack technique identification number.
[0038] The attack technique name 440 is a technique that realizes an attack tactic. In the example shown in FIG. Phishing emails ·Connecting physical devices Command line usage Use of API (Application Programming Interface) Abuse of remote connection services Remote file copy
[0039] 5 is a diagram showing a display example of an attack scenario condition input screen 500. The attack scenario condition input screen 500 is an example of the attack scenario generation condition input unit 101.
[0040] Condition 1 and condition 2 can be input on the attack scenario condition input screen 500. In the first embodiment, two conditions are input, but the number is not limited to two. One or three or more conditions may be input. A list of input information is displayed on the attack scenario condition input screen 500, and the conditions are in an undetermined state.
[0041] For condition 1, a region is selected from a pull-down menu 510. The pull-down menu 510 selects the time period 320, industry 330, region 340, system configuration characteristics 350, attack target 360, and attack purpose 370 that are associated with the attack case information 300. In addition, the pull-down menu 520 determines detailed information about the region selected from the pull-down menu 510.
[0042] For condition 2, information is entered in the free text box 530. On the attack scenario condition input screen 500, "Industry: Electricity" is entered. In addition, the input to the free text box 530 on the attack scenario condition input screen 500 is made to correspond to the detailed information of each item, such as the time 320, industry 330, region 340, system configuration characteristics 350, attack target 360, and attack purpose 370, which are associated with the attack case information 300, by the symbol colon ":". However, the symbol is not limited to a colon, and any symbol that can indicate the relationship between multiple pieces of information, such as a semicolon ";" or a hyphen "-", may be used. In addition to the information associated with the attack case information 300, information such as laws, standards, and regulations may also be input. This information on laws, etc. can be linked to attack techniques based on the region of condition 1, the industry of condition 2, or the security measures (not shown) described in those conditions.
[0043] The attack scenario condition input screen 500 also includes an add condition button 540 for adding a condition, and a confirm condition button 550 for confirming a condition. In Fig. 5, two conditions can be input, but pressing the add condition button 540 makes it possible to input three or more conditions. After all conditions displayed on the attack scenario condition input screen 500 have been input, pressing the confirm condition button 550 confirms the input conditions.
[0044] 6 is a diagram showing an example of the configuration of an evaluation result list 400 A. The evaluation result list 400 A is configured by adding an item of evaluation 450 to the offensive tactics / technical information 400 shown in FIG. The evaluation 450 stores the evaluation result of the attack tactics by the attack technique evaluation unit 103.
[0045] In the first embodiment, the attack scenario condition input screen 500 shown in Fig. 5 generates an evaluation result list 400A for the attack scenario generation conditions where the region is set to "North America" in condition 1 and the industry is set to "electricity" in condition 2. In the first embodiment, the attack technique evaluation unit 103 focuses on the number of attack techniques 380 used in attack cases that meet condition 1 and condition 2 (case numbers 310 1, 2, and 4 in the attack case information 300 shown in Fig. 3), and stores the evaluation results of the attack techniques 380 in the evaluation 450. Here, the following evaluation results are obtained for each attack technique by the evaluation 450. Phishing emails: High (3 times) Physical device connection: None (0 times) Command line usage: Low (1 time) ·API usage: Medium (2 times) Remote connection service abuse: Low (1 time) Remote File Copy: Medium (2 times)
[0046] In the first embodiment, the attack technique evaluation unit 103 evaluates the attack techniques with the two conditions 1 and 2 being of equal value, but it is also possible to evaluate the attack techniques by placing emphasis on one of the conditions based on the condition number or condition item. In the first embodiment, the attack technique evaluation unit 103 evaluates the attack techniques by focusing on the number of attack techniques used in the attack cases that meet the conditions. However, by inputting the attack technique itself from the attack scenario generation condition input unit 101 as an attack scenario generation condition, it is also possible to improve the evaluation of the input attack technique as an attack technique that can be selected with the highest priority when the attack scenario generation unit 104 generates a scenario. In this case, the attack technique input from the attack scenario generation condition input unit 101 is more likely to be selected as an attack scenario.
[0047] Next, the scenario generating method according to the first embodiment will be described using a specific example. First, a specific example of a system configuration 700 of a system 710 that is input to the system information input unit 102 as an attack target, that is, a target for risk assessment, will be described. FIG. 7 is a diagram showing an example of the system configuration of a system 710 inputted by the system information input unit 102. As shown in FIG.
[0048] The system 710 includes as its components a desktop PC 701, a notebook PC 702, a control server 703, and a controller 704. Each system component is connected to the other components as follows. For example, the desktop PC 701 is connected to the notebook PC 702 and the control server 703 via a communication line such as a LAN (Local Area Network). The notebook PC 702 is also connected to the desktop PC 701 and the control server 703 via a communication line such as a LAN.
[0049] The control server 703 is connected to the desktop PC 701, the notebook PC 702, and the controller 704 via a communication line such as a LAN. The controller 704 is connected to the control server 703 via a communication line such as a LAN. The components of the desktop PC 701 to the controller 704 shown in Fig. 7 correspond to the component numbers "1" to "4" of 810 shown in Fig. 8, which will be described later.
[0050] The attack scenario generation device 20 may be connected to the system 710, or may be realized as one component of the system 710. When configuring the attack scenario generation device 20 as one component of the system 710, the functions of the attack scenario generation device 20 are provided to any one of the desktop PC 701, the notebook PC 702, the control server 703, or the controller 704.
[0051] FIG. 8 is a diagram showing an example of the configuration of system configuration information 800. As shown in FIG. As described with reference to FIG. 1, the system configuration information 800 is information input to the attack scenario generation device 20 from the system information input unit 102.
[0052] System configuration information 800 includes various information about each system component that constitutes the system that is the target of an attack. This system configuration information 800 is information that has the following items for each component: component number 810, device name 820, device type 830, device role 840, OS (Operating System) 850, malware countermeasures 860, user management 870, and physical access 880.
[0053] The component number 810 stores a component number that is an identifier that uniquely represents a component of the system 710 . The name of the device, that is, the name of the system component, is stored in the device name 820. In the example shown in Fig. 8, there are a notebook PC 1, a desktop PC 1, a control server 1, a controller 1, etc. In addition, the devices include a smartphone, a tablet terminal, etc.
[0054] The type of device, that is, the type of system component, is stored in the device type 830. In the example shown in Fig. 8, these are a notebook PC, a desktop PC, a server, and a controller. The role played by the device is stored in the device role 840. In the example shown in Fig. 8, the roles are data browsing, data input / editing, controller management, device control, and the like.
[0055] The type and version of the OS (basic software) installed in each system component are stored in the OS (basic software) 850. In the example shown in Fig. 8, there are OS1 ver.1, OS1 ver.2, OS3, OS4, etc.
[0056] The presence or absence of malware countermeasures for each system component is stored in the malware countermeasures 860. In the example shown in Fig. 8, if "yes" indicates that malware countermeasures have been taken for the components of the system 710, and if "no" indicates that the components of the system 710 have not been countered. For example, when antivirus software is not installed in the components of the system 710, or when antivirus software is installed but the virus definition file has not been updated to the latest file, this is referred to as "no malware countermeasures being taken."
[0057] The presence or absence of user management in each system component is stored in the user management 870. In the example shown in Fig. 8, "Yes" indicates that user management is performed, and "No" indicates that user management is not performed. Physical access 880 stores information on whether an attacker can physically access (contact) the relevant device. In the example shown in Fig. 8, it is shown that the laptop PC1 and desktop PC1 are physically accessible by an attacker, but the control server 1 and controller 1 are physically inaccessible by an attacker. For example, if the laptop PC1 and desktop PC1 are placed in an office, the attacker can physically access them. On the other hand, it is assumed that the attacker cannot physically access the control server 1 and controller 1 that are placed in an area where entry and exit are strictly controlled, such as a server room.
[0058] In this way, information indicating the countermeasure status against cyber attacks is stored in the device role 840, OS (basic software) 850, malware countermeasure 860, user management 870, and physical access 880. Therefore, as described later, the attack scenario generation unit 104 uses the information indicating the countermeasure status.
[0059] 9 is a diagram showing a display example of a system information input screen 900. The system information input screen 900 is an example of the system information input unit 102. Into the system information input screen 900, system information of the system 710 is input.
[0060] The system information input screen 900 includes a connection status input interface 910 , a device information input interface 920 , and an add device button 930 . The connection status input interface 910 is a functional unit that allows the user to input the connection status (system configuration 700) of each system component of the system 710. The system configuration 700 of the system 710 is illustrated in this connection status input interface 910. The user can input the connection status of each device from the connection status input interface 910.
[0061] The device information input interface 920 is a functional unit for a user to input system configuration information 800 of each device constituting the system 710. The device information input interface 920 has input items of device name 820, device type 830, device role 840, OS 850, malware countermeasure 860, user management 870, and physical access 880 of the system configuration information 800 by name 921, type 922, role 923, OS 924, malware countermeasure 925, user management 926, and physical access 927. A user can input necessary information from each input item. The information input to the device information input interface 920 is used as the system configuration information 800. In the first embodiment, the form of each input item is a free text box, and the user can freely input information of each device constituting the system 710. However, the form of all or some of the items of each input item of the device information input interface 920 may be a pull-down menu, and the user may select necessary information from the pull-down menu.
[0062] The add device button 930 is a functional section for adding a device constituting the system 710. When the user selects the add device button 930, a new device is added to the connection status input interface 910. Information on the added device is input from the device information input interface 920.
[0063] In the first embodiment, an example was shown in which the user inputs all of the system information from the system information input screen 900, but it is also possible to define part or all of the system information in a separate file and input the system information by reading that file. For this reason, the system information input screen 900 may be configured to have a file path input section 1410 in FIG. 14, which will be described later, and to have a file reading function. By having the file reading function, the system information input screen 900 can read files in which various variations of system information are described in a batch, thereby reducing the burden on the user compared to the case in which multiple identical or similar system information are repeatedly input.
[0064] FIG. 10 is a flowchart showing an example of a process in which the attack scenario generation unit 104 generates a scenario.
[0065] First, the attack scenario generation unit 104 reads and acquires system information including the system configuration 700 and system configuration information 800 input from the system information input unit 102 (S1). Next, the attack scenario generation unit 104 determines the system and system components that will be the targets of the attack (S2). The attack scenario generation unit 104 can determine the system components that will be the targets of the attack based on the attack scenario generation conditions input from the attack technology evaluation unit 103.
[0066] The attack scenario generation conditions according to the first embodiment correspond to attack cases 1, 2, and 4 in the attack case information 300 shown in FIG. 3. In addition, it is assumed that the region is "North America" as condition 1 and the industry is "electricity" as condition 2. In this case, since the controller is determined as the attack target, the attack scenario generation unit 104 selects the controller. However, it is also possible to set the attack target determined directly by the user as the attack scenario generation condition.
[0067] Next, the attack scenario generation unit 104 generates an attack path, which is an intrusion route of a cyber attack that can reach the attack target (S3). An "attack path" represents the execution order of attack techniques against the attack elements 1130, which are executed from top to bottom for each scenario shown in Fig. 11, which will be described later.
[0068] Next, the attack scenario generation unit 104 reads the evaluation results of the attack techniques evaluated by the attack technique evaluation unit 103 (S4). The evaluation results of the attack techniques are information stored in the evaluation 450 in the evaluation result list 400A shown in FIG. 6 described above.
[0069] Next, the attack scenario generation unit 104 judges whether an attack technique against each device on the attack path is successful or not by using the device role 840, OS (basic software) 850, malware countermeasure 860, user management 870, and physical access 880 of the system information input unit 102 (S5). Here, it is judged whether an attack against a certain device by a certain attack technique is successful or not.
[0070] Finally, the attack scenario generation unit 104 determines a combination of attack techniques using the judgment result and the evaluation result from the attack technique evaluation unit 103 (S6), and generates an attack scenario. If appropriate conditions are specified before the attack scenario generation unit 104 generates a scenario, the attack scenario generation unit 104 can generate an appropriate scenario that allows the user to consider how to deal with attacks on devices.
[0071] The cyber-attack scenario generation method performed by the attack scenario generation device 20 according to this embodiment can be executed by a computer program for causing a computer to execute the method.
[0072] FIG. 11 is a diagram showing an example of an attack scenario list 1100. The attack scenario list 1100 is generated by the attack scenario generation unit 104 and output from the attack scenario output unit 107 .
[0073] This attack scenario list 1100 includes a plurality of attack scenarios, each of which has the controller 1 as an attack target, and is created based on the evaluation result list 400A (see FIG. 6), the system configuration 700, and the system configuration information 800. This attack scenario list 1100 is provided with a scenario number 1110, an order 1120, attack elements 1130, and attack techniques 1140. The order 1120 is associated with the scenario number 1110, and the attack elements 1130 and attack techniques 1140 are associated with the order 1120.
[0074] The scenario number 1110 stores a scenario number for identifying a scenario generated by the attack scenario generation unit 104. In the first embodiment, the scenario numbers are alphabetical characters such as "A", "B", ..., but the scenario numbers may also be a combination of alphanumeric characters, etc.
[0075] In the order 1120, numbers such as "1", "2", ... are stored for each attack element in the scenario number from the top. This indicates that the attack techniques generated in a certain scenario are executed in numerical order from the top. The names of the attack elements defined in the scenarios are stored in the attack elements 1130. The attack elements are system components that exist in the attack path through which the attack on the system passes in each scenario. At the end of the order 1120 of each scenario, "Controller 1" selected as the target of attack is stored. The attack technique 1140 stores an attack technique identification number defined in the attack tactic / technique information 400 in Fig. 4. The attack technique identified by the attack technique identification number is executed in each system component.
[0076] According to the attack scenario list 1100, for example, in the case of scenario number "A", sequence "1", and attack element "control server 1", it can be seen that the attack techniques included in the attack scenario are "1-1 phishing email, 2-4 utilization of API, 3-6 remote file copy". Note that scenario numbers "D" and "E" have the same attack element 1130. However, since the sequence 1120 is different, they are created as different attack scenarios. Here, in FIG. 7, the controller 704 is not directly connected to the LAN, but there are also cases where an attack starts from an email accumulated by the control server 703. For this reason, a scenario in which "control server 1 (control server 703)" is attacked and then "controller 1 (controller 704)" is attacked, as shown in scenario number "A", is also assumed.
[0077] In the first embodiment, when the attack scenario generation unit 104 generates an attack path, it does not generate a path that passes through the same system component within a single scenario. In other words, even if a single system has multiple identical system components configured, a scenario does not have a path set that simultaneously attacks multiple identical system components. However, a scenario may have a path set that simultaneously attacks multiple identical system components.
[0078] The attack technique for each system component is selected based on the attack tactics / technical information 400 in Fig. 4. For example, the attack technique of the attack tactic "initial intrusion, execution of attack code, movement to other assets" is selected for the first system component in each scenario. Also, the attack technique of the attack tactic "execution of attack code" is selected for the system component that is the target of the attack (for example, controller 1). Also, in other attack scenarios, the attack technique of the attack tactic "execution of attack code, movement to other assets" is selected one by one for the system components in the middle of the attack scenario. However, it is also possible to output a scenario with multiple attack techniques.
[0079] For example, the attack technique against the control server 1 in the scenario A is assigned an attack tactic with a high rating among the items of the rating 450 stored in the evaluation result list 400A. However, the attack on laptop PC1 in scenario B is assigned 2-3 "Using command line" which is rated "low" instead of 2-4 "Using API" which is rated "medium" as indicated by attack technique identification number 430. The reason why such an attack technique with a low rating is assigned is because laptop PC1 is "enabled" in the malware countermeasures 860 item of system configuration information 800 shown in Fig. 8. In other words, because malware countermeasures have been implemented for laptop PC1, it is determined in step S5 of Fig. 10 that the attack technique 2-4 "Using API" cannot be executed, and 2-3 "Using command line" which is an attack technique that an attacker can execute is set.
[0080] FIG. 12 is a diagram showing an example of a scenario output screen 1200. As shown in FIG. The scenario output screen 1200 is an example of the attack scenario output unit 107.
[0081] The attack scenario output unit 107 outputs a scenario output screen 1200 to the display devices of the terminal devices 26-1 and 26-2 shown in Fig. 2. The user can check the attack scenario through the scenario output screen 1200.
[0082] The scenario output screen 1200 includes a table 1201. The table 1201 includes a scenario number 1210, a sequence 1220, an attack element 1230, and an attack technique 1240. Each item included in the table 1201 displays the contents of "A" to "C" of the scenario number 1110 in the attack scenario list 1100 shown in FIG.
[0083] The scenario output screen 1200 also includes a scenario number display area 1250 , an attack scenario regeneration button 1260 , a sorting button 1270 , a display range switching button 1280 , and a file output button 1290 . The scenario number display area 1250 displays the total number of attack scenarios generated by the attack scenario generation unit 104. The number of scenarios A to E in FIG. 11, “5”, is counted as the total number of scenarios and is displayed in the scenario number display area 1250.
[0084] The regenerate attack scenario button 1260 is a button that allows the user to instruct the attack scenario generation device 20 to re-create the attack scenario. When the user selects the regenerate attack scenario button 1260, the screen transitions to an attack scenario condition input screen 500 (see FIG. 5) or a system information input screen 900 (see FIG. 9). The user can then input various information, allowing the attack scenario generation device 20 to generate a scenario again.
[0085] The sort button 1270 is a button for the user to instruct sorting of the attack scenarios displayed in the table 1201 . The display range switching button 1280 is a button for allowing the user to adjust the switching of the display range of the attack scenarios displayed in the table 1201 . The file output button 1290 is a button for the user to instruct to output the table 1201 as a file.
[0086] 12, the scenario numbers are sorted in ascending order, and the display range is output as scenarios with 3 or less attack elements. Note that the scenarios may be sorted not only by scenario number 1210, but also by a criterion that prioritizes display of system components or attack techniques 1240 that appear for the first time in a scenario and are included in attack elements 1230. It is also possible to switch the display range depending on the number of scenario numbers 1210 and the type of attack technique 1240.
[0087] In the attack scenario generation system 1 according to the first embodiment described above, a user can arbitrarily change the configuration of a system to be attacked, and can input various information that can identify an attack technique as a generation condition for an attack scenario. Here, the attack scenario generation device 20 can generate an attack scenario including an attack technique that is likely to be used in a cyber attack by preferentially incorporating highly evaluated attack techniques into the attack scenario based on past case information. This allows the attack scenario generation device 20 to generate flexible and diverse attack scenarios with high accuracy, not limited to past attack cases. Furthermore, when considering attack countermeasures, a user can list and consider multiple countermeasures.
[0088] In addition, since the user inputs system information of the actual system 710, attack scenarios are generated that are in line with the actual system configuration. Then, the user can consider countermeasures against attack techniques that are likely to be executed by attackers. In this way, in the past, attack techniques were not evaluated, and a huge number of scenarios were generated, but in this embodiment, scenarios are generated without excess or deficiency of attack techniques based on feasible attacks, so the user can select an appropriate number of scenarios, and specific countermeasures against attack techniques become possible.
[0089] Furthermore, the attack scenario generation system 1 can generate attack scenarios with variations intended by the user by inputting required conditions. The user can select the intended number of attack scenarios from the multiple attack scenarios generated by the attack scenario generation system 1, or extract attack scenarios for which the user wants to focus on countermeasures.
[0090] In this way, the attack scenario generation system 1 can generate attack scenarios that can be used to plan meaningful countermeasures, and therefore can provide a client with a software program that plans scenario-based security countermeasures, enabling specific security countermeasures for the client's system. Therefore, a user can use the attack scenario generation system 1 in various services, such as a security consultancy business or cyber defense training service, to implement countermeasures tailored to the client's system and provide advice to the client.
[0091] [Second embodiment] Hereinafter, a configuration example of an attack scenario generation system according to the second embodiment of the present invention will be described with reference to FIGS. The combination of attacking techniques in cyber attacks is constantly evolving, and a method for generating attack scenarios that can respond to the latest trends is required. Therefore, a method for generating attack scenarios according to a second embodiment will be described, in which a function for inputting new attack case information (referred to as "new case information"), analyzing the input new case information, and storing the analysis results is added to the method described in the first embodiment.
[0092] FIG. 13 is a functional block diagram showing an example of a functional configuration of an attack scenario generation system 1A according to the second embodiment. The attack scenario generation system 1A according to the second embodiment is configured by adding a case information input unit 1301 to the attack scenario generation system 1 according to the first embodiment. The attack scenario generation device 20 according to the second embodiment is configured by adding a case information analysis unit 1302 and an analysis result checking and editing unit 1303.
[0093] The case information input unit 1301 inputs new case information to the case information analysis unit 1302. The new case information is input via a case information input screen 1400 shown in Fig. 14, which will be described later.
[0094] The case information analysis unit 1302 analyzes information on new attack cases input from the case information input unit 1301. Here, the case information analysis unit 1302 performs, for example, text mining or statistical processing on the input new case information. Then, the case information analysis unit 1302 reads out the attack tactics / technique information 400 from the attack tactics / technique storage unit 106, and associates the attack tactics and attack techniques with the input case information based on the analysis results.
[0095] The analysis result checking and editing unit 1303 outputs the analysis results of the information on new attack cases so that they can be confirmed, accepts editing of the analysis results, and stores the confirmed and edited analysis results and information on new attack cases in the attack case storage unit 105. Here, the analysis result checking and editing unit 1303 checks and edits the analysis results through a checking and editing screen 1500 shown in Fig. 15, which will be described later. Thereafter, the attack technique evaluation unit 103 refers to the attack example storage unit 105, reads out the attack examples, and evaluates the attack techniques.
[0096] 14 is a diagram showing a display example of a case information input screen 1400. The case information input screen 1400 is an example of the case information input section 1301.
[0097] Case information input screen 1400 has a file path input section 1410 and a URL input section 1430, and can accept input of a file path or URL. Inputting a file path is a function for specifying a file in a computer. A user can specify a file path by inputting a file path in a computer into file path input section 1410. A user can also click browse button 1420 and input a file path into file path input section 1410 using a file browser or the like. When a file path is input into case information input section 1301, case information analysis section 1302 retrieves a file, etc. from the input file path.
[0098] The case information input screen 1400 shows an example in which a PDF (Portable Document Format) file in which new case information is described has been input. However, the input file is not limited to a PDF file. For example, an electronic document that holds new case information, such as a document file or a text file created by word processing software, may be input.
[0099] As described above, the case information input screen 1400 can accept URL input. URL input is a function that allows a user to input the URL of a web page holding new case information or a file published on the Internet, etc., into the URL input section 1430. When a URL is input into the case information input section 1301, the case information analysis section 1302 acquires a file, etc., from the input URL.
[0100] When information has been input in the file path input section 1410 or URL input section 1430, the user clicks on the input decision button 1440, whereby the case information to be input by the case information input section 1301 is decided.
[0101] After the case information is determined, the case information analysis unit 1302 acquires and analyzes the case information input from the case information input unit 1301. The case information may be analyzed, for example, by creating in advance a list of keywords to be extracted from attack cases and matching those keywords. Furthermore, machine learning, deep learning, AI (Artificial Intelligence), or the like may be used to analyze the case information.
[0102] 15 is a diagram showing a display example of a checking and editing screen 1500. The checking and editing screen 1500 is an example of the analysis result checking and editing section 1303. The checking and editing screen 1500 displays various information related to cyber-attack cases as the analysis results of new case information by the case information analysis unit 1302.
[0103] The confirming and editing screen 1500 has information associating time 1510, business type 1520, region 1530, system configuration characteristics 1540, attack target 1550, attack purpose 1560, and attack technique 1570. This information corresponds to the information stored in time 320 to attack technique 380 of the attack example information 300 shown in FIG.
[0104] However, depending on the analysis results of the case information, the information is not limited to that included in the confirmation and editing screen 1500. Also, each item on the confirmation and editing screen 1500 can be edited. For example, the user can edit the industry 1520 by rewriting it from "electricity" to other information such as "railroad" or "automobile manufacturing."
[0105] Depending on the analysis results, there may be items with no information or items with multiple pieces of information. Even in such cases, the user can confirm the information through the confirmation and editing screen 1500 and add or delete information. When the user has finished confirming and editing the information for each item, he or she clicks the confirmation button 1580 to confirm the information. When the confirmation button 1580 is clicked, the analysis result confirmation and editing unit 1303 stores the confirmed information in the attack example storage unit 105.
[0106] 16 is a diagram showing an example of the attack case information 300 to which new case information has been added. As described above, the attack case information 300 is stored in the attack case storage unit 105. In the attack case information 300 shown in Fig. 16, new case information confirmed and edited by the analysis result checking and editing unit 1303 is added below the attack case information 300 shown in Fig. 3. Here, the information with case number "5" is highlighted as the newly added case information.
[0107] After that, the attack scenario generation device 20 according to the second embodiment evaluates attack techniques and generates and outputs attack scenarios using the attack case information 300 to which the new case information has been added. These processes are the same as those in the first embodiment.
[0108] In the attack scenario generation system 1 according to the second embodiment described above, the case information analysis unit 1302 analyzes new case information input from the case information input unit 1301. Then, the attack case information confirmed and edited by the analysis result checking and editing unit 1303 is added to the attack case information 300. Then, the attack scenario generation device 20 can generate an attack scenario corresponding to the latest trends using the added attack case information. Therefore, an attack scenario reflecting the latest attack cases is generated.
[0109] [Third embodiment] Next, a configuration example of an attack scenario generation system according to a third embodiment of the present invention will be described with reference to FIGS.
[0110] In the first and second embodiments, a method for generating an attack scenario has been described. In these embodiments, it is also possible to consider and output security countermeasures (hereinafter abbreviated as "countermeasures") against attack techniques based on the generated attack scenario at the same time as generating the attack scenario. Therefore, in order to automate part of the countermeasure consideration and improve the efficiency of the countermeasures, in the third embodiment, an attack scenario generation system will be described that adds a function of outputting the countermeasure contents at the same time as outputting the attack scenario.
[0111] FIG. 17 is a functional block diagram showing an example of a functional configuration of an attack scenario generation system 1B according to the third embodiment. The attack scenario generation system 1B according to the third embodiment is configured by adding a countermeasure content storage unit 1701 to the attack scenario generation system 1 according to the first embodiment. The attack scenario generation device 20 is configured by adding a countermeasure examination unit 1702 and a recommended countermeasure output unit 1703.
[0112] The countermeasure content storage unit 1701 stores countermeasure content information 1800 shown in FIG. 18, which will be described later, as countermeasure content against attacking techniques.
[0113] The countermeasure review unit 1702 reviews countermeasure contents against the attack technique included in the attack scenario by referring to the countermeasure content storage unit 1701. For example, the countermeasure review unit 1702 reviews countermeasure contents against the cyber attack based on the attack tactic / technique information 400 (see FIG. 4) of the cyber attack read from the attack tactic / technique storage unit 106, the countermeasure content information 1800 (see FIG. 18) read from the countermeasure content storage unit 1701, and the attack scenario generated by the attack scenario generation unit 104.
[0114] The recommended countermeasure output unit 1703 outputs the result of the countermeasure content consideration by the countermeasure consideration unit 1702 as a recommended countermeasure based on the components of the system 710 and the effects of the countermeasure content. Therefore, the user can obtain effective recommended countermeasures.
[0115] 18 is a diagram showing an example of the measure content information 1800. The measure content information 1800 is stored in the measure content storage unit 1701. The countermeasure content information 1800 is information having the items of a countermeasure identification number 1810 and a countermeasure name 1820 .
[0116] 18, the following information is stored as the name of the measure in the measure name 1820. Then, the measure identification number for identifying each measure is stored in the measure identification number 1810. - Introduction of email censorship -Block unnecessary ports -Disable unnecessary functions - Application control implementation Multi-factor authentication ·Communication monitoring Anti-malware ·User management
[0117] The countermeasure examining unit 1702 uses the attack tactics / technique information 400 and the countermeasure content information 1800 to associate the attack techniques with the countermeasure names, and obtains the association results shown in FIG.
[0118] FIG. 19 is a diagram showing an example of a correspondence 1900 between attack techniques and countermeasures. The correspondence relationship between the attack technique and the countermeasure that can prevent the attack technique is defined in the correspondence relationship 1900. The correspondence relationship 1900 is stored in the countermeasure content storage unit 1701.
[0119] The correspondence 1900 is information having items of attack technique name 1910 and countermeasure name 1920. For example, for an attack of "phishing email" stored in the attack technique name 1910, "introduction of email censorship" stored in the countermeasure name 1920 is listed as a countermeasure. Then, the countermeasure consideration unit 1702 automatically considers countermeasures using the correspondence 1900 and the attack scenarios in the attack scenario list 1100 generated by the attack scenario generation unit 104.
[0120] 20 is a diagram showing a display example of a countermeasure screen 2000. The countermeasure screen 2000 is an example of the recommended countermeasure output section 1703.
[0121] The countermeasure screen 2000 includes a table 2001. The table 2001 includes items such as countermeasure 2010 and name of relevant device 2020. The countermeasures 2010 include the countermeasures considered by the countermeasures consideration section 1702 (also called “recommended countermeasures”). The name of the relevant device 2020 includes the name of the device that is a system component for which the countermeasure is implemented. The contents of table 2001 are shown as an example in which the devices are rearranged in descending order of the number of applicable devices, and the display range is switched to measures for two or more applicable devices. For example, when the attack technique is "API usage", "implementation of application control" is displayed in measure 2010 based on the correspondence relationship 1900 shown in FIG.
[0122] The countermeasure screen 2000 also includes a scenario display section 2002 , a sort button 2030 , a display range switching button 2040 , and a file output button 2050 . The scenario display section 2002 displays the scenario number of the scenario that is the target of countermeasure consideration. In the example of Fig. 20, "Scenario E" shown in Fig. 11 is displayed in the scenario display section 2002 as the target scenario.
[0123] The sort button 2030 is a button for the user to instruct sorting of the measures and the corresponding device names displayed in the table 2001. The display range switching button 2040 is a button for the user to adjust the switching of the display range of the measures and the corresponding device names displayed in the table 2001. The file output button 2050 is a button for the user to instruct to output the table 2001 as a file.
[0124] In the attack scenario generation system 1B according to the third embodiment described above, the countermeasures for attack techniques are automatically considered from the attack scenario by the countermeasures consideration unit 1702, and recommended countermeasures are output from the recommended countermeasures output unit 1703. This allows the user to study countermeasures more efficiently.
[0125] [Variations] In the attack scenario generation system 1B, countermeasures are considered for a single scenario, but it is also possible to perform statistical processing, etc. for all attack scenarios generated by the attack scenario generation unit 104, consider countermeasures, and output recommended countermeasures.
[0126] Also, with regard to table 2001 displayed on countermeasure screen 2000, it is possible to display each scenario and recommended countermeasures for preventing attacks on the corresponding device in a list form.
[0127] Furthermore, the configurations of the attack scenario generation device 20 according to the first to third embodiments described above may be combined. For example, the attack scenario generation device 20 shown in Fig. 17 may be combined with the case information input unit 1301 for adding new case information to the attack case storage unit 105, the case information analysis unit 1302, and the analysis result checking and editing unit 1303 shown in Fig. 13. With this configuration, countermeasures against attack techniques are automatically considered based on the attack scenario generated including the new case information added to the attack case storage unit 105, and recommended countermeasures are output from the recommended countermeasure output unit 1703.
[0128] In addition, the system may have a function for inputting system information on the status of security measures before and after the change, and comparing the number and contents of generated scenarios. This function assists the user in examining measures, allowing the user to easily find highly effective measures.
[0129] This concludes the description of the embodiments of the present invention. The present invention is not limited to the above-mentioned embodiments, and of course, various other applications and modifications can be made without departing from the gist of the present invention described in the claims. The above-mentioned embodiments are detailed and specific descriptions of the configuration of the device and system in order to easily explain the present invention. Therefore, for example, the contents of the information stored in each storage unit, the process of assigning component risk evaluation points for each component, the results of extracting attack scenarios, the evaluation results, etc. are not necessarily limited to all of the configurations, processes, information, and numerical values described here. In addition, it is possible to replace a part of the configuration of the embodiment described here with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of a certain embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.
[0130] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them as an integrated circuit. In addition, each of the above configurations, functions, etc. may be realized in software by interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be stored in a memory 22, a recording device such as a hard disk or SSD (Solid State Drive), or a storage device such as an IC card, SD card, or DVD. In addition, the control lines and information lines in the figure show those that are considered necessary for explanation, and do not necessarily show all control lines and information lines in the product. In reality, it may be considered that almost all of the configurations are connected to each other. [Explanation of symbols]
[0131] 1...attack scenario generation system, 20...attack scenario generation device, 21...processing unit, 26-1, 26-2...terminal device, 101...attack scenario generation condition input unit, 102...system information input unit, 103...attack technology evaluation unit, 104...attack scenario generation unit, 105...attack case storage unit, 106...attack tactics / technology storage unit, 107...attack scenario output unit, 300...attack case information, 400...attack tactics / technology information, 500...attack scenario condition input screen, 700...system configuration, 710...system, 800...system configuration information
Claims
1. an attack technique evaluation unit that acquires generation conditions including at least region, industry, and attack technique as generation conditions for an attack scenario simulating the behavior of a cyber-attack, information on attack cases of the cyber-attacks, attack tactics that define the behavior by which the cyber-attacks are executed, and the attack techniques that realize the attack tactics, and evaluates the attack techniques for each attack case that meets the generation conditions of the attack scenario by referring to an attack case storage unit in which the attack cases are stored, and an attack tactics and attack technique storage unit in which specific attack techniques that can realize the attack tactics indicating the behavior by which the cyber-attacks are executed are stored together with the attack tactics; an attack scenario generation unit that generates an attack path that specifies an attack order for the components of the computer system based on at least one of system information of the computer system including the target of the cyber attack and security measure information for the components of the computer system and the evaluation result of the attack technique, and generates at least one or more attack scenarios for the computer system, which are made up of combinations of the attack techniques for each component and include at least one or more of the attack techniques, based on the evaluation result of the attack techniques, including an attack technique that has been input as a generation condition and has a higher evaluation than other attack techniques, and generates the attack scenario for the region and industry in which the computer system that is the target of the attack is located; an attack scenario output unit that outputs the attack scenario according to the evaluation result of the attack technique. Attack scenario generator.
2. The attack scenario generation unit generates the scenario including the attack technique that is capable of executing the cyber attack against the component even if the attack technique has a lower evaluation than other attack techniques. The attack scenario generation device according to claim 1 .
3. a case information analysis unit that analyzes information on new attack cases input from the case information input unit; an analysis result confirming and editing unit that outputs an analysis result of the information of the new attack case in a confirmable manner, accepts edits to the analysis result, and stores the confirmed and edited analysis result and the information of the new attack case in the attack case storage unit. The attack scenario generation device according to claim 2 .
4. a countermeasure review unit that reviews countermeasure contents against the attack technique included in the attack scenario by referring to a countermeasure content storage unit that stores countermeasure contents against the attack technique. The attack scenario generation device according to any one of claims 1 to 3.
5. and a recommended countermeasure output unit that outputs a result of the countermeasure content review by the countermeasure review unit as a recommended countermeasure based on the components of the computer system and the effects of the countermeasure content. The attack scenario generation device according to claim 4.
6. a process of acquiring generation conditions including at least region, industry, and attack technique as generation conditions for an attack scenario simulating the behavior of a cyber-attack, information on attack cases of the cyber-attack, attack tactics that define the behavior by which the cyber-attack is executed, and the attack technique that realizes the attack tactics, and evaluating the attack technique of the cyber-attack for each of the attack cases that meet the generation conditions of the attack scenario by referring to an attack case storage unit in which the attack cases are stored and an attack tactics and attack technique storage unit in which the specific attack techniques that can realize the attack tactics that indicate the behavior by which the cyber-attack is executed are stored together with the attack tactics; a process of generating an attack path that specifies an attack order for the components of the computer system based on at least one of system information of the computer system including the target of the cyber attack and security measure information of the components of the computer system and the evaluation result of the attack technology, and generating at least one or more attack scenarios for the computer system, which are made up of combinations of the attack technologies for each component and include at least one or more of the attack technologies based on the evaluation result of the attack technology, including an attack technology that has been input as a generation condition and has a higher evaluation than other attack technologies, for the region and industry in which the computer system to be attacked is located; and outputting the attack scenario according to the evaluation result of the attack technique. Method for generating attack scenarios.
Citation Information
Patent Citations
Program, method, and device for assisting cyberattack analysis
JP2018032354A
Cyber threat evaluation apparatus, cyber threat evaluation program and cyber threat evaluation method
JP2019125267A
Anticipatory cyber defense
JP2019145091A
Risk assessment measure planning system and risk assessment measure planning method
JP2020166650A
Incident scenario generation device and incident scenario generation system
JP2021005165A
