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

# Let's recap

<table data-view="cards"><thead><tr><th>Step</th><th>Title</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Designate a lead and set up governance</td><td>Risk management requires a dedicated person or team. The task can be long and tedious, so entrust it to someone who knows how the organization works.</td></tr><tr><td>2</td><td>Record past events</td><td>Take stock of past events, which will let you assess risks on the basis of real facts.</td></tr><tr><td>3</td><td>Configure the risk scale</td><td>Set your risk scale and the conditions applicable to each level.</td></tr><tr><td>4</td><td>Define control points</td><td>Take stock of your organization's security measures and objectives. You can draw inspiration from the measures recommended in ISO 27001 (for IT security risks).</td></tr><tr><td>5</td><td>Identify risks</td><td>Start with the risks to your most critical assets.</td></tr><tr><td>6</td><td>Create a risk type</td><td>Identify dreaded events, threats, sources, etc.</td></tr><tr><td>7</td><td>Assess the risk</td><td>The assessment covers the initial risk (the theoretical risk associated with the activity, before any control measure) and the residual risk (the risk remaining after the implementation of control measures).</td></tr><tr><td>8</td><td>Treat the risk</td><td>Depending on the response, the control system may include the implementation of control points.</td></tr><tr><td>9</td><td>Monitor the risk</td><td>A risk must live with the activity it covers. Monitor its changes on a regular basis.</td></tr></tbody></table>


---

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