Automated Threat Scenario Creation (Cybersecurity)

medini_1068027459

In the automated threat scenario creation we observed an interesting behaviour: When referencing a cybersecurity property to a damage scenario (in the sense, that the loss of the property leads to the damage scenario) a threat scenario is automatically created. If the same cyber security property is afterwards referenced to another damage scenario an additional threat scenario is created with a connection to both the first and the second damage scenario. This however is makes no sense, because the name of the (automatically created) threat scenario is specific to the damage scenario. attached is the obfuscated project, location of the mentioned damage and threat scenarios can be seen in the following screenshot. Threat Scenario Collection:

medini_1068027459

Note: in the obfuscated project, the Threat Scenario naming is not obvious, you'd need to recreate that in order to see this problem. Important is, that the number of damage scenarios linked to the threat scenarios marked in the table above increases with every automatically created threat scenario. This seems to be the case, because the previously linked damage scenarios are always linked to the next threat scenario for a fixed cyber security property.