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

# 4. Monitor

Learn how to monitor risks in Dastra.

Once the risk is treated, make sure it is followed over time and spot any change. In the risk page, the **Monitoring** step is named **Treated** when the response type is **Mitigation and controls**; for another option, it carries the name of that option.

## Follow the control points

With the **Mitigation and controls** option, the section shows two indicators: the **Completion** as a percentage and the **Score** in points out of the maximum. Control points are grouped by influence: those that reduce severity and those that reduce likelihood, each with its percentage.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-313c76468a728242036f6cc98c9b20717b2a3675%2Frisks-monitor-1.png?alt=media" alt="Monitoring step of a risk: completion, score and control points grouped by severity and likelihood"><figcaption><p>The control points of a risk and its remediation</p></figcaption></figure>

1. Click **Assign control points** to choose the control points of the risk type.
2. On the control point concerned, click **New questionnaire**.
3. Choose the answer, enter the **Implementation date**, and add a description and files in **Send implementation proofs** if needed.
4. Click **Submit response**.

Every response is kept: the **Activity history** button of the control point lists them, and the most recent one is the current response. If the control point is assessed on a recurring basis, Dastra notifies you when the chosen number of days has elapsed.

## Effect on the current risk

After each new response, Dastra recalculates the remediation rate, then the current risk: {Current risk} = {Initial risk} - ({Initial risk} - {Residual risk}) \* {Remediation rate}. The closer the remediation gets to 100%, the closer the current risk gets to the residual risk. The calculation is detailed in the [glossary](https://doc.dastra.eu/en/features/risks/glossary.md).

## Follow changes over time

The module **Overview** and the workspace dashboard track how risks change: average initial, current and residual risk, average remediation, number of risks per step. The heatmap shows the initial, residual or current risk. **Reporting** details the minimum, average and maximum scores per object.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-adb83468b88fe3550ac3bb3d776c05c4a87d9ca4%2Frisks-monitor-2.png?alt=media" alt="Risk overview with the indicators and the heatmap of the current risk"><figcaption><p>The risk dashboard tracks changes over time</p></figcaption></figure>

## Archive a risk

When a risk has disappeared, click **Archive the risk**. The risk moves to the **Archive** step: you can still read it, but you can no longer edit it. To put it back under monitoring, click **Cancel** in the archive section. Only the risk owner can archive a risk or cancel its archiving.


---

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