> 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/getting-started/tutorial/step-3.md).

# Step 3: Managing risks

Risk management in Dastra can take several forms:

* the data protection impact assessment (DPIA),
* risk identification and assessment (with the Risks module),
* audits.

## The impact assessment

If you have identified personal data processing activities likely to result in a high risk to the rights and freedoms of data subjects, you must carry out a [data protection impact assessment](https://www.cnil.fr/en/privacy-impact-assessment-pia) (DPIA) for each of them.

{% hint style="info" %}
Carrying out a DPIA is mandatory for any processing likely to result in a high risk to the rights and freedoms of data subjects (Article 35 of the GDPR).
{% endhint %}

To help you determine whether your processing is likely to result in a high risk, the following 9 criteria are defined in the guidelines of the Article 29 Working Party:

1. evaluation or scoring;
2. automated decision-making with legal or similarly significant effect;
3. systematic monitoring;
4. sensitive data or data of a highly personal nature;
5. personal data processed on a large scale;
6. matching or combining datasets;
7. data concerning vulnerable data subjects;
8. innovative use or application of new technological or organizational solutions;
9. exclusion from a right, a service or a contract.

These criteria are built into the workflow for creating a processing activity: for each one, you indicate whether a DPIA must be carried out.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0af333e0bf1ef8b15bccd56bc228443139574109%2Fgetting-started-tutorial-1.png?alt=media" alt="Impact assessment step of a processing activity, with the 9 criteria and the button to generate the assessment"><figcaption><p>Example of a processing activity that potentially requires a DPIA</p></figcaption></figure>

## Risk identification and assessment

Dastra's Risks module lets you manage risks at the level of your processing activities, your stakeholders (for example processors) and your assets.

The risk management methodology complies with standard information system risk management requirements. It has four steps:

1. risk identification;
2. risk assessment;
3. risk response;
4. risk monitoring.

In general, risk is measured as follows:

$$
Risk = Probability \* Impact
$$

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

## Audits

To go further in risk management, Dastra also lets you design audits, run campaigns and collect the results as an exportable audit report.

{% content-ref url="/pages/RY7aouLcykTlhn7qY0o2" %}
[Questionnaires](https://doc.dastra.eu/en/features/questionnaires.md)
{% endcontent-ref %}

Your risks are identified and assessed. Move on to step 4, task prioritization:

{% content-ref url="/pages/djLnRzZWpQ7yCg9aHpKJ" %}
[Step 4: Prioritize actions](https://doc.dastra.eu/en/getting-started/tutorial/step-4.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/getting-started/tutorial/step-3.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.
