> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/compliance/library/risks.md).

# Risks

The risk library helps identify, qualify and track the risks associated with the requirements and controls defined in compliance frameworks.

In Dastra, a risk represents a **feared event** that may have a negative impact on the organization, in relation to the use, development or operation of systems (e.g. AI systems).

Risks are a **key steering element**: they make it possible to measure the organization's exposure and to assess the actual effectiveness of the controls that are in place.

***

## Risks and controls: a central relationship

**Risks are never isolated.**

In Dastra:

* a **risk is covered by one or more controls**
* a **control contributes to reducing one or more risks**

Controls therefore constitute the **risk mitigation measures**.\
They make it possible to reduce:

* the **likelihood** of the risk occurring,
* and/or its **impact** on the organization.

This relationship makes it possible to move from a declarative approach to **operational risk management**, based on concrete and verifiable actions.

***

## Risk library view

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-2e63f6fca2124a75f87932e7975d8a588e6356bb%2Fimage-497.png?alt=media" alt="Risk library with the list of risks"><figcaption></figcaption></figure>

The risk library provides a global view of the identified risks, including in particular:

* their reference and description,
* the associated tags (confidentiality, performance, robustness, etc.),
* the initial impact and likelihood levels,
* filters to facilitate cross-cutting analysis.

This view makes it possible to:

* identify the major risks,
* verify their coverage by controls,
* prioritize compliance efforts.

***

## Creating and describing a risk

{% columns %}
{% column %}

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-75669b3c8bd3bc11a0f4446aa1dae53dfa2f56ae%2Fimage-498.png?alt=media" alt="Risk edit window with the name, the reference, the description and the assessment"><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}
When creating or editing a risk, the user provides:

* **the name and reference of the risk**
* a **description** used to qualify the risk scenario
* **tags** to facilitate categorization
  {% endcolumn %}
  {% endcolumns %}

***

## Risk assessment

Each risk is subject to two entered assessments, the initial risk and the residual risk, plus one calculated level, the current risk:

### Initial risk

The **initial risk** corresponds to the risk level **before the controls are implemented**.

It is assessed according to:

* a **likelihood**
* an **impact**

These two dimensions are positioned on a standardized **risk grid**.

***

### Residual risk

The **residual risk** corresponds to the risk level **after the associated controls are applied**.

Comparing the initial risk and the residual risk makes it possible to:

* measure the effectiveness of the controls,
* visualize the reduction of the risk,
* justify remediation choices.

At this stage, the **risk grid is fixed** and common to all risks, in order to guarantee a homogeneous and comparable assessment.

***

### Current risk

In a project, Dastra also shows the **current risk**. It represents the level of risk at a given point in time, based on the actual progress of remediation actions and controls. It therefore evolves between the initial risk and the residual risk.

The three levels are visible side by side in the **Cartography** view of the **Risks** tab of a project (see [Project implementation](https://doc.dastra.eu/en/features/compliance/projects/implement.md)).

***

## Associating controls

{% columns %}
{% column %}
A risk must be associated with one or more **controls**, which represent the measures implemented to mitigate it.

The association makes it possible to:

* clearly identify the levers for reducing the risk,
* track the impact of the controls on the residual risk,
* ensure traceability between compliance and risk management.
  {% endcolumn %}

{% column %}

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e595f1ef7e2ac66470be991a37a11ed99bd4bd4f%2Fimage-499.png?alt=media" alt="Search for controls to associate with a risk"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

## Associating threats

Risks can also be linked to **threats**, which represent the **events or causes** likely to trigger the risk.

Example:

* **Threat**: lack of monitoring of AI logs
* **Risk**: information leakage through AI queries

This distinction allows a finer and more structured analysis of risk scenarios.

***

## Merging risks

As with controls and tests, the risk library can contain duplicates. Select at least two risks, then click **Merge** in the bulk actions, or **Merge** in the edit window of a risk. The wizard is the same as for controls: choose the **reference version** and the fields to carry over (see [Controls](https://doc.dastra.eu/en/features/compliance/library/controls.md)). The merge is irreversible.

***

## Why include risks in the library

Centralizing risks in the library makes it possible to have:

* a cross-cutting view of risks across all frameworks
* better consistency in their assessment
* a direct link between risks, controls and requirements
* more effective steering of compliance and security


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.dastra.eu/en/features/compliance/library/risks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
