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

# 3. Treat

Learn how to treat risks in Dastra.

The treatment step is the response given to the identified and assessed risk. In the risk page, it is the **Risk response** section.

Choose an option in the **Risk response type** field:

* **Mitigation and controls**: measures must be implemented to reduce the risk;
* **Acceptance**: the organization accepts the raw risk as it stands, without reduction measures;
* **Avoidance**: the risk prevents the activity in question from being carried out;
* **Transferance**: the risk weighing on the organization is transferred to another organization, for example through insurance;
* **Take risks**: the risk should be subject to reduction measures, but the organization agrees not to implement them.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-b5b4cff4cc80bc90f49ac92e1b4cc99256c42f36%2Frisks-treat-1.png?alt=media" alt="Risk response section with the five response options and the response justification"><figcaption><p>The Risk response section</p></figcaption></figure>

Explain your choice in **Response justification**, then click **Validate response** to move to the **Monitoring** step. This decision belongs to the risk owner: only the owner can validate the response.

{% hint style="info" %}
Only the **Mitigation and controls** option relies on control points and on the remediation rate, which move the current risk. For the other options, Dastra does not calculate a remediation rate.
{% endhint %}


---

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