> 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/risk-management/attach-a-risk-to-a-processing-activity.md).
# Attach a risk to a processing activity
Dastra makes it possible to map the risks linked to data processing in order to quickly assess the level of priority and the actions to be taken on a data processing.
## Adding a risk to a processing of data
To add a risk to a processing of data, go to the risks tab on the processing of data edit page.
and click on the "Create a risk assessment" button.
You will be taken to a risk edit page and you can start to fill in the information about the risk you have identified.
You can then find all the risks in your register in the risk repository.
You can also attach a risk to a treatment directly from the risk management module.
To do this, simply go to the "Risks" tab and "create a risk assessment".
## Visualising the risks of a processing
To view the risks on processings, it is necessary to go to the Dastra Risks module.
You have to go to the "Risks" tab and you will have a visualization of all the risks sorted according to the elements related to each risk.
## Risk assessment
The risk level is calculated according to the following formula :
```
Risk level = probability value X impact value
```
In the dashboard, a risk module shows the number of risks, the processings with the highest risks, the overall risk and the level of the processing with the highest risk.
The overall risk is calculated according to the following formula:
```
sum (probability* impact ) / number of risks
```
The level of the processing with the highest risk is calculated according to the following formula:
```
((impact x probability) / 25)
```
## Go further
{% content-ref url="/pages/-Lw3hALWsjvX2sseOt14" %}
[Planning](/en/features/planifier.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/risk-management/attach-a-risk-to-a-processing-activity.md?ask=&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.
