2.3 — RS/OT → feared events mapping

Workshop 2.3: associate each retained risk source / targeted objective pair with the feared events from Workshop 1 that it could plausibly cause.

This is the junction point between Workshop 1 (what we fear) and Workshop 2 (who could cause it, and why).

Two tabs

Pairs table — reuses the rating from 2.2: source, objective, motivation, resources, relevance, priority, retained, and a justification in case of exclusion.

Mapping to feared events — one row per retained pair, with the list of associated feared events. Associate button to add one, with a filter; a cross to remove one.

What the page requires

It only works with retained pairs

The mapping tab is empty until at least one pair is marked Retained in 2.2. The empty-state message explicitly points back to the pairs table.

Likewise, you need feared events defined in 1.3 — otherwise there is nothing to associate.

Deleting a feared event

Deleting a feared event referenced here triggers a confirmation that counts its dependencies: attack paths from Workshop 3, summary rows from Workshop 5, and RS/OT mapping links.

The principle applied

These items are kept: only their link to the feared event is cleared. An attack path or a summary row is never deleted as a side effect — only pure links, like the ones on this page, are.