> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/en/maatregelen.md).

# Controls

Controls in ControlBee form the basis for compliance. By linking evidence to a Control, compliance can be demonstrated. Controls arise from requirements, objectives and risks.

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-d4b419766813af2db7ba6358ceb6b74bf87567a6%2Fmaatregelen-01.png?alt=media" alt="Overzicht maatregelen"><figcaption></figcaption></figure>

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-97af2d1b7c260ee942bd374b5d9ad5867b85ee76%2Fmaatregelen-02.png?alt=media" alt="Overzicht maatregelen"><figcaption></figcaption></figure>

## Controls overview

Here the user finds an overview of all Controls that have been created or imported. In the overview, you can see per Control whether the Control applies, under which process the Control is linked, and what the current status of the Controls is.

Controls can be easily found by entering a search term or by filtering the Controls by control status, source and labels.

## Creating Controls

When creating a Control, the user gives the Control a number and indicates from which source this Control comes, for example from ISO 27001. Next, the Control is given a name, for example: Privacy and protection of personal data, and a description, for example: Privacy and protection of personal data must, insofar as applicable, be ensured in accordance with relevant laws and regulations. Then it can be indicated whether the Control is applicable and why it is applicable.

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-205e633ffcf0468e98a6806a16d795a63dcf6705%2Fmaatregelen-03.png?alt=media" alt="Aanmaken maatregelen"><figcaption></figcaption></figure>

## Importing and exporting Controls

The user can also add multiple Controls at once by importing an xlsx file with all Controls. This can for example be the entire ISO 27001 standard. In addition, the Controls can be edited and exported in xlsx format. When exporting Controls, all Controls can be exported, but also only the filtered Controls.

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-0454e6d1a6bd1362006c3eb904258fc858242582%2Fmaatregelen-04.png?alt=media" alt="Importeren en exporteren maatregelen"><figcaption></figcaption></figure>

## Archiving Controls

Controls can be archived. To do this, select the Controls you want to archive as a user, and then use the 'archive' button. The Controls are then placed in the archive, which means that audit findings are retained, but the Controls are no longer visible to users. This function can be used once a new version of a standard is available and the old version is therefore no longer applicable.

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-9498d9ba82a1c471a2b40906502742ecf1a915b8%2Fmaatregelen-05.png?alt=media" alt="Archiveren maatregelen"><figcaption></figcaption></figure>

## Deleting Controls

From the archive, it is possible to restore Controls, but also to permanently delete Controls.

{% hint style="warning" %}
Note: if Controls are removed from the archive, all audit findings of the relevant Control(s) are also removed.
{% endhint %}

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-ac5c0a976470f96700f7dd43d44f70a3efebcca9%2Fmaatregelen-06.png?alt=media" alt="Verwijderen maatregelen"><figcaption></figcaption></figure>

<figure><img src="https://3156569376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGr73dCEp7VK8XigZ4lH9%2Fuploads%2Fgit-blob-afe626783f2723c0a31ed921a410a7b588da84e1%2Fmaatregelen-07.png?alt=media" alt="Verwijderen maatregelen"><figcaption></figcaption></figure>

## Linking: Controls, requirements, objectives, risks and processes

Controls arise from requirements, objectives and/or risks; these links can be made among each other. Think of Control 'A.7.2.2 Awareness, education and training regarding information security', which can be linked to a requirement 'Accredited ISO 27001 certification', to an objective 'Promoting awareness among employees', or to a risk 'Low awareness of information security among employees'. In addition, Controls are carried out in processes and Control 'A.7.2.2' can be linked to the process 'Personnel'.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.controlbee.nl/en/maatregelen.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
