> 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/risks.md).

# Risk management

Identify, assess, treat and monitor your risks in Dastra, by organizational unit, processing activity, asset, stakeholder or AI system.

Privacy, strategic, compliance, operational, financial and vendor risks: the risk management module brings them together in a single repository. It is for DPOs, compliance teams and risk managers.

It gives you a global view of your risks to feed your remediation plans, extend your coverage and reduce your exposure.

## Risk management in Dastra in a few words

The module lets you identify, assess, treat and monitor your risks in one place, with an overview of your organization's exposure.

With Dastra, you can:

* view your risks by organizational unit, processing activity, asset, stakeholder or AI system;
* centralize the assessment, control, reporting and follow-up of remediation tasks;
* keep risk data up to date, reliable and available to the whole team.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-23718792e54fe196004c8b473bbe4feaf2ca9c7a%2Frisks-overview-1.png?alt=media" alt="Overview of the risk management module: indicators, heatmap and latest control points"><figcaption><p>The overview of the risk management module</p></figcaption></figure>

## Attach a risk

In Dastra, a risk is attached to one of the following objects:

* organizational unit;
* processing activity;
* stakeholder, for example a processor;
* asset;
* AI system.

The object types you see depend on the modules enabled in your workspace. You can assess the same risk type on as many objects as needed.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-3f81068606220595b3628880515ec3bd4f6f2638%2Frisks-list-1.png?alt=media" alt="List of the risks of the Processing activity tab, with initial, current and residual risks"><figcaption><p>Example of consolidated risk view</p></figcaption></figure>

## The module at a glance

Open **Risk management** in the sidebar. The module is visible with read access to risks; creating and editing requires write access.

| Menu entry         | Content                                                                                                                          |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| **Overview**       | The indicators (initial, current and residual risk, remediation), the heatmap, the riskiest items and the latest control points. |
| **Risks**          | The assessed risks, with one tab per object type. You create them one by one or in batch.                                        |
| **Type of risks**  | The repository of risk types: dreaded event, threats, sources, control points and pre-assessment.                                |
| **Threats**        | The repository of threats, which you reuse across risk types.                                                                    |
| **Sources**        | The repository of risk sources.                                                                                                  |
| **Control points** | The measures that reduce the risk, with their successive responses.                                                              |
| **Events**         | The history of events that occurred in the organization, with their date and financial impact.                                   |
| **Reporting**      | The initial, current and residual scores per object (minimum, average, maximum), with one tab per object type.                   |

### Risk states

Every risk goes through five steps, shown at the top of its page: **Identification**, **Assess**, **Processing**, **Monitoring** and **Archive**. Each one is described in [the risk management process](https://doc.dastra.eu/en/features/risks/process.md).

{% hint style="info" %}
Only the risk owner can change the state of a risk. The owner is shown in the **Identification** section of the risk.
{% endhint %}

### Create several risks at once

In a tab of **Risks**, open the menu of the **Create a risk** button and click **Batch risk identification**. Choose the organizational unit, the type of risk, the risk owner, the identification date and the objects concerned: Dastra creates one risk per object, with the pre-assessment of the risk type.

## Go further

{% content-ref url="/pages/uhawHsdCvyqvxrFJgKbi" %}
[Definition of risks](https://doc.dastra.eu/en/gdpr/risks/definition.md)
{% endcontent-ref %}

{% content-ref url="/pages/HZPdbZZ6lVXreOkF4RrE" %}
[Risk assessment](https://doc.dastra.eu/en/gdpr/risks/assessment.md)
{% endcontent-ref %}

{% content-ref url="/pages/zGkLmYam7IP9xxLigjAY" %}
[Attach a risk to a processing activity](https://doc.dastra.eu/en/features/risks/attach-to-processing.md)
{% endcontent-ref %}


---

# 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/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.
