Security analysis system, security analysis method, and security analysis program
The security analysis system addresses computational inefficiencies in generating attack scenarios by reusing and efficiently combining attack activity information, ensuring comprehensive coverage and reduced costs in complex IT/OT systems.
Patent Information
- Application Number
- JP2023081134
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-16
- Publication Date
- 2024-11-28
AI Technical Summary
Existing security analysis techniques face computational inefficiencies due to combinatorial explosions in generating attack scenarios, particularly in complex IT/OT systems, leading to reduced comprehensiveness and low reusability of cached scenarios.
A security analysis system that efficiently reuses stored attack activity information by determining identity and combining applicable activities to generate scenarios, utilizing a rule-based system and a hierarchical attack activity database for improved searchability and reusability.
Enables efficient generation of attack scenarios with high reusability and reduced computational cost, ensuring comprehensive coverage of attack scenarios in complex systems.
Smart Images

Figure 2024165201000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a technique for generating attack scenarios. [Background technology]
[0002] By incorporating measures against security threats at the early stages of development, it is possible to improve safety and reduce development costs. Therefore, when building a secure IT / OT system, it is desirable to conduct security analysis at the planning and design stages. This approach is called security by design. IT is an abbreviation for Information Technology. OT is an abbreviation for Operational Technology.
[0003] There are various methods for security analysis, one of which is scenario-based analysis. Scenario-based analysis is a method for deriving attack scenarios for threats that may affect business. Attack scenarios show the process of a cyber attack that creates a threat. The effect of attack scenarios is that they make it possible to consider countermeasures for all attack activities leading up to a threat. For this reason, scenario-based analysis is superior to other methods in considering countermeasures in more detail.
[0004] Patent Document 1 proposes a technology that can efficiently identify threats and attack methods against a system being designed. In this technology, various templates related to components, assets, threats, and attack methods are prepared, and attack scenarios are efficiently derived by using or reusing (caching) the templates from the system definition to the identification of threats and attack methods. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2009-070084 A Summary of the Invention [Problem to be solved by the invention]
[0006] Many techniques and tools for generating attack scenarios have been proposed, but most of them have problems with computation time due to combinatorial explosion. The reason for this is due to comprehensiveness, which is one of the requirements for security analysis. Comprehensiveness means not missing any possible attack scenarios during analysis. Analysis that ensures comprehensiveness has a very high computational cost.
[0007] Real-world IT / OT systems are made up of complex networks. Therefore, to ensure comprehensiveness, it is necessary to calculate attack scenarios for all possible intrusion routes in the configuration. Even in a small network, a combinatorial explosion of routes occurs in graph theory. Furthermore, if attack patterns are considered for routes that have combinatorial explosion, even further combinatorial explosion occurs.
[0008] Conventional techniques attempt to reduce the amount of calculations by the following approaches, but each approach has its own issues. (1) By pruning intrusion vectors, the threats and attack patterns analyzed are narrowed down. However, this approach reduces comprehensiveness. (2) Caching the generated attack scenarios for reuse (see Patent Document 1). However, the patterns of the generated attack scenarios are diverse, and simple caching has low reusability.
[0009] The present disclosure aims to improve the efficiency of reusability of stored attack activity information so that attack scenarios can be generated. [Means for solving the problem]
[0010] The security analysis system of the present disclosure generates attack scenarios. The intrusion path information includes attack target information for each of one or more attack targets. The relevant method information is attack method information on an attack method for attacking the attack target. The relevant technique is the attack technique in the relevant technique information. A similar target is an attack target whose characteristics match those of the attack target in the attack target information. The relevant activity information is attack activity information on an attack activity against the same target using the relevant method. The application activity information is attack activity information on the attack activity against the attack target using the corresponding technique. The security analysis system includes: an identity determination unit that determines whether the corresponding activity information is registered in an attack activity database in which attack activity information of each of a plurality of attack activities is registered for each of the attack target information; an attack activity extraction unit that generates the application activity information using the corresponding activity information when the corresponding activity information is registered for each of the attack target information, and generates the application activity information using the attack target information and the corresponding technique information when the corresponding activity information is not registered; and an attack activity combination unit that combines the generated application activity information to generate the attack scenario. Effect of the Invention
[0011] According to the present disclosure, it is possible to efficiently reuse stored attack activity information and generate attack scenarios. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a configuration diagram of a security analysis system 100 according to a first embodiment. [Diagram 2] FIG. 2 is a configuration diagram of a threat identification unit 120 according to the first embodiment. [Diagram 3] FIG. 2 is a configuration diagram of an attack scenario generation unit 130 according to the first embodiment. [Figure 4] FIG. 1 is a functional configuration diagram of a security analysis system 100 according to a first embodiment. [Diagram 5] FIG. 1 is a schematic diagram of a security analysis method according to a first embodiment. [Figure 6] FIG. 2 is a diagram showing a processing procedure of the rule-based system in the first embodiment. [Figure 7] FIG. 2 is a diagram showing a mechanism for generating an attack scenario in the first embodiment. [Figure 8] 3 is a flowchart of a security analysis method according to the first embodiment. [Figure 9] 11 is a flowchart of step S120 in the first embodiment. [Figure 10] FIG. 1 shows an example of a threat database 191 according to the first embodiment. [Figure 11] 11 is a flowchart of step S130 in the first embodiment. [Figure 12] FIG. 13 shows an example of an attack method database 192 according to the first embodiment. [Figure 13] 4 is a flowchart of step S200 in the first embodiment. [Figure 14] FIG. 4 is a diagram showing a procedure of identity determination in the first embodiment. [Figure 15] FIG. 13 is a diagram showing an example of the configuration of an attack activity database 193 in the first embodiment. [Figure 16] FIG. 13 is a diagram showing abstraction of attack activity information in the first embodiment. [Figure 17] FIG. 13 is a diagram showing an overview of a second embodiment. [Figure 18] FIG. 11 is a configuration diagram of a security analysis system 100 according to a second embodiment. [Figure 19] FIG. 13 is a diagram showing an example of the configuration of an attack activity database 193 in the third embodiment. [Figure 20] 13 is a flowchart of step S200 in the third embodiment. [Figure 21] FIG. 13 is a diagram showing an example of identity determination in the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] In the embodiments and drawings, the same or corresponding elements are denoted by the same reference numerals. Descriptions of elements denoted by the same reference numerals as those of the elements described above will be omitted or simplified as appropriate. Arrows in the drawings mainly indicate data flow or processing flow.
[0014] Embodiment 1 The security analysis system 100 will be described with reference to FIGS.
[0015] ***Configuration Description***
[0016] The configuration of a security analysis system 100 will be described with reference to FIG. The security analysis system 100 is a computer that includes hardware such as a processor 101, a memory 102, an auxiliary storage device 103, and an input / output interface 104. These pieces of hardware are connected to each other via signal lines. The computer may be a desktop type or a notebook type.
[0017] The processor 101 is an IC that performs arithmetic processing and controls other hardware. For example, the processor 101 is a CPU or a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. GPU is an abbreviation for Graphics Processing Unit.
[0018] The memory 102 is a volatile or non-volatile storage device. The memory 102 is also called a primary storage device or a main memory. For example, the memory 102 is a RAM. Data stored in the memory 102 is saved in the secondary storage device 103 as necessary. RAM is an abbreviation for Random Access Memory.
[0019] The auxiliary storage device 103 is a non-volatile storage device. For example, the auxiliary storage device 103 is a ROM, a HDD, a flash memory, or a combination of these. Data stored in the auxiliary storage device 103 is loaded into the memory 102 as needed. ROM is an abbreviation for Read Only Memory. HDD is an abbreviation for Hard Disk Drive.
[0020] The input / output interface 104 is a port to which an input device and an output device are connected. For example, the input / output interface 104 is a USB terminal, the input device is a keyboard and a mouse (or a trackpad, etc.), and the output device is a display (monitor). Input and output of the security analysis system 100 is performed using the input / output interface 104. A touch panel may be connected to the input / output interface 104 instead of the keyboard, mouse, and display. USB is an abbreviation for Universal Serial Bus.
[0021] The security analysis system 100 comprises components such as a reception unit 110, a threat identification unit 120, an attack scenario generation unit 130, and an output unit 140. These components are realized by software.
[0022] The auxiliary storage device 103 stores a security analysis program for causing a computer to function as a reception unit 110, a threat identification unit 120, an attack scenario generation unit 130, and an output unit 140. The security analysis program is loaded into the memory 102 and executed by the processor 101. An OS is also stored in the auxiliary storage device 103. At least a part of the OS is loaded into the memory 102 and executed by the processor 101. There is no restriction on the type of OS. The processor 101 executes a security analysis program while executing the OS. OS is an abbreviation for Operating System.
[0023] The input and output data of the security analysis program are stored in the storage unit 190 . The auxiliary storage device 103 functions as the storage unit 190. However, a storage device such as the memory 102, a register in the processor 101, or a cache memory in the processor 101 may function as the storage unit 190 instead of the auxiliary storage device 103 or together with the auxiliary storage device 103.
[0024] The security analysis system 100 may include multiple processors replacing the processor 101 .
[0025] The security analysis program can be recorded (stored) in a computer-readable manner on a non-volatile recording medium such as an optical disk or a flash memory.
[0026] The configuration of the threat identification unit 120 will be described with reference to FIG. The threat identification unit 120 includes elements such as an information acquisition unit 121 , a final goal extraction unit 122 , and a threat extraction unit 123 .
[0027] The configuration of the attack scenario generation unit 130 will be described with reference to FIG. The attack scenario generation unit 130 includes elements such as an initial target extraction unit 131, an intrusion route extraction unit 132, an identity determination unit 133, an attack activity extraction unit 134, and an attack activity combination unit 135.
[0028] 4 shows a functional configuration diagram of the security analysis system 100. DB stands for database. The threat database 191, the attack method database 192, and the attack activity database 193 are stored in the storage unit 190, for example.
[0029] ***Explanation of Operation*** The operation procedure of security analysis system 100 corresponds to a security analysis method, and also corresponds to a processing procedure by a security analysis program.
[0030] An overview of the security analysis method according to the first embodiment will be described with reference to FIG. FIG. 5 shows an example of an attack scenario generated by the security analysis system 100 and a conceptual diagram of the attack scenario.
[0031] The security analysis method in the first embodiment relates to a scenario-based security analysis. Scenario-based security analysis is a method for identifying the process by which a threat (attack scenario) occurs, for a threat that is assumed to be the subject of security analysis. A threat is an undesirable state or event for a target system, and is the ultimate goal of an attacker. A threat is specified by the target of attack, the threat type, and information assets. An attack scenario is a time-series of attack activities to achieve a security threat. Attack activities are specified by attack method and attack target. The attack target can be a device, a communication path, or an information asset.
[0032] The security analysis system 100 has the functionality of a rule-based system. A rule-based system is an analysis system that infers threats, attack activities, and attack scenarios according to pre-prepared rules.
[0033] Explain a rule-based system. A rule-based system has elements such as fact information, rule information, and question information. Each element includes a predicate and an argument, and is expressed in the form of predicate (argument 1, argument 2, ...). Below are examples of fact, rule, and question information. Arguments (X) beginning with a capital letter represent variables, and constants written in lower case (e.g., "socrates") are entered into the arguments (X). An example of factual information is “human(socrates).” This indicates the fact that Socrates is a human being. An example of rule information is "die(X):-human(X)." This indicates the rule that if X, then human will die. An example of question information is “?-die(socrates).” This indicates the question, “Is Socrates mortal?”
[0034] The factual and rule information is predefined. A rule-based system, when given a query, returns a solution to the query. For example, prolog is used. The procedure for returning a solution to a query will be described with reference to FIG. (1) The question “?-die(socrates).” is given. (2) Rule information having the same predicate as the predicate "die" of the query information is searched for. (3) The question constant “socrates” is assigned to the rule information variable (X). (4) Factual information that is the same as the element "human(socrates)." of the rule information after substitution is searched for. If the corresponding factual information exists, a solution indicating that the query information is true is returned.
[0035] Below are examples of questions, rules, and facts for a security analysis. The questions in the security analysis indicate security threats. Examples of the questions are as follows: “informationTampering(pc1,plan22).” This question information indicates a threat of tampering with the file plan22 on the device pc1.
[0036] The rule information in security analysis indicates the occurrence conditions and dependencies of threats and attack methods. Examples of rule information are as follows: “informationTampering(Machine,File) :-fileLocation(Machine,File), fileManipulation(Attacker,Machine,File). This example shows rule information for tampering with files in a machine, including rules that there are files in the machine and rules that attack files in the machine.
[0037] Factual information in security analysis indicates the configuration information of the system being analyzed. Examples of factual information are as follows: “wifi” is a registered trademark. "machineClass(pc1,pc)." This indicates the fact that the type of the machine pc1 is pc. "fileLocation(pc1,plan22)." This indicates the fact that the file plan22 is located on the device pc1. "networkAccess(pc1,nw1,pc2)." This indicates the fact that device pc1 and device pc2 are connected via network nw1. "networkClass(nw1,wifi)." This indicates the fact that the type of network nw1 is wifi.
[0038] Based on Figure 7, we will explain how attack scenarios are generated when using a rule-based system. (1) First, the final goal PC1 and the initial goal PC2 are determined. The final goal is the component (threat target) given in the question. (2) Next, the intrusion path from the initial target PC2 to the final target PC1 (PC2→communication path 1→PC1) is identified. (3) While referring to the intrusion paths in reverse chronological order of the attack activities (analysis order), infer based on rules and facts whether the necessary attack is possible at each component of the intrusion path. By tracing the intrusion path in reverse order of analysis, a timeline of attack activities (i.e., an attack scenario) can be obtained.
[0039] The procedure of the security analysis method will be described with reference to FIG. In step S110, the receiving unit 110 receives the system configuration information of the target system. A target system is a system that is the subject of security analysis.
[0040] Specifically, a user inputs various definitions of the target system together with an execution command to security analysis system 100 . The accepting unit 110 then receives the various definitions that have been input and generates data indicating the various definitions that have been received. The generated data is the system configuration information.
[0041] The various definitions of the target system indicate component device information, installation location information, communication path information, information asset information, registered person information, and the like. The component device information indicates one or more component devices and the security information of each component device. A component device is an element (component) of the target system. Examples of component devices include PCs, servers, PLCs, and sensors. The security information of a component device is information related to security analysis of the component device. For example, the security information of a component device indicates the OS type, installed SW, and countermeasure functions. PC is an abbreviation for personal computer. PLC is an abbreviation for programmable logic controller. SW is an abbreviation for software. The installation location information indicates the installation location of each component device and security information for each installation location. The installation location of a component device means the physical location where the component device is installed. Examples of the installation location of a component device include a section, a room, or a rack. The security information of the installation location is information related to a security analysis for the installation location. For example, the security information of the installation location indicates countermeasures. The communication path information indicates the communication paths between the component devices and the security information of each communication path. A communication path is a component of the target system. The security information of a communication path is information regarding security measures for the communication path. For example, the security information of a communication path indicates the line type, communication protocol, and security functions. The information asset information indicates the information assets flowing through each communication path and the security information of the information assets. Examples of information assets include customer information and operation commands. The security information of the information assets is information related to security analysis of the information assets. For example, the security information of the information assets indicates the asset value and countermeasures. The registered person information indicates one or more people involved in the target system and the security information of each person involved. People involved in the target system are people involved in the target system who are capable of attacking the target system. Examples of people involved in the target system include regular employees, outsourced maintenance staff, and third parties. Security information of people involved is information related to security analysis of the people involved. For example, security information of people involved includes roles, accessible locations, IT skills, and the presence or absence of malicious intent. Accessible locations are locations where access is permitted. IT is an abbreviation for information technology.
[0042] In step S120, the threat identification unit 120 identifies security threats to the target system based on the system configuration information of the target system.
[0043] The procedure of step S120 will be described with reference to FIG. In step S121, the information acquisition unit 121 acquires system configuration information of the target system. Specifically, the information acquisition unit 121 receives system configuration information of the target system from the reception unit 110 .
[0044] The system configuration information includes one or more pieces of component information and one or more pieces of registered person information.
[0045] In step S122, the final goal extraction unit 122 extracts final goal information from the system configuration information. The final goal information is component information of a component that can become a final goal. The target is the component from which the security threat originates. For example, each component of the target system can be a target.
[0046] Steps S123 to S125 are executed for each piece of final goal information extracted in step S122.
[0047] In step S123, the threat extraction unit 123 extracts one or more pieces of threat information indicating the same occurrence element type as the component type indicated in the final goal information from the threat database 191. In this step, the rule-based system is utilized.
[0048] In the threat database 191, information on one or more threats (threat information) is registered. The threat information indicates the name of the threat, the type of occurrence factor, and the occurrence condition. The occurrence element type is the type of component (occurrence element) from which a threat occurs. The occurrence conditions are the conditions for a threat to occur.
[0049] FIG. 10 shows an example of the threat database 191. The "Name" column indicates the name of the threat. The "element type" column indicates the type of generated element. The "Conditions" column indicates the conditions under which a threat occurs. For example, "information leakage" occurs in "devices" and not in "communication paths." However, "information leakage" occurs in "devices" such as personal computers or servers and not in "devices" such as controllers or sensors.
[0050] Returning to FIG. 9, the explanation will be continued. The threat information extracted in step S123 is referred to as threat candidate information.
[0051] In step S124, the threat extraction unit 123 selects, from one or more pieces of threat candidate information, threat candidate information that indicates the occurrence condition that is satisfied by the final target information. The selected threat candidate information is referred to as corresponding threat information.
[0052] In step S125, the threat extraction unit 123 generates target threat information for each piece of relevant threat information by using the final target information and the relevant threat information. The target threat information is information about a threat (target threat) occurring at the final goal. Specifically, the target threat information indicates the relevant parties, the final goal, and the target threat. After step S125, step S120 ends.
[0053] Step S120 will be supplemented. If there is no threat candidate information in step S123, step S124 and subsequent steps are not executed and step S120 ends. If there is no relevant threat information in step S124, step S125 is not executed and step S120 ends. In these cases, the output unit 140 outputs information to inform the user of the result that there is no threat, and the security analysis method ends without generating an attack scenario.
[0054] Returning to FIG. 8, the description will continue from step S130. In step S130, the attack scenario generator 130 generates an attack scenario based on the system configuration information and the target threat information.
[0055] The target threat information used in step S130 is the target threat information generated in step S125. By extracting a threat in step S125, the goal of the attack scenario is determined, and the system can calculate the attack scenario until the target threat information occurs.
[0056] The procedure of step S130 will be described with reference to FIG. The system configuration information is passed from the information acquisition unit 121 to the initial target extraction unit 131 .
[0057] In step S131, the initial goal extraction unit 131 extracts initial goal information from the system configuration information. The initial target information is component information of a component that can be an initial target. The initial target is a component that is attacked first to generate a threat at the final target. For example, each component of the target system other than the final target can be an initial target. It is also possible for the initial target to coincide with the final target, which occurs when an attacker can attack the final target in the first move.
[0058] Step S132 is executed for each piece of initial target information extracted in step S131.
[0059] In step S132, the intrusion route extraction unit 132 extracts intrusion route information from the system configuration information based on the initial target information and the final target information. The intrusion route information is information that indicates a route (intrusion route) from an initial target to a final target. The intrusion route information includes component information (attack target information) of one or more components (attack targets) of the intrusion route.
[0060] Steps S133 and S200 are executed for each piece of intrusion route information extracted in step S132.
[0061] In step S133, the identity determining unit 133 extracts corresponding method information from the attack method database 192 for each piece of attack target information included in the intrusion route information. The relevant method information is information on the relevant method (attack method information). The relevant method information indicates the occurrence conditions that the attack target information satisfies. The method in question is an attack method for attacking a target.
[0062] The attack method database 192 stores information on one or more attack methods (attack method information). The attack method information indicates the name of the method and the conditions under which it occurs. The occurrence conditions are the conditions for an attack to occur.
[0063] FIG. 12 shows an example of the attack method database 192. The "Name" column indicates the name of the attack method. The “Condition” column indicates the condition for an attack to occur. The condition is described in terms of the rule-based system. For example, if the device (attack target) is a PC, the device's OS is a Windows system, and an email client (software) is installed on the device, a suspicious email-type malware infection may occur.
[0064] Returning to FIG. 11, the description will continue from step S200. In step S200, the attack activity extraction unit 134 generates application activity information for each piece of attack target information. In this step, the rule-based system is utilized. The application activity information is attack activity information on an attack activity against an attack target using the corresponding technique.
[0065] The procedure of step S200 will be described with reference to FIG. Step S200 is executed for each piece of attack target information. If multiple pieces of method information corresponding to the attack target information are extracted, step S200 is executed for each piece of method information corresponding to the attack target information.
[0066] In step S211, the identity determination unit 133 determines whether the relevant activity information is registered in the attack activity database 193. The relevant activity information is attack activity information on attack activities against a similar target using the relevant method. A similar target is an attack target whose characteristics match those of the attack target in the attack method to be determined. In other words, a similar target is an attack target that is substantially the same as the attack target. In other words, a similar target is an attack target that is the same as the attack target or similar to the attack target.
[0067] The attack activity database 193 registers information on one or more attack activities (attack activity information). The attack activity information indicates information on the target of the attack and the type of attack method.
[0068] A procedure for determining whether an attack target is substantially the same as an attack target will be described with reference to Fig. 14. The attack target is a device PC2, and the attack target is a device PC4. (1) The identity determination unit 133 acquires a fact information set of an attack target and a fact information set of an attack target. The fact information set is one or more pieces of fact information. The fact information indicates the characteristics of the configuration element. (2) The identity determination unit 133 extracts predicates of fact information from the corresponding method information. In Fig. 14, the corresponding method is "unauthorized access", and the predicates "OS information" and "OS setting" are extracted. (3) The identity determination unit 133 extracts fact information having the same predicate as the extracted predicate from each of the fact information set of the attack subject and the fact information set of the attack target. Then, the identity determination unit 133 compares the extracted factual information of the attack subject with the extracted factual information of the attack target, ignoring proper nouns contained in each piece of factual information. If both pieces of factual information match, then the attack subject is substantially identical to the attack target. 14, the extracted factual information of device PC2 and the extracted factual information of device PC4 are identical except for the proper nouns (PC2, PC4). Therefore, device PC2 is substantially identical to device PC4.
[0069] Returning to FIG. 13, the explanation of step S211 will be continued. If the corresponding activity information is registered in the attack activity database 193, the identity determination unit 133 extracts the corresponding activity information from the attack activity database 193, and the process proceeds to step S212. If the relevant activity information is not registered in the attack activity database 193, the process proceeds to step S213.
[0070] In step S212, the attack activity extraction unit 134 generates applicable activity information using the relevant activity information. Specifically, the attack activity extraction unit 134 replaces the attack target name in the relevant activity information with the attack target name. The relevant activity information after the replacement becomes the target activity information. After step S212, step S200 ends.
[0071] In step S213, the attack activity extraction unit 134 determines whether the attack target information satisfies the occurrence condition indicated in the corresponding method information. If the attack target information satisfies the occurrence condition indicated in the corresponding method information, the process proceeds to step S214. If the attack target information does not satisfy the occurrence condition indicated in the corresponding method information, step S120 ends. In this case, the output unit 140 outputs information to inform the user of the result that there is no attack scenario. Then, the security analysis method ends without generating an attack scenario.
[0072] In step S214, the attack activity extraction unit 134 generates applied activity information using the attack target information and the corresponding technique information. Application activity information indicates the people involved, the attack targets, and the applicable methods.
[0073] In step S215, the attack activity extraction unit 134 registers the generated application activity information in the attack activity database 193 as attack activity information. After step S215, step S200 ends.
[0074] Returning to FIG. 11, step S134 will be described. In step S134, the attack activity combination unit 135 combines the generated application activity information to generate an attack scenario. Specifically, the attack activity combination unit 135 combines the applicable activity information in chronological order of the attack activities along the intrusion route.
[0075] Returning to FIG. 8, step S140 will be described. In step S140, the output unit 140 outputs the generated attack scenario. For example, the output unit 140 displays the attack scenario on a display.
[0076] *** Description of the Example *** The attack activity database 193 manages multiple pieces of attack activity information in a list. However, the attack activity database 193 may hierarchically manage one or more pieces of abstracted activity information and a plurality of pieces of attack activity information. The abstracted activity information is abstracted attack activity information.
[0077] FIG. 15 shows an example of the configuration of the attack activity database 193. The attack activity database 193 manages five pieces of abstract activity information and four pieces of attack activity information in three hierarchical layers. At the third level, four pieces of attack activity information are managed. Each piece of attack activity information indicates the proper name of the target of the attack. The second layer manages three abstracted activity information pieces obtained by abstracting the attack activity information from the third layer. Each abstracted activity information piece indicates the target of the attack by type, rather than by a proper noun. The first layer manages two pieces of abstracted activity information obtained by abstracting the attack activity information in the second layer. Each piece of abstracted information indicates the form of an attack rather than its method. By hierarchically managing one or more abstracted activity information and multiple attack activity information, the searchability of the attack activity database 193 is improved.
[0078] An example of a search method using hierarchical management is shown below. First, it is determined whether the characteristics of the relevant activity information match the characteristics of each activity information in the most abstract layer (highest layer) in the attack activity database 193. If there is activity information whose features do not match the corresponding activity information (mismatching activity information), the activity information in the lower layer for the mismatching activity information (activity information more specific than the mismatching activity information) is excluded from the search. For example, if the corresponding activity information is activity information for IT equipment, there is no need to search for activity information for OT equipment (mismatching activity information) and lower-level activity information that embodies the activity information for OT equipment. In this way, the search begins at the abstract layer (higher layer), and the search scope is narrowed by pruning search branches, and a search is performed to see if there is any attack activity that can be determined to be identical at the concrete layer (lower layer). This is the most naive example, and existing efficient algorithms for searching a hierarchical database may be employed.
[0079] A non-hierarchical attack activity database is a state in which activity information of the most specific layer (lowest layer) of the hierarchical attack activity database 193 is listed one-dimensionally. A search method using hierarchical management is expected to reduce the number of search steps compared to a naive search method for activity information registered in a non-hierarchical attack activity database.
[0080] The abstraction of attack activity information will be described based on FIG. (1) An abstract ontology is prepared in advance. The abstract ontology is prepared, for example, by a developer. The prepared abstract ontology is stored, for example, in the attack activity database 193. (2) Attack activity information is abstracted according to the abstraction ontology. The attack activity information is abstracted, for example, by a tool. For example, the attack activity extraction unit 134 abstracts the attack activity information by executing the tool using the attack activity information and the abstraction ontology as input. In FIG. 16, the proper noun "PC1" is abstracted into the type "PC", and the type "PC" is abstracted into "IT device".
[0081] ***Advantages of the First Embodiment*** The first embodiment proposes a technology that enables more efficient calculations with high reusability of calculation results while ensuring the comprehensiveness of attack scenarios.
[0082] The identity determination unit 133 compares information on targets (devices / communication paths) for which an attack method needs to be analyzed against an intrusion route with previously calculated attack targets, using the attack activity database 193. The comparison is performed by focusing only on features necessary for determining the attack method to be analyzed. If there is a matching attack target, the attack activity extraction unit 134 generates attack activity information by a string replacement operation. In other words, the attack activity extraction unit 134 reuses past attack activity information. This makes it possible to reuse past calculation results even if the required attack activity information does not exactly match the past calculation results (attack activity information), and makes it possible to skip analysis and generate attack activity information by string replacement. If there is no past attack activity information that can be reused, attack scenarios are generated using the rule-based system.
[0083] In the attack activity database 193, the analyzed attack activity information is abstracted based on the characteristics of the target of the attack and stored hierarchically. This improves the searchability of the calculation results (attack activity information) and reduces the processing load of the identity determination unit 133.
[0084] According to the first embodiment, when generating an attack scenario by reusing past calculation results (attack activity information), it is possible to reuse the past calculation results even if they do not completely match the required attack activity information. Therefore, there are more opportunities to reuse the past calculation results, and attack scenarios can be generated more efficiently than with the conventional technology. In the first embodiment, the possibility of reuse (diversion) can be determined by a string comparison operation, and therefore the calculation cost is low. In the first embodiment, the processing cost is low because reuse (repurposing) can be performed by a character string replacement operation. In the first embodiment, the reused calculation results (past attack activity information) are hierarchically stored in a database, making it easy to search.
[0085] Embodiment 2 The form in which the attack activity database 193 is utilized will be described below with reference to FIG. 17 and FIG. 18, mainly with respect to the points that differ from the first embodiment.
[0086] *** Overview *** The second embodiment will be outlined with reference to FIG. In the second embodiment, the attack activity database 193 constructed by the security analysis method for the target system is utilized in the security analysis method for the updated target system (another system having a common part with the target system). This makes it possible to omit the analysis of the common part. 17, systems A and B have common parts except for PC4 and PC5. Therefore, if attack activity database 193 constructed by the security analysis method for system A is applied to the security analysis method for system B, it becomes possible to omit calculations for the common parts of systems A and B. However, there is a constraint that the security analysis method for system A and the security analysis method for system B require that threat database 191 and attack method database 192 are the same.
[0087] ***Configuration Description*** Based on FIG. 18, the configuration of a security analysis system 100 is provided. The security analysis system 100 further comprises an element called a preparation unit 150 . The security analysis program further causes the computer to function as a preparation unit 150 .
[0088] ***Explanation of Operation*** The operation of security analysis system 100 (excluding preparation unit 150) is the same as that in the first embodiment.
[0089] The preparation unit 150 operates as follows. Before step S130 is executed, the preparation unit 150 determines whether the attack activity database 193 for the previous target system is to be carried over to the current target system. For example, the user specifies to the security analysis system 100 whether or not to take over the attack activity database 193, and the preparation unit 150 makes a decision according to the user's specification. When the attack activity database 193 is inherited, the preparation unit 150 does not initialize the attack activity database 193. If the attack activity database 193 is not to be carried over, the preparation unit 150 initializes the attack activity database 193.
[0090] ***Effects of the second embodiment*** According to the second embodiment, when analyzing a new system, it is possible to divert (reuse) attack activity information of a system that has been analyzed in the past, which is expected to reduce calculations.
[0091] ***Additional information to the second embodiment*** It is expected that as the amount of data in the attack activity database 193 increases, the amount of spatial calculation increases, slowing down the processing of the identity determination unit 133. For this reason, it is not desirable to store data indiscriminately. Therefore, it is advisable to take over the attack activity database 193 that has accumulated data on similar systems that are likely to be diverted (reused) as much as possible. Specifically, it is considered to be highly effective to utilize the attack activity database 193 obtained after analyzing IT system A for the updated IT system A or a similar IT system B.
[0092] The second embodiment is particularly effective in cases where a specific system is repeatedly analyzed. For example, the second embodiment is particularly effective for analysis during agile development. The second embodiment is also particularly effective in cases where a system that is continuously updated is analyzed over a long period of time.
[0093] Embodiment 3 The embodiment in which information obtained by identity determination is utilized will be described below with reference to Figs. 19 to 21, mainly with respect to the points that differ from the first embodiment.
[0094] ***Configuration Description*** The configuration of security analysis system 100 is similar to that in the first embodiment. However, a part of the attack activity database 193 is different from the configuration in the first embodiment.
[0095] The configuration of the attack activity database 193 will be described with reference to FIG. In addition to attack activity information, the attack activity database 193 stores past determination results of the identity determination unit 133. Specifically, the attack activity database 193 stores information (determination result) indicating the matching portion for each pair of attack targets whose characteristics partially match each other.
[0096] ***Explanation of Operation*** The procedure of the security analysis method is similar to that in the first embodiment. However, a part of step S200 is different from the procedure in the first embodiment.
[0097] The procedure of step S200 will be described with reference to FIG. In step S231, the identity determination unit 133 determines whether the relevant activity information is registered in the attack activity database 193. At this time, the identity determination unit 133 utilizes the determination results stored in the attack activity database 193.
[0098] Specifically, the identity determining unit 133 utilizes the determination result as follows. The identity determination unit 133 determines whether a matching determination result is stored in the attack activity database 193 for each piece of attack activity information registered in the attack activity database 193. The matching determination result is a determination result that a pair of an attack target and an attack target of the attack activity information is an attack target pair. If the matching determination result is stored, the identity determination unit 133 compares the characteristics of the attack target with the characteristics of the attack target in the attack activity information, excluding the matching parts shown in the matching determination result, and determines whether the attack target in the attack activity information is a similar target. If the corresponding determination result is not stored in the attack activity database 193, the identity determination unit 133 compares all of the characteristics of the attack target with all of the characteristics of the attack target in the attack activity information and determines whether the attack target in the attack activity information is a similar target.
[0099] If the corresponding activity information is registered in the attack activity database 193, the identity determination unit 133 extracts the corresponding activity information from the attack activity database 193, and the process proceeds to step S232. If the relevant activity information is not registered in the attack activity database 193, the process proceeds to step S233.
[0100] In step S232, the attack activity extraction unit 134 generates target activity information using the relevant activity information. Step S232 is the same as step S212 in the first embodiment. After step S232, step S200 ends.
[0101] In step S233, the identity determination unit 133 registers the determination result obtained in step S231 in the attack activity database 193.
[0102] Specifically, the identity determination unit 133 generates a matching determination result based on the comparison result in step S231, and stores the generated matching determination result in the attack activity database 193.
[0103] An example of identity determination will be described with reference to FIG. (1) The target of the attack is "pc2". The target of the attack is "pc4". The method in question is "connecting an unauthorized terminal". (2) The attack target information indicates the characteristics of "pc2". The attack target information indicates the characteristics of "pc4". Since the attack target information does not match the attack target information in the identity determination, the determination result is stored in the attack activity database 193. The determination result indicates that "pc2" and "pc4" match for "OS information" and "external interface". (3) In the next and subsequent identity determinations, the comparison of "OS information" and "external interface" is omitted because the determination results are stored in the attack activity database 193. This reduces the processing cost of the next and subsequent identity determinations.
[0104] Returning to FIG. 20, the explanation will be continued. Steps S234 to S236 are the same as steps S213 to S215 in the first embodiment. After step S236, step S200 ends.
[0105] ***Effects of the Third Embodiment*** According to the third embodiment, when determining the identity of attack subject A and attack target B for a different attack method, it is not necessary to compare features that are known to match, and it is expected that the weight of the identity determination process will be reduced. As the security analysis approaches the final stage, the determination results will be accumulated, and further weight reduction is expected.
[0106] ***Additional Note to the Third Embodiment*** The third embodiment may be implemented in combination with the second embodiment. That is, in the third embodiment, the security analysis system 100 may include the preparation unit 150, and may take over the attack activity database 193 to implement the security analysis method.
[0107] ***Supplementary explanation of implementation form*** Each embodiment is an example of a preferred embodiment, and is not intended to limit the technical scope of the present disclosure. Each embodiment may be implemented in part or in combination with other embodiments. The procedures described using flow charts, etc. may be modified as appropriate.
[0108] The security analysis system 100 may be implemented on multiple computers. Each function of the security analysis system 100 may be implemented in software, hardware, firmware, or a combination thereof. The "part" of each element of security analysis system 100 may be read as a "process," a "step," a "circuit," or a "circuitry."
[0109] Various aspects of the present disclosure are described below as appendices. (Appendix 1) A security analysis system that generates attack scenarios. The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, an identity determination unit that determines whether the corresponding activity information is registered in an attack activity database in which attack activity information of each of a plurality of attack activities is registered for each of the attack target information; an attack activity extraction unit that generates the application activity information using the corresponding activity information when the corresponding activity information is registered for each of the attack target information, and generates the application activity information using the attack target information and the corresponding technique information when the corresponding activity information is not registered; an attack activity combination unit that combines the generated application activity information to generate the attack scenario; A security analysis system comprising:
[0110] (Appendix 2) The identity determination unit extracts, for each of the attack target information, attack method information indicating an attack occurrence condition satisfied by the attack target information from an attack method database in which attack method information for each of a plurality of attack methods is registered, as the corresponding method information. 2. A security analysis system as described in Appendix 1.
[0111] (Appendix 3) The attack activity database hierarchically manages one or more abstracted activity information, which is one or more pieces of abstracted attack activity information, and a plurality of pieces of attack activity information. 2. A security analysis system as described in claim 1 or 2.
[0112] (Appendix 4) The attack activity extraction unit registers the generated applicable activity information in the attack activity database when the corresponding activity information is not registered. 4. A security analysis system according to any one of claims 1 to 3.
[0113] (Appendix 5) A preparation unit is provided for determining whether the attack activity database after the attack scenario for the previous target system is generated should be handed over to the current target system before an attack scenario for the current target system is generated, not initializing the attack activity database if the attack activity database is handed over, and initializing the attack activity database if the attack activity database is not handed over. 5. A security analysis system as described in claim 4.
[0114] (Appendix 6) The attack activity database stores a determination result, which is information indicating a matching portion for each pair of attack targets having a part of a characteristic that matches each other, The identity determination unit, for each of the attack activity information registered in the attack activity database, uses the determination result, which sets a pair of the attack target and the attack target of the attack activity information as the attack target pair, as a matching determination result, and when the matching determination result is stored in the attack activity database, compares the characteristics of the attack target and the characteristics of the attack target of the attack activity information excluding the matching portion shown in the matching determination result to determine whether the attack target of the attack activity information is the similar target, and when the matching determination result is not stored in the attack activity database, compares all of the characteristics of the attack target and all of the characteristics of the attack target of the attack activity information to determine whether the attack target of the attack activity information is the similar target, and generates the matching determination result and stores it in the attack activity database. 6. A security analysis system according to any one of claims 1 to 5.
[0115] (Appendix 7) A security analysis method for generating attack scenarios, The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, For each of the attack target information, it is determined whether the corresponding activity information is registered in an attack activity database in which attack activity information for each of a plurality of attack activities is registered; For each of the attack target information, if the corresponding activity information is registered, the application activity information is generated using the corresponding activity information, and if the corresponding activity information is not registered, the application activity information is generated using the attack target information and the corresponding technique information; The generated application activity information is combined to generate the attack scenario. Security analysis methods.
[0116] (Appendix 8) It is a security analysis program for generating attack scenarios, The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, an identity determination process for determining whether the corresponding activity information is registered in an attack activity database in which attack activity information of each of a plurality of attack activities is registered for each of the attack target information; an attack activity extraction process for generating the application activity information using the corresponding activity information when the corresponding activity information is registered for each of the attack target information, and generating the application activity information using the attack target information and the corresponding technique information when the corresponding activity information is not registered; an attack activity combination process for combining the generated application activity information to generate the attack scenario; A security analysis program for a computer to run. [Explanation of symbols]
[0117] 100 security analysis system, 101 processor, 102 memory, 103 auxiliary storage device, 104 input / output interface, 110 reception unit, 120 threat identification unit, 121 information acquisition unit, 122 final goal extraction unit, 123 threat extraction unit, 130 attack scenario generation unit, 131 initial goal extraction unit, 132 intrusion path extraction unit, 133 identity determination unit, 134 attack activity extraction unit, 135 attack activity combination unit, 140 output unit, 150 preparation unit, 190 memory unit, 191 threat database, 192 attack method database, 193 attack activity database.
Claims
1. A security analysis system that generates attack scenarios. The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, an identity determination unit that determines whether the corresponding activity information is registered in an attack activity database in which attack activity information of each of a plurality of attack activities is registered for each of the attack target information; an attack activity extraction unit that generates the application activity information using the corresponding activity information when the corresponding activity information is registered for each of the attack target information, and generates the application activity information using the attack target information and the corresponding technique information when the corresponding activity information is not registered; an attack activity combination unit that combines the generated application activity information to generate the attack scenario; A security analysis system comprising:
2. The identity determination unit extracts, for each of the attack target information, attack method information indicating an attack occurrence condition satisfied by the attack target information from an attack method database in which attack method information for each of a plurality of attack methods is registered, as the corresponding method information. The security analysis system of claim 1 .
3. The attack activity database hierarchically manages one or more abstracted activity information, which is one or more pieces of abstracted attack activity information, and a plurality of pieces of attack activity information. The security analysis system of claim 1 .
4. The attack activity extraction unit registers the generated applicable activity information in the attack activity database when the corresponding activity information is not registered. The security analysis system of claim 1 .
5. A preparation unit is provided for determining whether the attack activity database after the attack scenario for the previous target system is generated should be handed over to the current target system before an attack scenario for the current target system is generated, not initializing the attack activity database if the attack activity database is handed over, and initializing the attack activity database if the attack activity database is not handed over. The security analysis system of claim 4 .
6. The attack activity database stores a determination result, which is information indicating a matching portion for each pair of attack targets having a part of a characteristic that matches each other, The identity determination unit, for each of the attack activity information registered in the attack activity database, uses the determination result, which sets a pair of the attack target and the attack target of the attack activity information as the attack target pair, as a matching determination result, and when the matching determination result is stored in the attack activity database, compares the characteristics of the attack target and the characteristics of the attack target of the attack activity information excluding the matching portion shown in the matching determination result to determine whether the attack target of the attack activity information is the similar target, and when the matching determination result is not stored in the attack activity database, compares all of the characteristics of the attack target and all of the characteristics of the attack target of the attack activity information to determine whether the attack target of the attack activity information is the similar target, and generates the matching determination result and stores it in the attack activity database. The security analysis system of claim 1 .
7. A security analysis method for generating attack scenarios, The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, For each of the attack target information, it is determined whether the corresponding activity information is registered in an attack activity database in which attack activity information for each of a plurality of attack activities is registered; For each of the attack target information, if the corresponding activity information is registered, the application activity information is generated using the corresponding activity information, and if the corresponding activity information is not registered, the application activity information is generated using the attack target information and the corresponding technique information; The generated application activity information is combined to generate the attack scenario. Security analysis methods.
8. It is a security analysis program for generating attack scenarios, The intrusion path information includes attack target information for each of the one or more attack targets; The method information is attack method information of an attack method for attacking the attack target, The method is the attack method of the method information, A similar target is an attack target having characteristics that match those of the attack target in the attack target information, The relevant activity information is attack activity information of an attack activity against the target by the relevant method, The application activity information is attack activity information of an attack activity against the attack target by the corresponding technique, an identity determination process for determining whether the corresponding activity information is registered in an attack activity database in which attack activity information of each of a plurality of attack activities is registered for each of the attack target information; an attack activity extraction process for generating the application activity information using the corresponding activity information when the corresponding activity information is registered for each of the attack target information, and generating the application activity information using the attack target information and the corresponding technique information when the corresponding activity information is not registered; an attack activity combination process for combining the generated application activity information to generate the attack scenario; A security analysis program for a computer to run.
Citation Information
Patent Citations
System security design device, system security design method, and system security design program
JP2009070084A
Cited By
Protection target identification system, protection target identification program, and protection target identification method
JP7804381B1
