Teams at workMap and test controlsExample · 1 question · 2 min

Build the Risk Bow-Tie

Map a fictional data-loss pathway and distinguish what prevents the event from what limits impact after it occurs.

Answer
Feedback
Finish

Your example

Risk path

The bow-tie runs from left to right. Threat: stolen login credentials, with multi-factor sign-in as a barrier before the event. Top event in the middle: data loss. Consequence: service outage, so far without a barrier.

Show data as a table

Node	Details
Credential theft	threat · barrier before: MFA
Data loss	top event
Service outage	consequence · no barrier yet

Choose one answer

A tested restore procedure reduces impact after data loss. Where does it belong, and what can it prove?

On the consequence side: it limits the damage after data loss but does not prevent it.On the threat side: a tested backup prevents data loss from happening at all.

About this activity

What you practise: Take a new fictional hazard and place one preventive barrier and one mitigating barrier, giving each a testable evidence statement.

A hand-written example with a fixed sequence. It shows what working on a Klarisma activity feels like; your own activities follow your goals and material.

An example with fictional data. Your answers stay on this page and are cleared when you restart or leave.

A tested restore procedure reduces impact after data loss. Where does it belong, and what can it prove? The bow-tie runs from left to right. Threat: stolen login credentials, with multi-factor sign-in as a barrier before the event. Top event in the middle: data loss. Consequence: service outage, so far without a barrier. The restore is used after the top event. A control can reduce consequence severity without preventing the event that triggered it.