---
id: CP-381
slug: ebios-risk-manager-risk-analysis-anssi
lang: en
title: "EBIOS Risk Manager: assessing digital risks"
description: "EBIOS Risk Manager, ANSSI's method for assessing digital risks: five workshops, the role of business teams, and a comparison with NIST."
canonical_url: https://startbrain.io/cyberpedia/en/articles/ebios-risk-manager-risk-analysis-anssi/
markdown_url: https://startbrain.io/cyberpedia/en/articles/ebios-risk-manager-risk-analysis-anssi.md
publisher: Brain (https://startbrain.io)
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
cite_as: "Brain, \"EBIOS Risk Manager: assessing digital risks\", Cyberpedia, 2026. https://startbrain.io/cyberpedia/en/articles/ebios-risk-manager-risk-analysis-anssi/ (CC BY 4.0)"
wing: 6
theme: safeguard_data
reflex: cr-036
schema: G3
updated: "2026-11-14"
translations:
  en: https://startbrain.io/cyberpedia/en/articles/ebios-risk-manager-risk-analysis-anssi/
  fr: https://startbrain.io/cyberpedia/fr/articles/ebios-risk-manager-analyse-risques-anssi/
  de: https://startbrain.io/cyberpedia/de/articles/ebios-risk-manager-risikoanalyse-anssi/
  es: https://startbrain.io/cyberpedia/es/articles/ebios-risk-manager-analisis-riesgos-anssi/
  it: https://startbrain.io/cyberpedia/it/articles/ebios-risk-manager-analisi-rischi-anssi/
  nl: https://startbrain.io/cyberpedia/nl/articles/ebios-risk-manager-risicoanalyse-anssi/
  pl: https://startbrain.io/cyberpedia/pl/articles/ebios-risk-manager-analiza-ryzyka-anssi/
  pt: https://startbrain.io/cyberpedia/pt/articles/ebios-risk-manager-analise-riscos-anssi/
  ja: https://startbrain.io/cyberpedia/ja/articles/ebios-risk-manager-risuku-bunseki-anssi/
sources:
  - "n": 1
    title: "EBIOS Risk Manager : méthode, ateliers et formations"
    publisher: ANSSI
    url: https://aide.messervices.cyber.gouv.fr/fr/article/ebios-risk-manager-realiser-une-analyse-de-risques-cyber-15p6xo1/
    accessed: "2026-11-14"
  - "n": 2
    title: Guide EBIOS Risk Manager (collection Gestion des risques cyber)
    publisher: ANSSI
    url: https://messervices.cyber.gouv.fr/documents-guides/250129_np_anssi_guide_ebios_fr_final_collection_WEB.pdf
    accessed: "2026-11-14"
  - "n": 3
    title: MooC EBIOS RM
    publisher: ANSSI
    url: https://messervices.cyber.gouv.fr/services/mooc-ebios-rm
    accessed: "2026-11-14"
  - "n": 4
    title: Guide for Conducting Risk Assessments
    publisher: NIST
    url: https://www.nist.gov/publications/guide-conducting-risk-assessments
    published: "2012-09-17"
    accessed: "2026-11-14"
  - "n": 5
    title: "Fiche méthode Atelier 4 : construire la cartographie de menace numérique de l'écosystème"
    publisher: ANSSI
    url: https://messervices.cyber.gouv.fr/documents-guides/Fiche_methode-Elaborer_des_graphes_d_attaque-atelier_4.pdf
    accessed: "2026-11-14"
  - "n": 6
    title: "EBIOS Risk Manager: The method"
    publisher: ANSSI
    url: https://messervices.cyber.gouv.fr/guides/en-ebios-risk-manager-method
    published: "2019-11-18"
    accessed: "2026-11-14"
---

# EBIOS Risk Manager: assessing digital risks

EBIOS Risk Manager (EBIOS RM) is the method for assessing and treating digital risk published by ANSSI, with the support of the Club EBIOS [1]. It answers a simple question: among everything that can go wrong in an organization, which risks really matter, and what should be done about them?

It does not take place in the IT department's office. The workshops bring together management, the business teams, the information systems security officer (RSSI) and the information systems department (DSI) [2]. An employee from a business unit may therefore be invited.

## In 30 seconds

- Where it happens: in working workshops, within a company, a public body or a digital project, whatever its size [2].
- What the method aims for: spotting digital risks, choosing security measures and getting the acceptable level of risk validated [2].
- The reflex: if your management or your RSSI invites you to a risk analysis workshop, come with your knowledge of the business, because that is what makes it possible to say what needs protecting.
- If it is already done: the analysis is not frozen, it is revised in cycles [1].

## Straight answers

### What is EBIOS RM for?

The method makes it possible to assess digital risks and to identify the security measures to put in place to control them. It also helps validate the acceptable level of risk and fit into a continuous improvement approach [2]. ANSSI describes three typical uses: setting up or strengthening a digital risk management process, treating the risks of a digital project with a view to a security accreditation (homologation), and defining the security level required for a product or a service [1].

### Who takes part in the workshops?

The core profiles are management (or decision-makers with the right level of delegation), the business teams, the RSSI and the DSI [1]. Depending on the workshop, others join: a specialist in digital threat analysis in workshop 2, people who know the contractual commitments with partners (generally Procurement or the legal department), functional architects and a cybersecurity specialist in workshop 3, and a cybersecurity specialist in workshop 4 [1].

### What do the business teams bring?

They know what matters in the activity. From the first workshop, the group lists the information or processes judged important and worth protecting, which the method calls "business values" [1]. In the guide's example, these values have owners: a pharmacist for research and development, a production manager and a quality manager for manufacturing and for traceability and control [2]. The method is designed to make decision-making levels and operational levels talk to each other [1].

### Do you need to be a technician to follow along?

No. According to ANSSI, the method turns complex threats into concrete, understandable scenarios by having business teams, IT, security and management work together [1]. The MOOC "Introduction à la méthode EBIOS Risk Manager", designed with the Club EBIOS, requires no technical prerequisite and remains accessible to motivated beginners [3].

### Who decides at the end?

The guide asks to identify, from workshop 1, the person responsible for accepting the residual risks at the end of the study [2]. ANSSI sums it up: technical tools do not decide, the leader does, informed by the collective work of the teams [1].

### How does EBIOS RM compare with the NIST approach?

EBIOS RM states that it is compatible with the ISO 31000:2018 series of risk management standards and with the ISO/IEC 27000 series, notably ISO/IEC 27005:2022 [1]. It applies to public and private organizations alike [2]. NIST, for its part, publishes Special Publication 800-30 Rev 1, "Guide for Conducting Risk Assessments", released on 17 September 2012. It provides guidance for conducting risk assessments of federal information systems and organizations, in three steps: preparing for the assessment, conducting it, and maintaining it [4].

## What it changes for employees

If you are invited to a workshop, your role depends on the stage.

- In workshop 1, say what in your activity would be serious if it were lost, altered, disclosed or unavailable. The guide classifies these impacts by availability, integrity, confidentiality and traceability [2]. Also specify from what point unavailability becomes serious: the guide recommends stating beyond what loss of service the severity level is reached, with an unavailability of more than 2 hours as an example [2].
- In the later workshops, point out the service providers and partners who have access to your tools or your data, since the stakeholders of the ecosystem are examined in workshop 3 [1].
- After the study, accept the follow-up: each measure has an owner and a deadline, and monitoring over time feeds continuous improvement [1].

Two precautions help avoid aiming at the wrong goal. In workshop 1, the point is not to list everything: the objective is not exhaustiveness but to keep the essential or sensitive business values, so as to keep the study agile [2]. And to prepare, ANSSI offers a free MOOC [1] that presents the fundamentals: identifying the values to protect, defining threats, qualifying how dangerous the ecosystem is, building realistic scenarios and proposing suitable measures. It does not replace training in the method [3].

## What it changes for management

Management sits in the workshops with the business teams, the RSSI and the DSI [1]. It also has decisions to make at specific moments.

- From the first workshop, the durations of the strategic cycle and of the operational cycle are defined [1]. For the accreditation of an information system, the guide commonly cites three years for the strategic cycle and one year for the operational cycle [2].
- In workshop 3, the team defines security measures on the ecosystem (suppliers, service providers, partners). They may require arbitration by management [1].
- In workshop 5, risks are ranked on three levels: low (acceptable as is), medium (tolerable under control) and high (corrective measures to be undertaken in the short term) [1]. Each measure in the action plan receives an owner, a deadline and an estimate of cost or complexity [1].
- At the end of the study, the person responsible for accepting residual risks, identified in workshop 1, accepts them [2].

## What the text says

ANSSI's guide starts from the highest level, the main missions of what is being studied, and moves down progressively to business and technical functions by studying risk scenarios [2]. It combines two approaches. Compliance deals with the most common risks, including those linked to accidental and environmental events. Scenarios are used to spot advanced risks of intentional origin, notably highly targeted or sophisticated attacks [2].

The work is done in five workshops, grouped into two cycles. The strategic cycle revisits the whole study. The operational cycle goes back over the operational scenarios in light of incidents that have occurred, new vulnerabilities and the evolution of attack methods [2].

To follow the workshops, take the guide's fictional company, a biotechnology firm that makes vaccines [2].

- Workshop 1, scoping and security baseline: the scope is set, the business values and feared events are listed, and the gap with the security baseline is measured, meaning the basic measures and mandatory rules [1]. The guide recommends keeping to 5 to 10 business values [1]. In the example, research and development is one of them, and interruption of vaccine production or distribution for more than a week during an epidemic peak is among the feared events [2]. Their severity is rated on a scale from G1 (minor) to G4 (critical, the survival of the company is threatened) [2].
- Workshop 2, risk sources: who could target these values, and with what aim? Pairs of "risk source / targeted objective" are selected (cybercriminals, competitors, activists), assessed by their motivation, resources and activity. Three to six pairs are generally a sufficient basis [1].
- Workshop 3, strategic scenarios: the ecosystem is mapped. Some stakeholders can serve as an entry point, not through malice but because of their privileged access. The guide recommends one to three attack paths per pair [1].
- Workshop 4, operational scenarios: the paths become concrete attack methods on the critical supporting assets. A successful attack often combines several weaknesses, technical, organizational or physical [1]. The workshop 4 method sheet proposes a sequence in four phases: know, enter, find, exploit [5].
- Workshop 5, risk treatment: risks are placed on a severity/likelihood map and receive an action plan [1].

The guide insists on one point: the method is an adaptable toolbox, whose level of detail and sequencing vary according to the subject, the deliverables, the knowledge of the scope and the sector [2]. It is therefore not a fixed recipe.

## Where implementation stands

The EBIOS RM guide is published by ANSSI. Its online presentation page carries the date of 18 November 2019, and the method sheets that help conduct each workshop are regularly updated [6]. The ANSSI page presenting the method shows an update on 6 October 2026 [1].

The method applies to public and private organizations, whatever their size or sector, whether their information systems already exist or are being developed [1]. The guide offers a grid of uses that crosses the workshops to conduct first with the objective of the study: identifying the security baseline, carrying out a compliance exercise, assessing the threat level of the ecosystem, running a full study with a view to accreditation, steering an audit or a penetration test, or steering the detection and response arrangements of a SOC [1].

The method sheets have limits. They serve to identify points of attention and are not meant to replace ANSSI's technical guides, security policies or regulations in force [5].

## Sources

1. ANSSI, "EBIOS Risk Manager : méthode, ateliers et formations". https://aide.messervices.cyber.gouv.fr/fr/article/ebios-risk-manager-realiser-une-analyse-de-risques-cyber-15p6xo1/ (accessed 14 November 2026)
2. ANSSI, "Guide EBIOS Risk Manager (collection Gestion des risques cyber)". https://messervices.cyber.gouv.fr/documents-guides/250129_np_anssi_guide_ebios_fr_final_collection_WEB.pdf (accessed 14 November 2026)
3. ANSSI, "MooC EBIOS RM". https://messervices.cyber.gouv.fr/services/mooc-ebios-rm (accessed 14 November 2026)
4. NIST, "Guide for Conducting Risk Assessments", 17 September 2012. https://www.nist.gov/publications/guide-conducting-risk-assessments (accessed 14 November 2026)
5. ANSSI, "Fiche méthode Atelier 4 : construire la cartographie de menace numérique de l'écosystème". https://messervices.cyber.gouv.fr/documents-guides/Fiche_methode-Elaborer_des_graphes_d_attaque-atelier_4.pdf (accessed 14 November 2026)
6. ANSSI, "EBIOS Risk Manager: The method", 18 November 2019. https://messervices.cyber.gouv.fr/guides/en-ebios-risk-manager-method (accessed 14 November 2026)

---

Original source: Cyberpedia, the public cybersecurity and AI encyclopedia published by Brain. Canonical version: https://startbrain.io/cyberpedia/en/articles/ebios-risk-manager-risk-analysis-anssi/
You may reuse this text freely under the CC BY 4.0 license (https://creativecommons.org/licenses/by/4.0/), provided you credit "Brain, Cyberpedia" with a link to the canonical URL above.
