> 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/incidents/as-processor.md).

# Incidents as a processor

Manage data breach incidents in which your organization acts as a processor under the GDPR.

The Incidents module of Dastra adapts to your organization's role in the incident: controller or processor. This role determines the applicable obligations and which steps are displayed in the form.

## Declare your role at creation

When you create an incident, the dialog asks **In the case of this data breach, are you a sub processor?**, with two answers:

* **No** (the default): you handle the incident as a controller. The flow is the standard one: notification to the supervisory authority, communication to the data subjects, risk assessment.
* **Yes**: you handle the incident as a processor. You do not have to notify the supervisory authority directly: that is the controller's responsibility.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-4a096a2ed7fb53a1c4f4a4fca7809fe2838ff302%2Fviolations-create-subprocessor.png?alt=media" alt="Create an incident dialog with the processor question, Yes selected"><figcaption><p>At creation, indicate whether your organization acts as a processor</p></figcaption></figure>

To create the incident step by step, see [Document a new data breach](https://doc.dastra.eu/en/features/incidents/document-breach.md).

{% hint style="info" %}
Article 33(2) of the GDPR: the processor notifies the controller of any personal data breach without undue delay after becoming aware of it. The processor has no obligation to notify the supervisory authority directly: that obligation rests with the controller.
{% endhint %}

## Differences in the form

When you answer **Yes** to the role question, the form changes as follows:

| Element                                       | Controller                         | Processor                                                                |
| --------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------ |
| **Notification** step (supervisory authority) | Shown                              | Hidden                                                                   |
| **Communication** step                        | Communication to the data subjects | Communication to the data controllers, with the **Data controllers** tab |

The other steps stay the same. In the **Risk assessment** step, a reminder tells you to inform the relevant controllers of the required actions so that they can act accordingly.

In the record, the **Type** filter tells incidents handled as a processor from those handled as a controller, and the **Reporting** page shows the **Role breakdown**.

## Communicate to the data controller clients

The **Communication** step of a processor incident has two tabs.

In the **Communication** tab, answer **Did you notify the relevant data controller(s)?** with **Not applicable**, **Yes** or **No**. With **Yes**, click **Add a communication** to record each message with its date. With **No**, give the reasons in **Why have you not notified the relevant data controller(s)?**.

The **Data controllers** tab lists the client controllers affected by the incident. You can:

* attach a controller with **Attach Data Controllers**;
* import the controllers automatically with **Sync Data Controllers**;
* tick **Communication sent** and **Authority notified** for each one;
* export the list with **Export list**, for your compliance file.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-c1376300300eba7163d7acee82feaad588535c98%2Fincidents-as-processor-1.png?alt=media" alt="Communication step of a processor incident, Data controllers tab"><figcaption><p>The Data controllers tab, with the Attach Data Controllers, Sync Data Controllers and Export list actions</p></figcaption></figure>

### Synchronize the data controllers

If processing activities are linked to the incident (**Data processing** step), Dastra finds the client controllers from those activities and adds them to the list. Click **Sync Data Controllers** to start it. If no processing activity or AI system is linked yet, Dastra asks you to link some first.

## Best practices

* Notify your client controllers as soon as you become aware of the incident. The GDPR sets no fixed deadline for the processor, unlike the 72 hours the controller has to notify the authority, but a quick response is essential.
* Record the date and time of each communication sent to the controllers.
* Keep the acknowledgements and replies in the **Documentation** step of the incident.


---

# 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/incidents/as-processor.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.
