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

# Controls

Controls are the central element of the Dastra compliance model.

Controls translate the requirements of a framework into **concrete measures** that are measurable and auditable, making it possible to demonstrate the effectiveness of compliance over time.

A control can:

* cover **one or more requirements**
* be shared across **several frameworks**
* be associated with **tests** and **risks**

***

## Tracking and managing controls

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-ecac45e54332f997d06c512f42ab5ab1205e9c2e%2Fimage-480.png?alt=media" alt="Controls tab of a framework with the list of controls and their remediation type"><figcaption></figcaption></figure>

Controls can be tracked from two complementary entry points.

***

### 1. From the framework

In the **Controls** tab of a framework, the user can view:

* the controls attached to the framework's requirements
* their remediation type
* the requirements covered
* the associated tests and risks

This view is useful for:

* understanding the coverage of a framework
* identifying key controls
* steering compliance by framework

***

### 2. From the control library

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-80571948f141c964d0cd06261a801d2ad126a6b7%2Fimage-481.png?alt=media" alt="Control library with the filters and the list of all controls"><figcaption></figcaption></figure>

The **control library** centralizes all of the organization's controls, across every framework.

This view makes it possible to:

* benefit from **global statistics** (controls with tests, risks, multiple associations, orphans)
* identify controls reused across several frameworks
* improve the **quality and consistency** of the control library

***

## Control editing window

{% columns %}
{% column %}
The editing window makes it possible to precisely define the role of the control and its links with the rest of the framework repository.
{% 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-403363687328676519f6706c5f7c79d9b9de7620%2Fimage-440.png?alt=media" alt="Control edit window with the name, the reference and the remediation type"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

### Control label and reference

* **Control label**\
  Clearly describes the action or measure being implemented.
* **Control reference**\
  Unique identifier of the control in the library.

{% columns %}
{% column %}
A **reference generator** is available to automatically suggest a reference that is consistent with:

* the context of the control
* the naming conventions
* the associated frameworks

The user can freely adjust the proposed reference.
{% 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-bcdfd6730a289d8da3915e73098f420b31cefbe0%2Fimage-441.png?alt=media" alt="Reference generator suggesting a consistent reference for the control"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

### Remediation type

Each control must be associated with a **remediation type**, which specifies its nature:

* **Preventive**\
  The control aims to **prevent** a risk from occurring\
  *(e.g. training, access rules, validation before going to production)*
* **Mitigation**\
  The control aims to **reduce the impact or likelihood** of a risk that already exists\
  *(e.g. monitoring, detection, mitigation plan)*

This distinction is used to:

* analyze the risk management strategy
* balance prevention and detection
* steer compliance maturity

***

### Tags

Tags make it possible to:

* categorize controls (e.g. training, AI, security, monitoring)
* make searching and filtering easier
* analyze the dominant themes of the library

***

## Associating tests

[**Tests**](https://doc.dastra.eu/en/features/compliance/library/tests.md) make it possible to verify the existence, application and effectiveness of a control.

### AI-assisted association

{% columns %}
{% 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-32cad06ef72511350d64b746de87ce840cadb5f0%2Fimage-442.png?alt=media" alt="List of the tests associated with a control"><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}
The AI assistance suggests:

* **existing tests** in the library that are relevant to the control
* the **creation of new tests** when necessary

This approach ensures:

* consistency between controls and tests
* time savings
* standardization of audit methods
  {% endcolumn %}
  {% endcolumns %}

***

## Associating requirements

{% columns %}
{% column %}
A control can be associated with:

* several requirements of the same framework
* requirements from **different frameworks**

In the **Linked requirements** section of the edit window, requirements are grouped by framework; the version number of the source framework (e.g. *Version 2*) is displayed next to its name.

This makes it possible:

* to share controls
* to link an internal control to a regulatory framework
* to create bridges between frameworks (e.g. Custom AI ↔ AI ISSP)
  {% 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-229028d2b8c6bf4ea7cb63820e82b5272bac98b1%2Fimage-443.png?alt=media" alt="Window to associate a control with requirements"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

## Associating risks

{% columns %}
{% 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-502fb29d9fbac14810ecab2e8f04ecca8a5a9fca%2Fimage-444.png?alt=media" alt="Control window with the associated risks"><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}
Controls can be associated with:

* **existing** [**risks**](https://doc.dastra.eu/en/features/compliance/library/risks.md)
* or **new risks** created directly from the control sheet

The association makes it possible:

* to view the risks covered by a control
* to assess the impact of the control on the residual risk
* to structure a consistent approach to risk management
  {% endcolumn %}
  {% endcolumns %}

***

## Merging controls

Over time, the control library may contain redundant or nearly identical controls coming from different frameworks. The **merge** feature makes it possible to consolidate them into a single reference control.

### How the merge works

From the control library or a project, select the controls to merge (up to 30), then trigger the merge via the **bulk actions**. A wizard prompts you to choose the **reference version**, that is, the control that will be kept. The associations of the other controls (evidence, requirements, risk scenarios, covered controls) are consolidated onto it, without data loss, and then the other controls are deleted.

{% hint style="info" %}
The matching is **entirely manual**: Dastra does not automatically detect duplicates. It is up to you to select the similar controls to consolidate.
{% endhint %}

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7e1561c52d631c2c17c56385903a59cba48fa5b1%2Ffusion-controles-selection.png?alt=media" alt="Selection of several controls and the bulk actions menu with the Merge option"><figcaption><p>Select up to 30 controls, then trigger the merge via the bulk actions</p></figcaption></figure>

The comparison table displays the controls side by side, one column per control. Choose the control to keep with the radio button of its column: it carries the **Reference version** label. The other columns carry the **Keep selected fields** label: only the fields you tick there are carried over to the reference version (**Select all** ticks the whole 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-308b8a58ad4a8cfa03b6c2725cb1066975885d22%2Ffusion-controles-comparaison.png?alt=media" alt="Side-by-side comparison table of the controls with selection of the values to keep"><figcaption><p>Compare the controls side by side and choose, field by field, the values to keep: evidence, requirements, risk scenarios and covered controls are consolidated onto the kept control</p></figcaption></figure>

{% hint style="warning" %}
The merge is irreversible. Check the associations of each control before confirming the operation.
{% endhint %}

### Typical use cases

* **Deduplication**: several framework imports have created equivalent controls: the merge consolidates them without loss of information.
* **Cross-cutting sharing**: a control covering both ISO 27001 and the AI Act framework can be obtained by merging the controls from each framework.
* **Library cleanup**: before an audit, removing orphaned or redundant controls improves the readability of the compliance dashboard.

***

## Summary: why controls are central

In Dastra, controls are the **point of convergence** between:

* the requirements (what is expected)
* the tests (what is verified)
* the risks (what is managed)

This approach enables:

* operational and measurable compliance
* cross-cutting governance
* reuse of compliance efforts


---

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