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

# Compliance

Manage your compliance with the various frameworks in Dastra.

The **Compliance** module of Dastra makes it possible to manage regulatory compliance in a structured, traceable and auditable way, relying on a modular architecture aligned with compliance frameworks.

***

## Navigate the module

In the menu, **Compliance** gives access to four entries:

* **Projects**: the compliance projects, their phases, their audits and your tasks. See [Projects](https://doc.dastra.eu/en/features/compliance/projects.md).
* **Library**: the reusable frameworks, controls, tests, risks and threats. See [Library](https://doc.dastra.eu/en/features/compliance/library.md).
* **Scopes**: the organizational units covered by a project. See [Scopes](https://doc.dastra.eu/en/features/compliance/scopes.md).
* **Statistics**: the compliance dashboard of the workspace (see below).

***

## Architecture of the Compliance module

The module is based on a logical chain of objects, from regulatory frameworks through to compliance evidence.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-42707c02daebf3497bb731398d2cd429d6cd052c%2Fcompliance-object-chain.svg?alt=media" alt="Chain of objects of the module: framework, requirements, controls, risk scenarios, tests, evidence and audits"><figcaption></figcaption></figure>

### Frameworks

Examples: GDPR, ISO 27701, ISO 27001, AI Act.

A framework:

* defines the regulatory or normative framework,
* contains a set of applicable requirements.

***

### Requirements

Requirements represent the obligations arising from a framework.\
Examples: access control, authorization management, logging.

Each requirement:

* is attached to a framework,
* is assessed during compliance audits,
* is implemented through one or more controls.

***

### Controls

Controls describe **how** a requirement is applied concretely.\
Examples: periodic access review, authorization procedure.

A control:

* implements a requirement,
* is linked to one or more risk scenarios,
* is verified using tests.

***

### Risk scenarios

Risk scenarios describe the feared events. They appear as **Risks** in the application.\
Example: unauthorized access to sensitive data.

Controls make it possible:

* to prevent or reduce these risks,
* to demonstrate the remediation measures put in place.

***

### Tests

Tests are used to verify the effectiveness of controls.\
Examples: recurring access review, validation delegation.

A test:

* checks one or more controls,
* produces measurable results,
* is supported by evidence.

***

### Test campaigns

Campaigns make it possible to orchestrate tests at scale:

* sending campaigns to teams or clients,
* centralized collection of responses,
* tracking progress and statuses.

***

### Evidence

Evidence demonstrates compliance.\
Examples: policies, procedures, access review reports.

A piece of evidence:

* is associated with a test,
* is used during audits,
* ensures the traceability of controls.

***

### Compliance audits

Audits make it possible to assess the level of compliance:

* internal audits,
* self-assessments,
* preparation for external audits.

They rely on:

* requirements,
* controls,
* the associated tests and evidence.

***

### Overview

The Dastra Compliance module thus makes it possible to:

* structure regulatory requirements,
* connect obligations to risks,
* prove compliance through tested and documented controls,
* efficiently prepare for audits and certifications.

### The multi-framework principle in Dastra

The Dastra Compliance module is **natively multi-framework**.

This means that:

* a given **framework** (GDPR, ISO, AI Act…) contains its own requirements,
* a **requirement** belongs to **one framework**,
* a **control can address several requirements**, including ones from **different frameworks**,
* **tests and evidence** are shared and reusable.

Objective: **avoid duplication** and steer compliance in a cross-cutting way.

***

### Key relationships between objects

* a **framework** contains several **requirements** (1 to N),
* **requirements** and **controls**: N to N relationship,
* **controls** and **tests**: N to N relationship,
* a **test** is supported by several pieces of **evidence** (1 to N),
* **controls** and **risk scenarios**: N to N relationship.

A single control (e.g. access review) can thus:

* satisfy a GDPR requirement,
* satisfy an ISO 27001 requirement,
* reduce several risk scenarios.

Example: the periodic access review control satisfies a GDPR requirement and an ISO 27001 requirement, is verified by a test proven by evidence, and reduces two risks:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-304d1af05d7244f496616ad69c10ff124a1243af%2Fcompliance-shared-control-example.svg?alt=media" alt="Example of one control shared by GDPR and ISO 27001, with its test, its evidence and the two risks it reduces"><figcaption></figcaption></figure>

***

## Statistics

**Compliance** > **Statistics** opens the **Compliance Dashboard**, which consolidates all the projects of the workspace. Filter it by **Status** (project phase), **Organizational units** and **Scopes**.

The dashboard contains:

* global indicators. Controls: **Total Controls**, **Passing Controls**, **Not Implemented** and **Orphan Controls** (with no associated requirement). Tests: **Total Tests**, **Passing Tests**, **Failing Tests** and **Missing Evidence**. Audits: **Total Audits**, **Completed Audits** and **Average Readiness**, with the distribution of requirements between **Compliant**, **Partially Compliant**, **Not Compliant** and **Not Applicable**;
* **Framework Progression**: for each framework, the number of projects and the progress of controls, tests, requirements and risks;
* **Projects by Status**: the distribution of projects by phase;
* **Compliance by Scope**: the compliance level of each scope.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-3db559495178ce2a419fde794bc3dd3553f70160%2Fcompliance-statistics-1.png?alt=media" alt="Compliance dashboard with the global indicators, the framework progression and the compliance by scope"><figcaption></figcaption></figure>


---

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