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

# Project implementation

The implementation phase marks the transition from the theoretical framework to the operational execution of compliance.

The **Implementation** phase marks the transition from the theoretical framework to the operational execution of compliance. It consists of **configuring the controls concretely**, defining the verification methods and preparing the collection of evidence.

At this stage, the project already has:

* its frameworks,
* its controls,
* its tests and risks initialized during the design phase.

***

## Objective of the phase

The objective of the implementation phase is to:

* define **how the controls are verified**,
* configure the **tests (manual or automated)**,
* associate the **risks with the controls**,
* prepare the **collection of compliance evidence**.

***

## 1. Understanding the status of tests during the implementation phase

By default, all the project's tests are in the **"Missing evidence"** status.

This means that:

* the control exists,
* the test is defined,
* but **no evidence has yet been provided or collected**.

As long as the project is not in the **Monitoring** phase, modifying or validating the evidence is not recommended: Dastra shows a warning, without blocking you.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-61ddcced46fbda96c3a0f4a7b3002467d84850ed%2Fimage-458.png?alt=media" alt="Details of a project test with its Missing evidence status"><figcaption></figcaption></figure>

The **Context** tab of the test details shows where the test comes from: the **Project** (name, status, description and **Frameworks**) and its **Scope**.

***

## 2. Configuring compliance tests

Each control can be verified using one or more **tests**.

{% columns %}
{% column %}
A test allows you to define:

* a **verification procedure**,
* an **execution frequency** (e.g. monthly, quarterly, annually),
* a **test owner**.

Tests can be:

* **manual**, requiring a human action and evidence,
* or **automated**, via a Dastra or custom connector.
  {% 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-c2a4301511944c52b1bb596b25a8dd9226bc031e%2Fimage-459.png?alt=media" alt="Installing a connector on a test"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

## Control status and exclusion

Each control of the project has a **Control status**, which you can change in the list of the **Controls** tab or in the control window:

| Status          | Meaning                                                                                                                     |
| --------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Draft**       | The control is identified but not implemented yet. It is counted among the not implemented controls.                        |
| **Implemented** | The control is in place. This is the status of controls imported with a framework. It is validated when all its tests pass. |
| **Excluded**    | The control does not apply to the project.                                                                                  |

To exclude a control, choose **Excluded**: the **Justify control exclusion** dialog opens. Enter the reason in **Explain why this control should be excluded** (2,000 characters at most). The justification is optional in this dialog, but you should fill it in: it is shown on the control and during audits, and carried into the statement of applicability, where an excluded control is marked as not applicable (see [Compliance monitoring](https://doc.dastra.eu/en/features/compliance/projects/monitoring.md)).

An excluded control is no longer assessed: during an audit, the justification is shown instead of its tests. Adding an excluded control to the project again, in bulk, reactivates it.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-ee362a17d7893226ccd278f7ad6783b0ce342229%2Fcompliance-project-control-exclusion-1.png?alt=media" alt="Justify control exclusion dialog with the explanation field"><figcaption></figcaption></figure>

***

## Assign an owner to all the controls and tests of a requirement

In the **Requirements** tab of the project, the users button to the right of a requirement opens the **Assign owner to all controls and tests** dialog. It saves time at the start of implementation, before the **Assign owners to tests** checklist step.

1. Click the button of the requirement concerned. The action applies to the requirement and its sub-requirements.
2. In **Select a user to assign as owner**, choose the person.
3. Turn on **Overwrite existing owner assignments** if you want to replace the owners already defined. Otherwise, only items without an owner are filled in.
4. Click **Validate**.

Write access to operational compliance is required.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-aec4ffe002b09066a07b5b687c1d8bdf12714820%2Fcompliance-project-mass-assign-owner-1.png?alt=media" alt="Assign owner to all controls and tests dialog with the user selection and the overwrite option"><figcaption></figcaption></figure>

***

## 3. Associating and assessing risks

Controls can be linked to one or more **risks** in order to measure their impact on risk reduction.

For each risk, you can:

* define an **initial assessment** (probability × impact),
* define a **residual assessment**, after the controls are applied,
* choose the **risk treatment** (reduction, acceptance, etc.).

This approach makes it possible to concretely visualize the effect of the controls on the risk posture.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-86483127e4a5ba76c8389915762476fd6ed7bd88%2Fimage-461.png?alt=media" alt="Details of a project risk with the initial and residual assessment"><figcaption></figcaption></figure>

### Visualize risks on a map

In the **Risks** tab of the project, the selector above the list switches between the **Table** view, which lists each risk with its scores, and the **Cartography** view, which places the risks on a probability × impact matrix.

The **Cartography** view shows three matrices side by side:

* **Initial risk**: the level assessed when the risk was identified, before any remediation measure;
* **Current risk**: the level at a given point in time, based on the actual progress of remediation actions and controls;
* **Residual risk**: the level expected once all planned measures are implemented, that is, the risk accepted or tolerated by the organization.

Filter by **Framework** to see only the risks of one framework, click a risk to open it, or click **Print** to print the page. Reading risks as both a table and a map makes it easier to prioritize risks and to communicate them to stakeholders.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f7e26f617c79807c5f88e52c203ed191a4af1ec4%2Fcompliance-project-risks-cartography-1.png?alt=media" alt="Cartography view of the risks of a project with the Initial risk, Current risk and Residual risk matrices"><figcaption></figcaption></figure>

***

## 4. Linking threats, risks and controls

**Threats** represent the concrete scenarios that can trigger a risk\
(e.g. injection of malicious data, lack of supervision, information exfiltration).

A threat can be:

* linked to one or more **risks**,
* indirectly covered by the **controls** put in place.

This chaining allows complete traceability:\
**Threat** > **Risk** > **Control** > **Test** > **Evidence**

***

## 5. Installing a connector to automate evidence

For certain tests, it is possible to install a **Dastra connector** in order to automate the collection of evidence.

Connectors make it possible, for example, to:

* verify the presence of a policy or a contract,
* query a registry (AI systems, assets, incidents, processing activities, third parties) or the audits,
* automate recurring controls without manual action.

The list of connectors and their configuration are described in [Tests](https://doc.dastra.eu/en/features/compliance/library/tests.md).

Each connector is configured with:

* an **execution frequency**,
* **collection parameters** adapted to the test.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0e6fd0d89391e76bbf899e875481fc08f1cbe04b%2Fimage-462.png?alt=media" alt="List of the connectors available to install"><figcaption></figcaption></figure>

***

## 6. Result of the implementation phase

At the end of the implementation phase:

* the **controls are configured**,
* the **tests are ready to be executed**,
* the **risks are assessed and linked**,
* any **connectors are installed**.

The project is then ready to enter the next phase: **Monitoring**, during which:

* the tests are executed periodically,
* the evidence is collected,
* and compliance is measured over time.

## Export the project lists

The **Controls**, **Tests** and **Risks** tabs of a project each have an **Export** button. It exports the list as it is displayed: the active filters apply. In the export window, choose the format (CSV, Excel or JSON) and the columns to include, then click **Download file**.

The button requires the permission to export the operational data of the compliance module. Without it, it is disabled.


---

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