🎉 VSEC Test v4.0.1 is now live! Release Notes ↗

Attack Steps

An Attack Step is a single discrete action an attacker takes as part of an Attack Path. Breaking attack paths into steps enables granular feasibility analysis and reuse across multiple paths.

List View

Open Risk ManagerLibrariesThreat Library. Attack Steps is the tab the Threat Library opens on.

The table shows each step’s ID (its auto-generated AS-xxx reference), Name, Attack Paths (reference chips), and an Actions column. Only the ID cell is a link — click it to open the detail page.

  • Create — click New in the toolbar. The New Attack Step dialog has a required Name plus optional ATM ID, Example, the five attack-potential factors, and Keywords (multi-select). The reference is auto-generated — there is no reference input.
  • Delete — click the delete icon in the Actions column; a confirmation dialog appears before permanent removal.

Detail Page

Click a step’s ID in the list to open its detail page. A Return to Attack Steps link navigates back to the list.

Details

FieldDescription
ReferenceAuto-generated identifier (e.g. AS-001)
NameDescriptive title of the attack action (required)
ATM IDOptional reference to an Attack Tree Model entry
ExampleIllustrative example of the step
FeasibilityThe five attack-potential values, shown as raw numbers (e.g. ET 4 · SE 3 · KoIC 7 · WoO 1 · Eq 4)

There is no Description field. Keywords can be set in the create/edit dialog but are not displayed on the detail page.

Attack Potential Factors

Each step carries five ISO/SAE 21434 attack-potential factors, entered as point values (higher points = harder for the attacker):

FactorWhat it measuresPoint values
ET — Elapsed TimeTime required for this step0 / 1 / 4 / 17 / 19
SE — Specialist ExpertiseSkill level needed0 / 3 / 6 / 8
KoIC — Knowledge of Item/ComponentFamiliarity with the target component0 / 3 / 7 / 11
WoO — Window of OpportunityAccessibility of the target0 / 1 / 4 / 10
Eq — EquipmentTools required0 / 4 / 7 / 9

Values are displayed as raw numbers — there is no Very Low/Low/Medium/High labeling and no stored per-step aggregate. Feasibility is aggregated per attack path at scoring time (see How feasibility works).

Attack Paths

Tab listing the Attack Paths that include this step. Click a path’s ID to navigate to the Attack Path detail page.

Editing

Click Edit on the detail page to open the step in a modal form dialog. Click Save Changes to persist or Cancel to discard.

Last updated on