> 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/ropa/activity/security.md).

# Security measures

Describe the security measures that protect the data of the processing activity.

[**Article 30 1. g) of the GDPR**](https://gdpr-info.eu/art-30-gdpr/) requires the record to include, "*where possible, a general description of the technical and organisational security measures referred to in* [*Article 32(1)*](https://gdpr-info.eu/art-32-gdpr/)".

Under [**Articles 5 1. f)**](https://gdpr-info.eu/art-5-gdpr/) and [**32**](https://gdpr-info.eu/art-32-gdpr/) of the GDPR, every data controller and processor must ensure the security of the data with measures appropriate to the level of risk.

What is a security measure? Any measure necessary to ensure the security and confidentiality of personal data. It can be, for example, a physical security measure, such as controlled access to the premises, or an IT security measure, such as an antivirus or a strong password policy for accessing the data.

For each processing of personal data, you must take the appropriate measures to ensure a level of security appropriate to the risk for the rights and freedoms of the data subjects (invasion of privacy, discrimination, etc.). The risk must not be assessed from the point of view of the company, but from the point of view of the data subjects.

Ensuring security means ensuring the confidentiality, integrity and availability of the data. Security measures must therefore prevent unauthorized access to the data, unwanted modification of the data and loss of the data.

For the measures to be appropriate to the risk, the risks must be assessed: identify the potential impacts on data security, the risk sources and the possible threats, and assess whether the existing measures are sufficient. If they are not, strengthen them.

## Add security measures to the processing activity

Security measures are entered in the **Measures** section of the processing activity.

1. In the **Measures** section, click **Attach security measure** and select the measures that apply to the processing activity.
2. If a measure does not exist yet, click **New security measure** to create it.

The measures are listed with their type (for example **Technical**, **Organizational**, **Physical** or **People**). For each measure, you can describe how it is applied to this processing activity in the **Specific details about the implementation in this processing** field.

Click a measure to view or edit it. From the **...** menu, you can also **Edit** it, open **More info** when a reference link is available, or **Delete** it from the processing activity.

{% hint style="info" %}
The security measures of an asset can also be added to the processing activity when you sync the asset's data from the [Assets](https://doc.dastra.eu/en/features/ropa/activity/assets.md) section.
{% endhint %}

## Deployment status of the measures

Each security measure linked to the processing activity has a deployment status: **Non applicable**, **To be done**, **Planned**, **Being deployed** or **Deployed**. A measure added to the processing activity is set to **Deployed** by default.

Change the status of a measure from its row in the list of measures, or apply the same status to all the measures of the processing activity at once with the **Status** selector in the header of the list.


---

# 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/ropa/activity/security.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.
