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

# Library

The library centralizes all of Dastra's compliance objects.

The library is the **common foundation** on which frameworks, compliance projects and risk management are built.

{% columns %}
{% column %}
From the library, you can create, structure and maintain:

* **frameworks** (compliance frameworks) and their **requirements**,
* **controls**, the central elements linking requirements, tests and risks,
* **tests** that verify the controls,
* as well as the associated **risks** and **threats**.
  {% endcolumn %}

{% column %}

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-ff1153b02bd81fb0fd46cdd96a1e228680278481%2Fcompliance-library-nav-menu-1.png?alt=media" alt="Side menu of the compliance library"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

The library enables a **cross-cutting and reusable approach** to compliance:\
a single control can cover several requirements, be shared across several frameworks and be assessed using standardized tests.\
This centralization facilitates governance, improves the consistency of frameworks and offers a global view thanks to dedicated indicators and statistics.


---

# 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/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.
