Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

To manage your attack paths, open the Global Attack Paths view and click the green ‘plus’ icon in the upper right edge to add a new row.

Identifying Attack Paths (Using Global Catalogs)

An attack path can be added to a threat scenario by creating row in a nested table below a threat scenario. Right-click on a threat scenario and select “Add Attack Path” from the context menu.

The overall design and usage of the attack path table are analogous to the other tables. As the below screenshot demonstrates, Attack Paths are sourced from the associated catalog. Having added a row to take your Attack Path, double-click inside the input field and make your selection from the drop-down menu provided.

For each rating parameter or metric select the level from drop-down menu as needed. You may declare a textual Justification.

Identifying Attack Paths (Using Project-Level Catalogs)

Project-specific Attack Paths, in common with other resources, are administrated in the context of your project’s RM folder. The screenshot below highlights the RM folder and shows both global and project Attack Paths.

A possible working method involves copying Attack Paths from the global catalog to the project catalog by dragging and dropping. The Attack Paths will then be available for use within your project context.

The next figure shows an example outcome with three attack paths added to a threat scenario. Attack potential method is applied for AF rating.

The Attack Feasibility is derived from processing the relevant input. Note that the highest value, in this case, “High”, propagates to the Threat Scenario:

Identifying Attack Steps

Attack paths can be characterized in more detail by adding one or more attack steps. The attack steps of an attack path might be derived from an attack tree analysis (ATA). Alternatively, attack steps can be created directly in TARA.

Attack Steps management is subject to the same rationale as applicable to Attack Paths. Thus, to manage your attack paths, open the Global Attack Steps view as described in
new TARA Main Table And Views and click the green ‘plus’ icon in the upper right edge to add a new row.

To add an attack step right-click on an attack path and select “Add Attack Step” from the context menu. This activity will create a nested table containing the attack steps of corresponding attack path.

An attack step provides a variety of attributes allowing a detailed characterization of the underlying attack activity. As shown below, Attack Steps are sourced from their associated catalog (global catalog scenario).

Add content as needed:

  • A text field is provided to assign a Name (optional)

  • A Vulnerability can be selected from the drop-down menu if known.

  • Select a Cybersecurity Property and Attack Class from the drop-down menu as required.

  • Preceding Step provides a drop-down menu listing all attack steps in the project. By this you define the order of action.

At attack step level the (local) attack feasibility can be rated as well to support rating on attack path level. The rating method is adopted from attack path.

The next figure presents a total of three attack steps containing varying levels of detail.

  • No labels