3.2 — Strategic scenarios

Page /ebios/scenariosstrategiques — builds strategic attack paths by linking a risk source, a targeted objective and, where relevant, an ecosystem stakeholder.

Toolbar

Button	Function
+ New scenario	Creates a strategic scenario (risk source + targeted objective)
✦ Generate A3 paths	AI generation of attack path proposals from the scenario
≡ Table / ◈ Diagram	Toggle between table view and diagram view
Likelihood ON/OFF	Shows/hides the Likelihood column in table view

Structure of a scenario

Each scenario groups one or more attack paths. The scenario header lets you choose:

• RS — risk source, entered freely or picked from the library (📚) among the RS/OT pairs defined in Workshop 2
• The associated targeted objective

Table columns (per path)

Column	Description
No.	Path number within the scenario
Path type	Direct / via stakeholder / via support asset
Stakeholder	Stakeholder used, if applicable (from page 3.1)
Description of the strategic attack path	Free text describing the path
Feared event	(optional) Link to a FE from Workshop 1
Likelihood	(optional, toggleable) L1 to L4
Severity	Carried over from the associated feared event

Diagram view

Displays each scenario as a visual diagram (source → path(s) → objective), useful for presenting strategic scenarios concisely in a review committee.

AI path generation

The ✦ Generate A3 paths button proposes attack paths built from the stakeholders already entered. Each proposal shows the source, the objective, the stakeholder used, the description, and the suggested severity and likelihood — to be validated before import into the table.

Direct path vs via a third party

A direct path is simpler to address (internal measures), while a path via a stakeholder often requires measures shared with the third party (contractual, technical) — document this clearly in the description.

Next steps

Retained strategic scenarios are detailed into technical attack chains in Workshop 4, page Operational scenarios.

See also Workshop 3 — Overview.