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

# Certifications

Dastra is committed to ensuring information security and protecting personal data, as evidenced by its ISO 27001 and ISO 27701 certifications obtained in 2025.

## ISO 27001: information security management system (ISMS)

Obtaining ISO 27001 certification demonstrates that Dastra has established an information security management system (ISMS).

This system is designed to protect sensitive information from potential threats, whether internal or external.

This certification is the result of an evaluation and continuous improvement process, which integrates good security practices into all our operations.

## ISO 27701: privacy information management

ISO 27701 certification, an extension of ISO 27001, attests to our compliance with privacy protection requirements. It strengthens our commitment to confidentiality and the protection of personal data.

This standard helps us manage privacy risks proactively and meet regulatory requirements for data protection.

## Maintaining certifications

Maintaining these certifications relies on regular audits and constant vigilance.

We make sure our processes remain aligned with these international standards. This includes continuous training of our staff and regular updates to our security policies.


---

# 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/security/certifications.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.
