> 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/nl/features/compliance/library.md).

# Bibliotheek

De bibliotheek bundelt alle conformiteitsobjecten van Dastra.

De bibliotheek is de gemeenschappelijke basis waarop kaders, conformiteitsprojecten en risicobeheer worden gebouwd.

{% columns %}
{% column %}
In de bibliotheek maakt en beheert u:

* kaders (conformiteitskaders) en hun vereisten,
* controles, de centrale elementen die vereisten, tests en risico's met elkaar verbinden,
* tests waarmee de controles worden geverifieerd,
* en de bijbehorende risico's en bedreigingen.
  {% endcolumn %}

{% column %}

<figure><img src="https://996651476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1i0NSpf8ID0PXTpIyycA%2Fuploads%2Fgit-blob-ff1153b02bd81fb0fd46cdd96a1e228680278481%2Fcompliance-library-nav-menu-1.png?alt=media" alt="Zijmenu van de conformiteitsbibliotheek"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

Dankzij de bibliotheek pakt u conformiteit transversaal en herbruikbaar aan: één controle kan meerdere vereisten dekken, over meerdere kaders heen worden gedeeld en met gestandaardiseerde tests worden beoordeeld. Die centralisatie vergemakkelijkt de governance, verbetert de consistentie van de kaders en geeft een globaal overzicht dankzij specifieke indicatoren en statistieken.


---

# 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/nl/features/compliance/library.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.
