For the complete documentation index, see llms.txt. This page is also available as Markdown.

Risks

The risk library helps identify, qualify and track the risks associated with the requirements and controls defined in compliance frameworks.

In Dastra, a risk represents a feared event that may have a negative impact on the organization, in relation to the use, development or operation of systems (e.g. AI systems).

Risks are a key steering element: they make it possible to measure the organization's exposure and to assess the actual effectiveness of the controls that are in place.


Risks and controls: a central relationship

Risks are never isolated.

In Dastra:

  • a risk is covered by one or more controls

  • a control contributes to reducing one or more risks

Controls therefore constitute the risk mitigation measures. They make it possible to reduce:

  • the likelihood of the risk occurring,

  • and/or its impact on the organization.

This relationship makes it possible to move from a declarative approach to operational risk management, based on concrete and verifiable actions.


Risk library view

Risk library with the list of risks

The risk library provides a global view of the identified risks, including in particular:

  • their reference and description,

  • the associated tags (confidentiality, performance, robustness, etc.),

  • the initial impact and likelihood levels,

  • filters to facilitate cross-cutting analysis.

This view makes it possible to:

  • identify the major risks,

  • verify their coverage by controls,

  • prioritize compliance efforts.


Creating and describing a risk

Risk edit window with the name, the reference, the description and the assessment

When creating or editing a risk, the user provides:

  • the name and reference of the risk

  • a description used to qualify the risk scenario

  • tags to facilitate categorization


Risk assessment

Each risk is subject to two entered assessments, the initial risk and the residual risk, plus one calculated level, the current risk:

Initial risk

The initial risk corresponds to the risk level before the controls are implemented.

It is assessed according to:

  • a likelihood

  • an impact

These two dimensions are positioned on a standardized risk grid.


Residual risk

The residual risk corresponds to the risk level after the associated controls are applied.

Comparing the initial risk and the residual risk makes it possible to:

  • measure the effectiveness of the controls,

  • visualize the reduction of the risk,

  • justify remediation choices.

At this stage, the risk grid is fixed and common to all risks, in order to guarantee a homogeneous and comparable assessment.


Current risk

In a project, Dastra also shows the current risk. It represents the level of risk at a given point in time, based on the actual progress of remediation actions and controls. It therefore evolves between the initial risk and the residual risk.

The three levels are visible side by side in the Cartography view of the Risks tab of a project (see Project implementation).


Associating controls

A risk must be associated with one or more controls, which represent the measures implemented to mitigate it.

The association makes it possible to:

  • clearly identify the levers for reducing the risk,

  • track the impact of the controls on the residual risk,

  • ensure traceability between compliance and risk management.

Search for controls to associate with a risk

Associating threats

Risks can also be linked to threats, which represent the events or causes likely to trigger the risk.

Example:

  • Threat: lack of monitoring of AI logs

  • Risk: information leakage through AI queries

This distinction allows a finer and more structured analysis of risk scenarios.


Merging risks

As with controls and tests, the risk library can contain duplicates. Select at least two risks, then click Merge in the bulk actions, or Merge in the edit window of a risk. The wizard is the same as for controls: choose the reference version and the fields to carry over (see Controls). The merge is irreversible.


Why include risks in the library

Centralizing risks in the library makes it possible to have:

  • a cross-cutting view of risks across all frameworks

  • better consistency in their assessment

  • a direct link between risks, controls and requirements

  • more effective steering of compliance and security

Last updated

Was this helpful?