Threat-Chain System Configuration for Early Insecure Design Rejection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automated secure system design techniques require repeated generation and evaluation of system configuration plans, leading to inefficiencies and prolonged time to derive a secure configuration, as they either reject insecure configurations late in the process or generate numerous insecure plans.
Innovation Solution
A system design device and method that includes an acquisition, configuration concretization, threat concretization, and analysis process to determine the security of system configurations by identifying and addressing concrete or abstract threats in threat chains, allowing early rejection of insecure designs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security evaluation is performed after generating complete system configuration plans, then comprehensive security assessment is achieved, but numerous insecure configuration plans are generated and rejected, increasing time consumption
Solution Approach 1:
The patent applies preliminary action by performing security evaluation during the configuration generation process rather than after completion. The security evaluation unit continuously assesses generated configuration plans and provides feedback to the generation unit, enabling early detection of insecure configurations and avoiding wasted computation on obviously vulnerable designs.
Solution Approach 2:
The patent implements feedback mechanisms where the security evaluation unit continuously monitors generated configuration plans and feeds security assessment results back to the configuration generation unit. This feedback loop enables real-time correction of insecure configurations and guides the generation process toward secure designs, reducing the number of rejected plans.
2Reliability
If repeated generation and evaluation of system configuration plans is performed to search for secure configurations, then thorough security search is achieved, but the derivation process becomes time-consuming
Solution Approach 1:
The patent performs preliminary security evaluation during the configuration generation process itself, rather than waiting for complete configuration plans. This allows the system to identify and eliminate insecure configuration paths early, reducing the total number of configurations that need to be fully generated and evaluated, thus improving efficiency while maintaining thoroughness.
Solution Approach 2:
The continuous feedback loop between generation and security evaluation units enables the system to learn from security assessments and adjust the generation process in real-time. This feedback mechanism guides the search toward secure configurations more efficiently, reducing redundant generation of obviously insecure plans while maintaining comprehensive security coverage.
3Reliability
If security determination is conducted only after automated design completion, then final security verification is ensured, but a large number of insecure configuration plans are generated and rejected
Solution Approach 1:
The patent performs preliminary security determinations during the automated design process, continuously assessing configuration plans as they are generated. This early security detection prevents the system from completing and processing numerous obviously insecure configuration plans, reducing the overall complexity and volume of plans requiring full security verification.
Solution Approach 2:
The feedback mechanism continuously provides security assessment results to the configuration generation process, enabling real-time filtering of insecure configurations. This reduces the number of configuration plans that proceed through the entire generation and evaluation pipeline, thereby reducing system complexity and processing requirements while maintaining final security verification.
Data Source
AI summary
First configuration information is acquired, which includes information on a topology using components of any one component of nodes in a computer system and an edge indicating a relationship between nodes. A configuration of a topology of first configuration information is concretized. Whether or not a security threat event may occur in a node or an edge in the configuration of the concretized topology is determined, and configuration information is generated in which information indicating a relationship between the configuration component in which a threat may occur if the threat event may occur and another configuration component in which another threat contributing to the occurrence of the threat may occur, is added. Whether the content of each threat is concrete or abstract in a threat chain path based on the relationship between the threat in the configuration information and another threat that contributes to the occurrence of the threat, is determined, and whether or not a design is insecure if the content of the threat is concrete or if it is abstract, is determined.