> 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/useful-reminders/risk-management/definition-of-risks.md).

# Definition of risks

Some useful reminders about the definition of risk.

## What is a risk?

A security risk is defined by the French National Agency for Information Systems Security (ANSSI) as a scenario that combines a **feared event** (sources of threats, critical asset, security criteria, security needs, impacts) and **one or more threat scenarios** (sources of threats, supporting asset, security criteria, threats, vulnerabilities)

## Types of risks

Several types of risks can be distinguished (non-exhaustive list):

| Types of risks                  | Example of risks                                                                                                                                                                                                                                                                    |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Privacy and data security risks | <ul><li>data confidentiality breach</li><li>data availability breach</li><li>data integrity breach</li></ul>                                                                                                                                                                        |
| Legal risks                     | <ul><li>breach of professional secrecy</li><li>tort and contractual liability</li><li>criminal liability</li><li>loss of compliance with legal, regulatory, normative, sectoral or internal standards</li></ul>                                                                     |
| Operational risks               | <ul><li>Natural events</li><li>Internal fraud</li><li>Theft</li><li>Sabotage</li><li>Civil liability</li><li>System failure</li><li>Disclosure of confidential information</li><li>Damage to industrial equipment</li><li>Technological risks</li><li>Environmental risks</li></ul> |
| Financial risks                 | <ul><li>Market risk</li><li>Credit / counterparty risk</li><li>Liquidity risk</li><li>Political risk</li></ul>                                                                                                                                                                      |
| Strategic risks                 | <ul><li>Non-compliance</li><li>Subcontractor</li><li>Transformation</li><li>Project</li></ul>                                                                                                                                                                                       |

## For more information

{% content-ref url="/pages/HZPdbZZ6lVXreOkF4RrE" %}
[Risk assessment](/en/useful-reminders/risk-management/risk-assessment.md)
{% endcontent-ref %}


---

# 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/useful-reminders/risk-management/definition-of-risks.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.