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

# Project design

The design phase is the starting point of your compliance project.

The **Design** phase lets you define the **organizational scope** of the project, select the **applicable frameworks** and automatically initialize the associated controls, tests and risks.

This step lays the foundations of the project and determines the quality of monitoring in the following phases. For an overview of the phases, see [Projects](https://doc.dastra.eu/en/features/compliance/projects.md).

***

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-56161c045382cbae8d1caec8e3cf67e9c8a2efef%2Fimage-432.png?alt=media" alt="The phases of the compliance project, with the Scope phase in progress"><figcaption></figcaption></figure>

## 1. Creating the project and defining the scope

When creating the project, an **organizational scope** must be selected.\
The scope groups together one or more organizational units and determines **the scope of application of the compliance project**.

{% columns %}
{% column %}
Once the project is created, the scope is displayed in the project header and used throughout the compliance cycle.
{% 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-227bbdcf3a96dcf06ba99b5620a0b12591cb4f7c%2Fimage-490.png?alt=media" alt="Project creation window with the title and the scope"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

## 2. Assigning users to the project

{% 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-ca5df58548b0fb0c266684d642cae7e9cb06d022%2Fimage-491.png?alt=media" alt="Project creation window with the user assignment"><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}
The design phase also allows you to **designate the users authorized to manage the project**.

* Each user can be assigned a role: **Accountable** or **Informed**.
* These users will be entitled to steer the project's controls, tests and audits.
  {% endcolumn %}
  {% endcolumns %}

***

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-689fbc629b7ad62907790b485ce27d6d9db75c16%2Fimage-433.png?alt=media" alt="The phases of the compliance project, with the Design phase"><figcaption></figcaption></figure>

## 3. Adding compliance frameworks

A compliance project is based on one or more **frameworks** (standards, internal or custom referentials).

Adding a framework allows you to import:

* the **requirements**,
* the **controls**,
* the **tests**,
* and the associated **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-8f08e348c2b4017c72c2f70d55b4575d6a8691d9%2Fimage-434.png?alt=media" alt="Selection of a framework to add to the project"><figcaption></figcaption></figure>

Only the published versions of a framework are offered. When several published versions exist, choose the version in the **Version to install** list displayed next to the framework name; the current version is preselected.

The project remains attached to the installed version. When it is no longer the current version, the framework card in the project overview displays the **Update available** badge. Moving to another version is done manually with the **Update the framework version** action, which is not possible while an audit is in progress in the project (see [Framework versions](https://doc.dastra.eu/en/features/compliance/library/frameworks/versions.md)).

Several frameworks can be added successively to the same project.

***

## 4. Sharing controls across frameworks

When several frameworks are added to the project, Dastra automatically detects the **common controls**.

* A control shared between several frameworks **is imported only once**.
* Its implementation simultaneously covers all the associated requirements.
* This makes it possible to increase compliance coverage without multiplying 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-930925e324d73e35b687d0b19bc4781b0180e2fb%2Fimage-435.png?alt=media" alt="Import of the controls shared between several frameworks"><figcaption></figcaption></figure>

***

## 5. Selecting the controls to import

When adding a framework, several options are offered:

* import **all the controls** of the framework,
* import **only certain controls**,
* or **not import any controls** in order to implement them manually.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-090a470f7d9d1b7461651ba842fd4ca4a8dcff12%2Fimage-437.png?alt=media" alt="Choice of the controls to import with the framework"><figcaption></figcaption></figure>

This flexibility makes it possible to adapt the project to the organization's maturity.

***

## 6. Initializing controls and tests

{% columns %}
{% column %}
Once the frameworks are imported:

* The **selected controls** are automatically added to the project.
* They are considered **implemented by default**.
* The **associated tests** are also attached to the controls.

At this stage:

* the tests are set to the **"missing evidence"** status,
* no evidence has been collected yet.
  {% endcolumn %}

{% column %}

<div align="center"><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-da26c5d9d62cf336057a62bfb8a2c3b5d2df7e74%2Fimage-438.png?alt=media" alt="Project overview with the imported frameworks"></div>
{% endcolumn %}
{% endcolumns %}

***

## 7. Preparing the risk analysis

The **risks from the frameworks** can be selected during the import.

They constitute:

* the basis for the **initial risk assessment**,
* the reference point for calculating the **residual risk** after the controls are applied.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-487fb7c53f75a8013d160ac480e9dc1af6ea54dd%2Fimage-439.png?alt=media" alt="Risk matrix of the project"><figcaption></figcaption></figure>

***

## Removing a framework from the project

On the project **Overview**, the **⋯** menu of a framework card offers **Detach framework**. Dastra then removes from the project the controls, tests, risks and threats attached only to that framework. A control that the project still applies through another framework is kept.

Removal is not possible while an audit of that framework is not archived (see [Audits](https://doc.dastra.eu/en/features/compliance/projects/audits.md)).

***

## Result of the Design phase

At the end of the design phase, the project has:

* a clearly defined scope,
* identified owners,
* the applicable frameworks imported,
* shared controls ready to be monitored,
* initialized tests,
* and a structured risk base.

The project is then ready to enter the next phase: **Implementation**.


---

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