> 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/gdpr/risks/processors.md).

# Vendor risk management

Learn how to manage the risks of working with processors under the GDPR.

The requirements of the GDPR extend to processors, the vendors that process personal data on your behalf.

## Contract

The contract with a processor must specify the subject matter, the duration, the nature and the purpose of the processing, the type of personal data, the categories of data subjects, and the obligations and rights of the controller. It must also set out the processor's data protection obligations (Article 28).

## Audit

The processor must allow audits by the controller, so that the controller can check that the processor complies with the contractual data protection clauses. The processor must also process the personal data only for the purposes set out in the processing contract and on documented instructions from the controller.

## Supervision of the processing chain

The processor does not engage another processor (a sub-processor) without the prior written authorization of the controller, which may be specific or general. With a general authorization, the processor informs the controller of any intended change so that the controller can object. Any contract with a sub-processor must impose the same data protection obligations as the contract with the controller.

## Processor record

Each processor must keep a record of the categories of processing carried out on behalf of each controller. The processor makes this record available to the supervisory authority on request (Article 30).

## Liability of the processor

The processor is liable for damage caused by processing only where it has not complied with GDPR obligations specifically directed to processors, or where it has acted outside or contrary to the controller's lawful instructions (Article 82). A processor can also be fined for breaching its own obligations (Article 83).

## Go further

{% content-ref url="/pages/zGkLmYam7IP9xxLigjAY" %}
[Attach a risk to a processing activity](https://doc.dastra.eu/en/features/risks/attach-to-processing.md)
{% endcontent-ref %}

{% content-ref url="/pages/7M96jDyzKR0VEEQbvTU4" %}
[Step 3: Managing risks](https://doc.dastra.eu/en/getting-started/tutorial/step-3.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/gdpr/risks/processors.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.
