EBIOS Risk Manager workshops #

Available

The /ebios route implements the five EBIOS RM workshops as a governed workflow. It uses only analyses created with the EBIOS_RM method under Analyses and knowledge capitalization. Each workshop has structured content, status, version, last author and, after validation, a validator and timestamp.

Five-workshop path #

Workshop	Required content
1 — Scope and baseline	context, business values, supporting assets, dreaded events, security baseline
2 — Risk sources	risk sources and target objectives
3 — Strategic scenarios	ecosystem and strategic scenarios
4 — Operational scenarios	operational scenarios and steps
5 — Risk treatment	treatment measures and residual risks

Create the EBIOS analysis first, select it in /ebios, then complete each element. List fields accept one item per line. Saving increments the version and sets READY when all required fields exist; otherwise the workshop remains DRAFT and the API returns missingFields.

Independent, ordered validation #

Workshops are validated in order. Workshop N cannot be validated before N−1 is VALIDATED. The validator must differ from the latest author. A validated workshop is immutable in the screen; further work belongs in a new analysis version rather than silently changing a validated result.

Permissions and API #

Method	Endpoint	Permission
`GET`	`/api/v1/ebios/analyses`	`ebios.read`
`GET`	`/api/v1/ebios/analyses/{id}/workshops/{1..5}`	`ebios.read`
`PUT`	`/api/v1/ebios/analyses/{id}/workshops/{1..5}`	`ebios.update`
`POST`	`/api/v1/ebios/analyses/{id}/workshops/{1..5}/validate`	`ebios.validate`

Stable errors are FORBIDDEN (403), NOT_FOUND (404), VALIDATION_ERROR, INVALID_WORKSHOP, PREVIOUS_WORKSHOP_REQUIRED, INCOMPLETE_WORKSHOP with missingFields, and INVALID_VALIDATION (422). All queries verify organization and analysis method.