A Damage Scenario is a construct defined in the automotive cybersecurity standard ISO 21434 and is described as the adverse consequence involving a vehicle or vehicle function and affecting a road user. They are typically caused by the loss of one or more cybersecurity properties associated to one or more assets.
Damage Scenarios are kept in damage scenario collections.
Select an arbitrary package in the project and use "New | Collection | Damage Scenario Collection". Give the collection an expressive name to summarize the reasoning behind this collection. Note, that there may be numerous damage scenario collections in the project or just one.
Open the damage scenario collection and use the "+" button to create new damage scenarios in the collection. The name of the damage scenario shortly describes it and is used throughout the tool as the label of the damage scenario. Give the damage scenario a more detailed description. An auto-counter-based identifier is given automatically to the damage scenario.
Damage Scenarios can also be put into cause-effect-relations by using the Cause/Effect net editor. Here they typically act as top-level effects which means that they themselves can only cause other damage scenarios or hazards. Regarding the causes of a damage scenario there are no limitations.
