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

# Compliance monitoring

The monitoring phase is the run phase of the compliance project: evidence, test campaigns and tracking of the indicators.

The **Monitoring** phase aims to **verify the actual effectiveness of the controls over time**, collect the associated evidence and track the evolution of compliance through recurring test campaigns.

Its objective: collect evidence across the entire project using test campaigns, make sure as many controls as possible pass and maintain a level of compliance that is measurable over time.

***

## Overview of the monitoring phase

In this phase, the project shifts from a preparation logic to a **continuous execution** logic:

* the controls are already implemented,
* the tests are executed regularly,
* the evidence is collected, updated and assessed,
* the compliance indicators become usable.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d0b46a225690f0b97d9621c8d050b4dde065a19d%2Fimage-464.png?alt=media" alt="Project overview in the Monitoring phase with the control and test indicators"><figcaption></figcaption></figure>

***

## Overall monitoring of controls and tests

In the **Controls & tests** area of the project **Overview**, four indicators give a synthetic view of the project status:

* **Controls status**: proportion of validated controls.
* **Controls implementation**: implemented or not implemented controls.
* **Tests status**:
  * passing tests,
  * missing evidence tests,
  * failing tests.
* **Tests freshness**:
  * up-to-date tests,
  * expired tests requiring new evidence.

These indicators make it possible to quickly identify points requiring attention and to prioritize corrective actions.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-015bcbf7ac073143e0ec96da1bc829f8c047132a%2Fimage-465.png?alt=media" alt="List of the project controls with their status and tests"><figcaption></figcaption></figure>

### Project history

Below these indicators, the **Project history** chart shows how the project evolves over time. Choose the period with the date picker (3 years at most), then set:

* **Time unit**: **Day**, **Week**, **Month** or **year**;
* **Metric**: **Tests**, **Controls**, **Requirements**, **Risks** or **Compliance**.

The chart lets you show the progress of compliance to management or auditors.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-767f119d68d9ca1d4c74f1748f6457a290dbd688%2Fcompliance-monitoring-history-1.png?alt=media" alt="Project history chart with the period, the time unit and the Tests metric"><figcaption></figcaption></figure>

***

## Evidence management

{% columns %}
{% column %}
Evidence is the core of the monitoring phase.\
It can be added directly from a test with **Add evidence** and be **reused across several tests of the project**.

The available collection methods notably include:

* adding evidence files,
* external links,
* selecting evidence already present in the project.

Each piece of evidence can be documented with an **Evidence description** in order to facilitate subsequent audits.
{% 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-763ebb5f13215ebf95a801eb976189ddd0d68946%2Fimage-466.png?alt=media" alt="Add evidence dialog with the file, the external link and the description"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

## Test campaigns

**Test campaigns** make it possible to orchestrate the execution of tests at scale. They are managed in the **Test campaigns** tab of the project.

A campaign allows you to:

* group together a set of tests to be executed,
* assign an owner to each test,
* define an overall deadline,
* track progress in a centralized manner.

To create a campaign, click **Create tests campaign** and enter the **Campaign label**. You can **pre-select all your project tests awaiting evidences** to make the launch easier. The campaign then opens in configuration: **Define the test campaign content**, check that each test has an owner, then launch the campaign.

{% hint style="warning" %}
If one or more tests of the campaign have no owner, Dastra shows a warning and asks you to review them before sending the invitations. Use **View tests without owners** to find them.
{% endhint %}

Launching a campaign outside the **Monitoring** phase 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-f2ef8c7dd1e1a3d275eb9b93b800a21553559ab7%2Fimage-467.png?alt=media" alt="Test campaign configuration with the content, the owners and the deadline"><figcaption></figcaption></figure>

***

## Launching and tracking campaigns

{% columns %}
{% column %}
Once the campaign is configured:

* the users concerned receive an **invitation by email**, which you send with **Send invitations** after selecting the owners to notify,
* a personalized message can be added to contextualize the request,
* each test progresses individually (*to do*, *in review*, *completed*).

The overall progress of the campaign is visible in real time, allowing the project owner to quickly identify delays or blockers.
{% 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-1eac27391059dd928b83e7656fa9ee7038c8c992%2Fimage-468.png?alt=media" alt="Send invitations dialog with the list of test owners"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Remind, close and track a campaign

In the list of campaigns, the **⋯** menu of each row offers:

* **Send reminder**: select the owners who still have tests to complete. A default reminder is sent, to which you can add a **Custom reminder message**;
* **Close test campaign**: ends the campaign; **Re open campaign** puts it back in progress;
* **Copy link**: copies the link to the campaign;
* **Move to recycle bin**: removes the campaign from the list. Use **Restore** to bring it back, or **Delete** to remove it permanently.

**Details** opens the campaign dashboard: number of tests, participants and frameworks, validated tests, **Completion rate by user** (completed tests, tests in review and tests to do) and **Test distribution by framework**.

***

## Validating tests

Each test has a clear lifecycle:

* consulting the **Test procedure**,
* adding or updating the evidence,
* validating the test with **Validate test**.

The result of a test is **Pass**, **Fail**, **Missing Evidence** or **Expired Evidence**. For a manual test, **Validate test** sets it to **Done**; **Invalidate test** cancels the validation. Once validated, the test automatically contributes to improving the status of the associated control and to the project's overall indicators.

The invitation sends the user to a personalized tracking dashboard in which they can fill in the evidence for the tests they own. This workspace is also available from **My tests** (see [Projects](https://doc.dastra.eu/en/features/compliance/projects.md)). When a user has completed all their tests, Dastra shows a congratulation message with the **View My Tasks** button.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0f5582ee3662e6a41e9d0d63c084d0d98415de81%2Fimage-469.png?alt=media" alt="Tracking dashboard of a test owner with the tests to fill in"><figcaption></figcaption></figure>

***

## Statement of applicability (SOA) export

The **Statement of Applicability** (SOA) is the reference document that gathers all the controls of a framework of the project. It is used for certification audits, for example ISO 27001, and to demonstrate the coverage of requirements to your management or auditors.

The export is done per framework, as an XLSX file:

1. Open the compliance project.
2. On the **Overview**, click the **⋯** menu of the framework card, or open the **Requirements** tab and use the **⋯** menu of the framework.
3. Click **Export statement of applicability**.

Export 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-20d1d7be2c73770cfc1aa6bfb02904c806778176%2Fcompliance-monitoring-soa-export-1.png?alt=media" alt="Framework card menu with the Export statement of applicability action"><figcaption></figcaption></figure>

The file contains one row per control, with the following columns:

| Column                 | Content                                                                                                                                                  |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ControlId`            | Reference of the control.                                                                                                                                |
| `Label`                | Name of the control.                                                                                                                                     |
| `Description`          | Description of the control, without formatting.                                                                                                          |
| `Applicable`           | Applicability: a control whose status is **Excluded** is not applicable.                                                                                 |
| `Justification`        | Exclusion justification entered on the control (see [Control status and exclusion](https://doc.dastra.eu/en/features/compliance/projects/implement.md)). |
| `ImplementationStatus` | Status of the control: **Draft**, **Implemented** or **Excluded**.                                                                                       |
| `Evidence`             | References to the evidence collected on the tests of the control.                                                                                        |
| `Auditor`              | Owner of the control.                                                                                                                                    |
| `RequirementNodes`     | Requirements covered by the control.                                                                                                                     |

***

## Expected result of the monitoring phase

At the end of this phase, the project has:

* **collected and traced evidence**,
* **regularly executed and updated tests**,
* a **reliable and measurable view of the actual compliance**,
* a solid base for preparing the **internal audit** and **certification** phases.


---

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